Organisations & roles
Create an organisation, arrange units and groups, and manage scoped roles.
Create your organisation
Sign in and open Organisation. If you have no organisation, enter a name, choose its kind and select Create organisation. You become its first admin. When you belong to several organisations, use the organisation selector. A not-connected message means the service is unavailable; it does not confirm an empty organisation.
Arrange units and groups
The tree shows the organisation, its units, groups and people. Expand a unit to inspect its contents. Admins can use the row's Actions menu to create, rename or manage the parts they administer. Available moves can be made through the menu or drag and drop, with confirmation. A unit admin manages that unit and its descendants; a group admin manages that group's members.
Invite the right people
On the target unit or group, use Invite here or Invite to group and choose the intended role. The recipient opens the invitation while signed in with the invited email address. Follow the result shown: when email is unavailable, the screen provides a one-time link for you to send yourself. Creating an invitation does not prove delivery or acceptance. Use the available controls to resend or revoke pending invitations.
Understand the roles
| Role | Organisation management |
|---|---|
| Admin | Manages people, invitations and the units or groups within their scope. |
| Member | Sees the organisation tree and member list; does not gain admin controls. |
| Viewer | Sees the organisation tree and member list read-only. |
Organisation roles govern organisation management. They do not change your reading, token or product plan permissions. Each person counts as a seat, including viewers. Leaving or removing people must preserve the organisation's required admin.
Billing visibility
Top-level organisation admins can see the organisation's billing summary, including its plan and people count, and choose its billing contact. Connected subscription and invoice details are read-only; a not-connected notice does not establish an active subscription or payment. Admin access to a sub-unit or group alone does not grant top-level billing visibility. See pricing and tokens for current payment availability.