Entity Views

Entity Views limit the exposure of Device or Asset telemetry and attributes to Customers. Similar to SQL database views, an Entity View exposes only a selected subset of data from the underlying entity. As a Tenant Administrator, you can create multiple views per device or asset and assign them to different customers.

Common use cases:

• Share selective data — expose specific telemetry keys (e.g. sensor readings) to a customer while hiding debug information like battery level or system errors
• Multi-customer sharing — share data from the same device or asset with multiple customers simultaneously, each seeing only their permitted data
• Device-as-a-Service (DaaS) — partition data collected by a device over different time periods, assigning each period to a different customer

1. Navigate to Devices & assets ⇾ Entity views.
2. Click + Add entity view.
3. Enter a Name (must be unique within the tenant) and Entity view type.
4. Select the Target entity (Device or Asset) and pick the target entity.
5. Configure the data filter:
   • Time series — select which telemetry keys are visible through this view.
   • Attributes — select which server, client, and shared attribute keys are visible.
   • Start time and End time — optionally restrict the time window for telemetry access.
6. Click Add.

1. Click the entity view in the list to open its details.
2. Click the pencil icon.
3. Update the name, target entity, data filter, or time window.
4. Click Apply changes.

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

1. Click the entity view 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 entity view to relevant entity view groups or create a new group.
5. Click Update.

Opening an entity view reveals a details panel with the following tabs:

Tab	Contents
Attributes	Copied attribute key-value pairs from the target entity (filtered by the view’s attribute keys)
Latest Telemetry	Most recent telemetry values from the target entity (filtered by the view’s time series keys and time window)
Alarms	Alarms propagated from the target entity
Events	Lifecycle events, logs, warnings, and errors
Relations	Directed connections to other entities
Audit Logs	History of user actions: creation, updates, deletions

All time series data is stored on behalf of the target entity — there is no data duplication. When a dashboard or API request queries an entity view:

• The request time range is clamped to the entity view’s start and end time. Queries outside this window return no data.
• Only telemetry keys listed in the entity view’s time series filter are returned. Requests for other keys are silently ignored.

Entity View copies the specified attributes from the target entity each time you save or update the entity view. For performance reasons, attribute changes on the target entity are not automatically propagated to the entity view.

To enable automatic propagation, add a “copy to view” rule node in your rule chain and link Post attributes and Attributes Updated messages to it:

• Dashboards — use entity views as data sources in widgets, so customers see only their permitted data
• Customers — assign entity views to customers to control data visibility
• Rule Engine — propagate attributes via the “copy to view” rule node
• REST API — query, create, and manage entity views programmatically