Illustrative roles. Permissions belong to the organisation, not individual outlets.
These controls are implemented on the development backend. Production rollout
is separate. Email-code verification requires working auth email delivery;
invitations currently produce a link to share, rather than sending an
invitation email.
A role belongs to an organisation
One account can have different roles across brands. Switching organisations changes the data and permission context; it does not combine their customers or billing.
Permissions are checked by server actions and database functions/policies—not just
by hiding buttons. Some configuration forms remain owner-only.
Invite a teammate
Open Settings → Team & access under Organisation settings. Enter the person’s email and choose Manager or Staff, then select Create invitation. Copy the generated link and share it directly with that person. The recipient signs in with the invited email, verifies that email, returns to the invitation link, and accepts. Links expire after seven days and cannot be accepted by another email. An owner can revoke a pending invitation. Duplicate pending invitations and invitations to existing teammates are rejected. Acceptance must fit the workspace’s team allowance. An invitation cannot promote an existing Staff member; use the role controls instead.Change or remove access
The owner can select a teammate’s role and choose Save role, or choose Remove and confirm. The Owner badge is separate: an owner cannot be downgraded or removed through the teammate controls. Removed teammates lose access on subsequent requests.Transfer ownership
- Invite the new owner as a teammate and have them accept first.
- In Ownership transfer, send a code to your sign-in email and verify it.
- Select the teammate and request the transfer.
- The teammate opens Organisation settings, verifies their own identity, accepts the responsibilities, and selects Accept ownership within 24 hours.