Device groups

Manage devices together, share access, invite people

A device group bundles multiple devices under one shared label — e.g. "North Site" or "Cold Chain A". Once a group exists, you can give other people access to exactly those devices from the app section under "Device groups", without having to add them as an owner on every device individually — and a Monitoring rule can target the whole group instead of a single device.

Device groups currently have no effect on your dashboard — they don't filter or select devices there. Their only purpose is sharing access and serving as a target for Monitoring rules.

Groups and their members

List of your own device groups

Each row shows, next to the label, your own role in that group, the number of devices assigned to it, and the member count. If there are open invitations alongside members who already joined, a fraction like "1/2" appears here — one person is already a member, a second was invited and hasn't accepted the invitation yet.

There are two roles within a group:

  • Regeladmin — can add or remove devices and members, rename or delete the group, and can create, change, or delete Monitoring rules for this group.
  • Betrachter — sees the group, its devices, members, and the Monitoring rules and incidents that apply to it, but can't change any of it.

These roles apply per group independently — the same person can be Regeladmin in one group and only Betrachter in another. Whoever creates a group automatically becomes its first Regeladmin.

Creating a group

Use + New group to give it a label and, optionally, pick its devices right away — both can be changed at any time later.

Form for creating a new device group

Members and invitations

You manage a group's membership through its edit dialog — both members who already joined and invitations that are still open:

Members and invitations area in the edit dialog

To add someone, enter their email address and pick the role you want (Regeladmin or Betrachter):

  • If an account already exists with that email address, the person is added as a member immediately — with no further confirmation from them.
  • If no account exists yet, this turns into a real invitation: the person receives an email with a link that lets them set up their own account first. Until then, the entry appears under "Pending invitations" and, as described above, is counted separately from confirmed members — recognizable by the × next to it, which lets you withdraw an open invitation at any time.

What the invited person sees

The invitation link leads to its own page where the invited person sets up an account:

Form for accepting an invitation with account setup

Besides a username and password, this also asks for the usual profile details (name, phone number, newsletter consent, agreement to the Terms and Conditions and the Privacy Policy) — the same as a regular registration. A brief, automatic security check prevents invitation links from being abused by automation in the process. Once submitted, the account is created and immediately joins the group with the role set at invitation time — no further step needed.

An invitation fixes a role when it's created — it can't be changed afterwards, before it's accepted. If someone should join with the other role instead, the old invitation has to be withdrawn and a new one sent with the desired role.

Device groups and Monitoring

The real value of a device group shows in Monitoring: a rule that targets a group instead of a single device automatically applies to every current and future member device — if another device is added to the group later, it gets monitored too without any change to the rule itself.

If one of the group's members violates such a rule, it becomes an Incident — an alert state detected by Monitoring, independent of the group's other members. An incident goes through the stages open → acknowledged → resolved; every member of the affected group can see, acknowledge, and resolve it — but creating, changing, or deleting the underlying rule itself stays reserved to the group's Regeladmins. The full explanation of rules, condition types, severities, and the incident lifecycle is in the Monitoring documentation.