Sharing a device

Sharing a device

A device belongs to whoever registered it, but you can let other people see and control it. Open the device’s gear button → Access.

Giving someone access

Enter their email address and add them. They need an existing Sensordata account — sharing doesn’t create one, so ask them to sign up first if they haven’t.

Once added they’ll see the device in their own device list, with its dashboard, and can send commands to it.

What each person can have

Everyone with access appears in a list, each with three switches:

Admin — an admin can change the device’s settings, build its dashboard and manage who else has access. Leave it off for someone who should only view and use the dashboard.

Notifications — whether notifications from this device reach this person. It’s off by default, so a newly added user gets nothing until you switch it on.

Commands — whether this person can send anything to the device. With it off their dashboard still updates, but the elements that send — buttons, switches, sliders, the command box, file transfers — are greyed out, and say why on hover. An admin’s row shows this on and locked: an admin is never shut out of their own device.

Notifications are per person, not per device

Turning on the notification service in device settings decides how notifications are delivered. This switch decides who gets them. Both have to be set, which is the usual reason a notification never arrives.

Admin-only elements

Every dashboard element has an Admin only checkbox in its settings. Tick it and the element disappears for everyone who isn’t an admin of the device — not greyed out, gone, along with the row it sat on if nothing else was there. It isn’t sent to them either: the server leaves those elements out of the dashboard it hands anyone who can’t edit it. While you’re editing, your own dashboard marks those elements with an amber dashed border, since they look ordinary to you otherwise.

Use it for the things a user has no business pressing: a factory reset, a calibration run, a debug command. It pairs with the Commands switch rather than replacing it — Commands is about a person, Admin only is about an element.

⚠️

This hides, it doesn’t refuse

Admin only is a dashboard setting, so the command behind a hidden element is still a command the server will deliver if someone sends it another way. Treat it as tidying away what people shouldn’t press, not as a lock — if a command is genuinely dangerous, make the firmware check before acting on it.

Removing access

The delete button beside a person removes their access immediately. The device stays yours; they simply stop seeing it.

Deleting the device

The Access tab is also where you delete the device entirely. This removes its dashboard, its stored data, its logs, and everyone else’s access. It cannot be undone.

Note that a device which is still powered on and still has a valid API key in its firmware will register itself again the next time it connects — it comes back as a fresh device, without its old dashboard or history. To retire a device for good, delete the API key it uses, or reflash it first.