An organisation administrator manages membership and product-role grants in Accounts. The products then apply their operational permissions and local site restrictions.
Invite the right identity
Open your organisation's Manage employees and access page. Check the organisation name before adding or changing a member. Use the person's own email address and the invitation controls provided.
The person must complete their identity set-up and accept the invitation. A pending or expired invitation is not active membership. Read any delivery or invitation status and use the provided resend action when appropriate.
Choose roles per product
Arrange access to the enabled product and select the roles the person actually performs. The suite's usual meanings are:
| Role | Main purpose |
|---|---|
| Owner | Site, team, devices, connections, plan, recovery, complete export and closure. |
| Author | Draft and test what production will use, then freeze it for review. |
| Reviewer | Review configuration, make releases live and manage approved reversals. |
| Supervisor | Oversee work, handle exceptions and authorised corrections or exports. |
| Operator | Do permitted everyday work: look up, scan, check, record or print. |
| Viewer | Read permitted records without changing them. |
Products can have additional roles or more specific boundaries. RefillFlow, for example, has Stores for picking and dispatching refills. Use the product's own handbook and role description for the exact action.
Understand Owner and seats
Every organisation administrator holds Owner automatically in applicable products. You do not tick or untick it as an ordinary role. Owner alone generally does no production work and takes no product seat.
An administrator who prints, authors or reviews needs those working roles too. A person with several ordinary roles uses one seat in that product, subject to its allowance. Viewer is an ordinary role and can take a seat.
The creator of an organisation may start with working roles in its initially enabled products where seats are available. Administrators or products added later do not automatically receive those working roles. Inspect the actual grants.
Where offered, Give me every role and Remove my roles change your ordinary roles. They do not remove the Owner role that follows organisation administration, bypass seat limits or waive independent review.
Check the product's site access
Central grants are one part of access. A product's Team & stations or equivalent can restrict a person locally or leave them waiting after removal. Ask the product Owner to check those assignments if central access appears correct.
After changing roles, have the person reopen the product and verify the intended actions using their own identity. Do not use role changes to bypass an unresolved production hold or an independent-approval rule.