People reach your organisation as members. Each member has one built-in role, a status, and may be in groups. This page covers the Members page, the roles and the rules around them. Inviting people is described in Invite your team; groups in Groups and permissions.
The Members page
Open Members (in the Organisation part of the menu). It lists “People with access to this organization” with Member, Role, Status and Joined. Use Search by email… to find someone.
| Button | What it does |
|---|---|
| Invite Member | Sends an invitation e-mail. See Invite your team. |
| Report | Member figures for the organisation. |
| Member settings | The default role and the approval rule (below). |
| Edit (row) | Change the role and the status. |
| Remove (row) | Removes the member. “This will immediately revoke their access.” |
Every member can see the list. Changing it needs the Admin role or higher.
Built-in roles
| Role | Can |
|---|---|
| Owner | Everything, including managing owners and admins, ownership transfer, deleting the organisation, buying or changing the plan, raw device commands, firmware signing keys and rotating API keys and webhook secrets. |
| Admin | Manage members, settings, devices, credentials, profiles, alarm rules, commands, firmware, flows, shared dashboards and rules. |
| User | View devices, profiles, dashboards and alarms; acknowledge alarms; send basic commands; run rules and switch their mode; build personal dashboards. |
Rules that always hold:
- You can only give a role below your own. The Owner role is never given on this page or by invitation: “The Owner role cannot be given here. Ownership is handed over with a transfer.”
- Only owners can change, suspend or remove owners.
- The organisation always keeps at least one active owner. The last owner cannot be demoted, deactivated or removed.
- An owner cannot remove themselves.
- A role or status change ends the member’s current sessions in the organisation, so the new rights apply at once.
Member statuses
| Status | Meaning |
|---|---|
| Active | Normal access. |
| Pending | Invited and not yet accepted, or held for an administrator’s review (see below). No access. |
| Inactive | Switched off by an administrator, or removed from your identity provider by SCIM. No access. |
| Suspended | Blocked for a while or until reactivated, with a reason. No access. |
The member page
Open a member to see the Overview, Permissions and Activity tabs.
| Item | What it shows or does |
|---|---|
| Identity and Membership | E-mail, Role, Status, Groups, Joined, Last active; for members provisioned by SCIM the SCIM external ID. |
| Edit role / status | Same as Edit on the list. |
| Manage groups | Assign groups. See Groups and permissions. |
| Suspend / Reactivate | Suspend with a reason and an optional end (Suspended until, or Indefinite); reactivate later. |
| Sign out | “Name is signed out of this organization on every device at once. They can sign in again; to keep them out, suspend them.” You can add a Note for the audit log. |
| Permissions tab | Effective access: what the member can do, from their role plus their active groups. Needs the right to manage access control. |
| Activity tab | The audit events of this member, newest first. |
Approval of sensitive member changes
Under Member settings, Require approval for sensitive member changes holds the following in an approval queue until a second reviewer approves: granting the Owner or Admin role, and removing an owner or admin. While a change waits, the page says “The role change was submitted for approval.” or “The removal was submitted for approval. The member keeps their access until it is approved.” Off (the default) applies changes at once. Only an owner can change this setting.
Default Member Role sets the role of invitations and added members that name no role: User (default) or Admin. People who sign up on their own always join as User.
New members held for review
In development: the AI firewall’s action that holds a new membership (a self sign-up or an accepted invitation of the last seven days, never an owner) for an administrator’s review. When it runs, the member shows as Pending and cannot work in the organisation; to approve, set the member Active with Edit. See The AI firewall.
Hand over ownership
Ownership moves only by a transfer. The new owner must be an active member. In one step the member becomes Owner and every current owner steps down to Admin (or User, if you choose), so the organisation is never without an owner.
A button for the transfer on the Members page is In development. Until then an owner makes the transfer with an API call from a signed-in session (API keys never hold owner-only permissions):
POST /tenant/{tenantId}/api/members/transfer-ownership
Content-Type: application/json
{ "toUserId": "<user id of the new owner>", "demoteTo": "ADMIN" }It answers 200 {"message": "Ownership transferred"}, 404 when the user is not a member, and 409 when the member is not active. The transfer is written to the audit log.
A sole owner must hand over ownership before deleting their own account while other members remain. See Export your data and close your organisation.
Seats
Your plan may limit the number of members. Active members and open invitations both count. When the limit is reached, new invitations and additions are refused; the check is made when the invitation is sent, never when it is accepted. My Modules shows the seat limit (“Members: up to n seats.”). See Your subscription and entitlements.
Programs are not members
Integrations use API keys, not personal accounts. A key acts within the rights of the member who created it. See API key hardening and Authentication.