Skip to content
Stand with Ukraine flag

Assets

Assets are abstract entities in ThingsBoard that represent physical objects, spaces, or organizational units — buildings, rooms, production areas, fields, streetlights, substations, or vehicles. Unlike devices, assets don’t generate telemetry on their own but can aggregate data from related devices and participate in rule chains, alarms, and dashboards.

  1. Navigate to Entities → Assets.
  2. Click + and select Add new asset.
  3. Enter a Name (must be unique within the tenant).
  4. Optionally select an Asset profile (defaults to “default”), Label, or Description.
  5. Click Add.
  1. Click the asset in the list to open its details.
  2. Click the pencil icon.
  3. Update the name, label, profile, or description.
  4. Click Apply changes.

Click the trash icon next to the asset and confirm, or open the asset details page and click Delete asset.

Opening an asset reveals a details panel with the following tabs:

TabContents
AttributesClient, server, and shared key-value pairs (location, category, configuration parameters)
Latest TelemetryTelemetry propagated from related devices, aggregated via calculated fields, or added manually; supports manual entry and deletion
Calculated FieldsValues computed from telemetry or attributes using formulas
Alarm RulesConditions, thresholds, and triggers configured for alarm generation
AlarmsActive and historical alarms for this asset
EventsLifecycle events, logs, warnings, and errors
RelationsDirected connections to other entities (devices, assets, dashboards, rule chains)
Audit LogsHistory of user actions: creation, updates, deletions
Version ControlGit-based export and restore for backup and collaboration

You can change the owner of an asset to control which Customer (or the Tenant) has access to it.

  1. Click the asset to open its details.
  2. Click Manage owner and groups.
  3. In the Owner field, select the Tenant or a specific Customer.
  4. Add the asset to relevant asset groups or create a new group.
  5. Click Update.

The Include customer entities toggle on the Assets page controls whether assets owned by customers appear in the list alongside tenant-owned assets.

Assets can belong to one or multiple groups for organization and access control. Every asset is automatically added to the "All" group of its owner.

  1. On the Assets screen, go to the Groups tab.
  2. Click +.
  3. Enter the group name.
  4. Optionally configure shared access for your customers.
  5. Click Add.

Add, Move, and Remove Assets

Section titled Add, Move, and Remove Assets

Add assets to a group:

  1. Open any asset group (e.g., "All").
  2. Select assets using the checkboxes.
  3. Click the Add to group icon.
  4. Select an existing group or create a new one.
  5. Click Add.

Move assets to another group:

  1. Open a specific (non-"All") group.
  2. Select assets and click Move to group.
  3. Select the target group and click Move.

Remove assets from a group:

  1. Open a specific (non-"All") group.
  2. Select assets and click Remove from group.
  3. Confirm removal.

Make a Group Public / Private

Section titled Make a Group Public / Private

Click the Make public icon next to an asset group to expose all its data publicly, or Make private to revoke access.

  1. Click the Share icon next to the asset group.
  2. Select the target customer.
  3. Optionally specify a user group within that customer.
  4. Click Share.

To manage permissions after sharing, click the pencil icon on the group, navigate to the Permissions tab, and add, edit, or delete permission entries.

You can create, view, edit, and delete relations between an asset and other entities from the Relations tab of the asset details page.

Add a relation:

  1. Open the asset details → Relations tab.
  2. Select the direction: From (outbound) or To (inbound).
  3. Click +.
  4. Set the Relation type (e.g., Contains, Manages) and choose the target entity.
  5. Click Add.
  • Dashboards — visualize aggregated data, attributes, and alarms via widgets
  • Rule Engine — process attribute updates, trigger alarms, route messages
  • Calculated Fields — compute derived values by aggregating data from related devices
  • Relations — model hierarchies (e.g., Building → Contains → Room → Contains → Sensor)
  • REST API — query, create, and manage assets programmatically