Skip to content
Stand with Ukraine flag

Device admin table

  • Widget
  • v1.0.0
  • Sep 1, 2026
  • MIT license
  • v4.2+ | Built-in
Device admin table

Customized entity table widget with preconfigured actions to create, update and delete devices.

Widget Type
  • Latest
Category
  • Tables & Lists

Who it’s for

Anyone who administers devices from a dashboard rather than from the platform’s own entity pages — a customer managing their own estate, an operator adding equipment during a rollout, a team whose devices are maintained by people who never see the admin UI.

What it does

The Device admin table lists the devices an alias resolves to and adds create, update and delete actions to the table. It is the Entities table with those actions preconfigured, so a dashboard can offer full device management without any action being wired up by hand.

  • Create, update and delete arrive configured, which is the whole difference from a plain entities table.
  • The alias defines which devices are listed, so a customer’s dashboard manages only their own.
  • Columns mix entity fields, attributes and telemetry, so an administrative row also carries live context.
  • Full-text search and pagination work server-side, keeping the table usable on a large estate.
  • A row style function colors rows from their own values, so an incomplete or faulted device stands out.
  • Column display can be chosen by the reader, so one table serves several roles.
  • The Device admin table acts through the same permissions as its user: the actions appear regardless, and fail for a user whose role does not allow them.

How to set up

Data keys

The Device admin table takes one column per data key.

KeyRoleTypeDescription
Entity nameOne columnEntity fieldEntity fields such as name, label and type are available as keys.
Any telemetry keyOne columnTimeseriesAttributes work equally well and can be mixed in. The key’s label is the column heading.

Point the alias at exactly the devices this table should manage. The delete action operates on whatever the table lists, so an alias broader than intended is a broader delete than intended.

Table

SettingDefaultEffect
Entities table titleDevice admin tableThe caption above the table
Default sort orderentityNameWhich column the table opens sorted by
Enable searchOnFull-text search across the rows
Enable select columns to displayOnLets the reader hide and show columns
Always display actions columnOnKeeps the actions visible while scrolling
Display paginationOnShows the pager, with configurable page size and steps

How to customize

  • To show the fields that matter when creating devices — add a device profile, its credentials and its label as columns.
  • To highlight incomplete records — turn on Use row style function and color rows whose required attributes are missing.
  • To name the columns for readers — edit each data key’s label.
  • To open on the newest first — set the Default sort order, which defaults to name order.
  • To fit the tile — set the Default page size and the page step settings.
  • To simplify a fixed board — turn off search and column selection.

Tips

  • Scope the alias tightly before publishing this to anyone. The table carries a delete action, and the difference between an alias for one site and an alias for the whole tenant is invisible on the dashboard itself.
  • Add the attributes that a new device must have as columns. An administrative table that shows only names lets devices be created incomplete, and the gap is usually found much later by whatever depends on those attributes.

Share Your Widget with the Community

Built a custom widget? Export it as a JSON from ThingsBoard and publish it to the IoT Hub through a simple 4-step wizard (Upload, Listing, Readme, Review & Submit). Share it with thousands of ThingsBoard developers worldwide and get featured in the catalog.