Skip to content
Stand with Ukraine flag

Entity Management

  • Solution Template
  • 6 installs
  • v1.0.0
  • Jul 20, 2026
  • MIT license
  • v4.2+
  • PE

An accelerator for managing every core entity type — customers, users, locations and devices — from a single dashboard. Built around two roles: a system administrator who manages everything (and creates customer administrators right here), and a customer administrator scoped to their own data.

Category
  • Asset Management
  • Device Management
  • Operations

Entity Management

The Entity Management template is a production-ready accelerator for managing every core entity type on ThingsBoard PE — customers, users, locations (assets) and devices — together with the relations and ownership between them, all from a single dashboard. Instead of jumping across separate platform pages, you run the whole hierarchy in one place.

Built for two user roles

The solution is designed around two roles that share the same data model but see it at different scopes:

  • Tenant administrator — the top-level operator. Manages all entities: creates and edits customers, and inside each customer manages its locations, users and devices. Crucially, the tenant administrator can create a customer administrator directly in this solution (from a customer’s Users tab) — no separate provisioning step required.
  • Customer administrator — a customer-scoped operator created by the tenant administrator. Signs in to a dedicated dashboard and manages only their own customer’s locations, users and devices, thanks to role-based access control.

What it does

  • Manage customers — create, edit and delete customers (title, country, address) from one table.
  • Manage users — add customer users and customer administrators; the tenant administrator provisions them in place.
  • Locations as geofences — draw a location’s boundary as a polygon on an interactive map and store it on the asset.
  • Manage devices & ownership — devices are owned by a customer and can be assigned to a location. Assigned devices carry latitude/longitude and an isAssignedToLocation flag, so they render as markers inside the location polygon on the map.
  • Relations — a location is linked to its devices via the locationToDevice relation.

What gets installed

  • 1 sample customer (Customer A) in New York, with an administrator user created inside the solution.
  • 2 locations — Location 1 (Manhattan) and Location 2 (Brooklyn) — both owned by Customer A and stored as map polygons.
  • 3 devices owned by the customer, all assigned to a location and placed on the map.
  • Roles — a generic Administrator role and a read-only dashboard role.
  • Two dashboards — a tenant administrator dashboard (main) and a customer administrator dashboard shared with customer users.

Who it is for

Solution builders and system integrators who need a clean, ready-to-extend foundation for managing customers, users, sites and devices — with the tenant-admin-provisions-customer-admin flow already wired up.

Share Your Solution with the Community

Built a complete IoT solution? Package it as a ZIP archive — dashboards, rule chains, profiles, calculated fields, devices, and emulators — and publish it to the IoT Hub so others can deploy your architecture in one click.