Reference & Data Model
Roles: Owner, Admin, Member (member.role)
Every member has exactly one role in their organization; the role governs running the organization, not access to data.
Purpose
Section titled “Purpose”The Membership (data type: identity) connects a user account with the organization and carries the Role. There are three values:
| Role | Technical | How you get it |
|---|---|---|
| Owner | owner |
Creating the organization; exactly one person; not transferable |
| Admin | admin |
Invitation with role „Admin“ or promotion by Owner/Admin |
| Member | member |
Invitation with role „Member“ or demotion of an Admin |
Owner and Admin manage settings, members, teams and grants through their role; the Owner differs only in that their row in the member list has no actions: they can be neither demoted nor removed. No role gives anything for data: every person needs a grant at a place for that, owners and admins too. Whoever creates the organization gets “Full access” on the whole organization for that. A fourth kind of member is the guest: a guest never does more than the guest list allows and gets grants only on single projects or drives (see Access: who may do what).
Where in the app
Section titled “Where in the app”Sign-in service › „Organisation“ › list „Members“ (name, e-mail, role as selection „Member“/„Admin“ or chip „Owner“, button „Remove“) and section „Pending invitations“. See Guides › Inviting colleagues & assigning a role.
Invitation (invitation)
Section titled “Invitation (invitation)”| Field | Technical | Type | Required | Meaning | Notes |
|---|---|---|---|---|---|
email |
Text | yes | Invited address | Must not belong to any organization | |
| Role | role |
Selection | yes | „Member“ or „Admin“ | Owner not selectable |
| Employee record | employeeId |
Reference | no | Employee that is linked on acceptance | Only unlinked employees selectable; or „Create a new employee from this invitation“ with first/last name |
| Expires | expiresAt |
Date | yes | End of validity | Shown as a chip in „Pending invitations“ |
| Status | status |
Selection | yes | see States | System |
States
Section titled “States”| Value | Meaning | Transition |
|---|---|---|
pending |
pending | Set on inviting |
accepted |
accepted | Invited person accepts during onboarding → membership is created |
cancelled |
canceled | „Cancel“ by Owner/Admin; re-inviting the same address replaces the old invitation |
| expired | Expiry date passed | No value of its own: the row stays pending but is no longer shown and can no longer be accepted |
Rules & automation
Section titled “Rules & automation”- Inviting only by Owner/Admin; members see neither invitations nor the „Invite someone“ button.
- Acceptance only with the invited address („Wrong account.“ when signed in with another). A user account is only created if a valid invitation exists.
- Role change: Owner/Admin switch others between „Member“ and „Admin“. Your own role is locked, your own row has no „Remove“.
- Removing ends the membership; the person can no longer sign in. The user account and the employee remain with their historical data.
- The role value is read fresh from the membership on every protected action, not from the sign-in token – a demotion takes effect immediately.
See also
Section titled “See also”Access: who may do what · Organization · Guides › Role vs. permission · Guides › Admin