Asset Profiles

Asset profiles let you centrally define common settings for a group of similar assets — rule chain, queue, alarm rules, and calculated fields. Instead of configuring each asset individually, you define the profile once and assign it to as many assets as needed.

1. Navigate to Profiles ⇾ Asset profiles.
2. Click + Add asset profile and select Create new asset profile.
3. Enter a Name (the only required field).
4. Optionally configure the rule chain, queue, alarm rules, and calculated fields.
5. Click Add.

1. Click the profile name or the pencil icon.
2. Update the desired settings across any tab.
3. Click Apply changes.

Click the trash icon next to the profile and confirm deletion.

Clicking a profile opens a details panel with the following tabs:

Tab	Contents
Details	Name, default rule chain, mobile dashboard, queue, default edge rule chain, profile image, and description
Calculated Fields	Formulas for computing derived metrics from asset telemetry or attributes
Alarm Rules	Conditions, severity levels, and actions applied to all assets in this profile
Audit Logs	History of user actions performed on this profile
Version Control	Git-based export and restore for backup and collaboration

A few Details fields are easy to misread:

• Mobile dashboard — the dashboard the mobile app uses as the device details screen for assets on this profile. Unrelated to the per-user login dashboard covered in Dashboards.
• Default edge rule chain — only relevant if the tenant also runs ThingsBoard Edge; it’s the rule chain Edge instances use to process incoming data for assets on this profile.

By default, the Root Rule Chain processes all incoming messages and events for every asset. As your system grows and you introduce different asset types, the Root Rule Chain can become complex.

Assign a dedicated rule chain to an asset profile to isolate processing logic — attribute updates and lifecycle events (Created/Updated/Deleted) — for that asset type without overloading the Root Rule Chain.

By default, all messages use the main queue. Assign a custom queue to isolate high-priority assets from high-volume ones, or to apply different submit and processing strategies. See Queues for available delivery guarantees and configuration.

Define conditions that apply to all assets in this profile — for example, trigger a Critical alarm when a computed value exceeds a threshold. Rules defined here are shared across every asset using the profile. See Alarm Rules.

Define formulas that compute derived metrics from telemetry or attributes — for example, aggregating temperature readings from every related device into a single building-level average. Like Alarm Rules, calculated fields defined here are inherited by every asset using the profile; an asset-level calculated field runs alongside any profile-level one, not instead of it. See Calculated Fields.

Export asset profile downloads the profile’s configuration as a JSON file — useful for backup or for migrating a profile between ThingsBoard instances. Import asset profile (from the + Add asset profile menu) creates a new profile from a previously exported file.

Sets this profile as the tenant’s default — the one pre-selected in the Asset profile field when creating a new asset without explicitly choosing one. Only one profile can be the default at a time.

Editing a profile’s Rule Chain, Queue, Alarm Rules, or Calculated Fields immediately affects every asset already assigned to that profile — there’s no need to touch individual assets. This is the main advantage of configuring these settings at the profile level instead of per asset.

Moving an asset to a different profile (in Edit an Asset) applies that profile’s rule chain, queue, alarm rules, and calculated fields going forward — it does not retroactively change alarms or calculated field results already generated under the previous profile.

Symptom	Cause	Fix
Alarm rule or calculated field doesn’t seem to run	It was added on the asset instead of the profile (or vice versa)	Confirm which level the rule was created at — profile-level rules apply to every asset on that profile, asset-level rules apply only to that one asset
Custom queue isn’t selectable when editing a profile	The queue hasn’t been created yet	Ask a System Administrator to configure the queue first — see Queues
New asset doesn’t get the profile you expected	No profile was selected at creation, so the tenant’s default profile was applied	Check which profile is marked default — see Make Asset Profile Default — or select the profile explicitly when creating the asset
Imported asset profile fails or looks incomplete	The JSON file was edited by hand or exported from an incompatible ThingsBoard version	Re-export the original profile and import that file unmodified

• Assets — every asset is assigned exactly one profile, inheriting its rule chain, queue, alarm rules, and calculated fields
• Rule Engine — the profile’s rule chain and queue route and process attribute updates and lifecycle events from all its assets
• Alarm Rules and Calculated Fields — shared logic applied across every asset using the profile
• Entity Groups — a separate mechanism for organizing assets; groups control access and sharing, profiles control behavior
• Roles — profile-level settings apply tenant-wide regardless of which role or customer owns an individual asset