Invite another user to a workspace and assign them a role.
Goal
Add a new member to an existing team workspace.
Preconditions
- The workspace is a team workspace, not a personal workspace.
- You are an Owner, a Moderator, or an Editor inviting a Reader.
- The workspace member quota is not reached (see product / plans and roles).
- You know the invitee's email.
Steps
- Open the workspace Members settings.
- Click Invite member.
- Enter the invitee's email.
- Pick a role: Moderator, Editor, or Reader. Reader is preselected. Only an Owner can invite a Moderator, and an Editor can only invite Readers.
- Pick the language of the invitation email.
- Click Send invitation.
The invitee receives an email with a sign-up or join link.
Verify success
- The invitee appears in the Members list with status "Invited."
- After they accept, status becomes "Active."
Widening what a Reader can do
A Reader can already read everything. To let them contribute, open their row's Manage access and grant editing on specific audits, the right to create audits, or edit access to journeys and accessibility plans. Everything is saved in one step.
Start there rather than promoting someone to Editor: an Editor can change every audit in the workspace, which is rarely what a single collaboration needs.
Common pitfalls
- Inviting to a personal workspace is not allowed; create a team workspace first.
- Handing out Moderator by reflex. A Moderator manages every member and every audit in the workspace. Most collaborators need Reader, plus a grant on the audits they work on.
- Plan quota exceeded. The invitation is refused once the workspace is at its member limit. Upgrade or remove an inactive member first.
- Expecting a Reader to be blind. A Reader sees every audit in the workspace. If somebody must see one audit and nothing else, share that audit with them directly instead of adding them to the workspace.
Revoking access
In the Members list, open the member's overflow menu and choose Remove. Access ends immediately, including any per-audit grant.
If that person owns audits, the dialog asks who takes them over and defaults to the workspace Owner: an audit must belong to somebody still in the workspace. Reports and statements keep crediting the original auditor.
A member can also leave on their own, from their own row. An Owner can do neither, and must transfer ownership first.
Related
- product / plans and roles - what each role can do.
- product / workspaces - workspace settings.