Skip to content

Team and roles

A workspace holds your sites, scans, issues and reviews, and the people who work on them. Each person has one role in it. You can belong to several workspaces, with a different role in each, and move between them from the workspace switcher at the top of the dashboard.

Role In short
Owner Everything, including inviting and removing people, changing roles, transferring ownership and deleting the workspace. The person who created the workspace is its owner, until they transfer it.
Admin Runs the workspace day to day: billing, integrations, API and MCP tokens, the statement, the VPAT and public pages, as well as everything a member does.
Member Does the work: adds and sets up sites, runs scans, triages issues, answers review checks, runs journeys and shares scan reports.
Viewer Reads everything a member can see, but changes nothing.
Task Owner Admin Member Viewer
See sites, scans, issues, reviews and reports Yes Yes Yes Yes
See who is in the workspace Yes Yes Yes Yes
Use the compliance copilot (Growth and above) Yes Yes Yes Yes
Add sites, and pick a schedule while adding one Yes Yes Yes No
Change a site’s settings, schedule and sign-in details, or delete it Yes Yes No No
Run, pause and cancel scans; verify fixes Yes Yes Yes No
Triage issues: status, assignee, comments, ignores Yes Yes Yes No
Answer review checks and record verdicts Yes Yes Yes No
Write and run journeys Yes Yes Yes No
Generate readiness reports and the evidence pack Yes Yes Yes No
Create and revoke share links to a scan Yes Yes Yes No
Draft and export the statement and the VPAT; publish public pages Yes Yes No No
Create and revoke API and MCP tokens Yes Yes No No
Connect GitHub, Linear and Jira Yes Yes No No
Change notification settings and webhook tokens Yes Yes No No
See Billing and Usage; choose the plan Yes Yes No No
Rename the workspace Yes Yes No No
Manage company domains (Pro and Enterprise) Yes Yes No No
Change the workspace handle Yes No No No
Invite people, change roles, remove people Yes No No No
Transfer ownership Yes No No No
Leave the workspace No (transfer first) Yes Yes Yes
Delete the workspace Yes No No No

Members see Settings tabs they cannot change as read-only. Billing and Usage are hidden from members and viewers, and so are the GitHub and issue tracker sections of Connections.

Only the owner can invite.

  1. Open Settings → Members and choose Invite member (it is also in the workspace switcher).
  2. Enter their email and choose a Role: Admin, Member (the default) or Viewer. The dialog describes the role you pick. The owner role cannot be given by invitation.
  3. Choose Send invite.

They get an email with Accept the invitation. The invitation expires after 7 days. Until it is accepted it is listed under Pending invitations, where you can Revoke it. To send a fresh one after it expires, invite the same address again.

The invitation link opens a page to join the workspace:

  • If they have an account, they sign in with the address the invitation was sent to and choose Join, followed by your workspace’s name. A different address is refused.
  • If they are new, they choose Create an account with that address and confirm their email; the link brings them back to the invitation. A new account also gets a workspace of its own, which they can ignore.

Once they join, the dashboard opens on your workspace.

Joining takes a seat, so the page checks your plan’s seats first. If the workspace is full when they open the link (or press Join), it says so and that you can upgrade the plan or free a seat; nothing is created, and the invitation stays open until it expires, so the same link works once a seat is free. The same happens if the workspace has no active plan, with a request to restore billing instead.

Each person in the workspace uses a seat, whatever their role: owners, admins, members and viewers all count.

Plan Seats
Starter 5
Growth 20
Pro Unlimited
Enterprise Unlimited

The limit is checked when you send an invitation, and again when it is accepted, which is when the seat is taken. Pending invitations do not hold a seat, so you can have more invitations out than free seats: whoever accepts first gets the seat, and the next person is told the workspace is full (see Accepting). At the limit, a new invitation is refused with “Your plan includes 5 seats. Upgrade to invite more members.”, and the plan can be changed in Settings → Billing. Moving to a smaller plan never removes anyone. The Usage tab shows how many seats are in use.

A workspace without an active plan cannot invite anyone, or let anyone accept an invitation sent earlier.

Some people need to see results without joining: an agency’s client, a procurement team, a manager.

  • A share link to a scan. On a scan’s page, choose Create share link… (or Create Share Link under Share Links), pick when it expires (never, or after 1, 7, 30 or 90 days) and copy the link; it is shown only once. Anyone with the link sees that scan’s report, read-only and without signing in, and it uses no seat. Revoke stops it at once. Members, admins and the owner can create and revoke links; viewers see a scan’s links under Share Links but cannot make or revoke one. A link belongs to the workspace, not to the person who made it, so it keeps working if they leave.
  • Documents on request. Your Accessibility status page lets anyone ask for the readiness reports (and the VPAT on Pro and Enterprise). Owners and admins approve each request, and the link expires after the time they choose.
  • The public pages. The hosted statement and the status page need no link at all.

The owner changes a role with the role menu on the person’s row in Settings → Members, and removes someone with Remove member…. They lose access at once. The role menu offers admin, member and viewer; making someone the owner is a transfer of ownership.

When someone is removed:

  • Every API and MCP token they created in the workspace is revoked at once, including their live review panel connection. A token always acts for the person who created it, so integrations built on their token stop working (the API answers 401). Before removing someone who set up an integration, have an owner or admin create a replacement token. See Authentication.
  • Webhook tokens keep working. They belong to the workspace, not to a person.
  • Issues assigned to them stay assigned. Reassign them from the Issues list.
  • Their answers and verdicts in Review stay. Only a person changes an answer.

When someone’s role is lowered, their tokens can do only what the new role allows: a viewer’s token can only read, and the review panel needs a member or above.

The owner cannot be removed, and the owner’s role cannot be changed from the role menu.

The owner can hand the workspace to an admin or a member:

  1. Open Settings → Members.
  2. On their row, open the actions menu and choose Transfer ownership….
  3. Confirm with Transfer ownership.

They become the owner and you become an admin, in one step, and the activity log in Settings → Account records it. Ownership cannot go straight to a viewer: change their role to member or admin first. Only the new owner can transfer it back. The subscription belongs to the workspace, so billing carries on as before.

Anyone except the owner can leave. In Settings → Members, choose Leave workspace… and confirm. You lose access at once and, as when someone is removed, every API and MCP token you created in the workspace is revoked. The dashboard then opens your next workspace; if this was your only one, you get a new, empty workspace of your own, as at sign-up. To come back, the owner has to invite you again.

The owner cannot leave. Transfer ownership first; you are then an admin and can leave.

The owner can delete the workspace in Settings → Account, under Delete workspace, by typing its name to confirm. This cancels the subscription and permanently removes the workspace and all of its data.

On Pro and Enterprise, owners and admins can add your organisation’s email domain, such as acme.com, and then choose how people with an email there sign in, and whether they join this workspace when they sign up. It is the last section of Settings → Members. On Starter and Growth the section says it is on Pro and Enterprise.

  1. Under Company domains, enter the domain (the part of your work email after the @) and choose Add domain. Public email services, such as gmail.com or outlook.com, cannot be added. A workspace can have up to 10 domains.
  2. The domain shows Waiting for DNS, with a TXT record to add: its Name (_tac-verification.acme.com) and Value (tac-verification= and a code). Copy both into your DNS provider.
  3. Choose Check now. DNS changes can take a few minutes, sometimes an hour, to appear; check again until the domain shows Verified.

A domain belongs to one workspace. If another workspace has already verified it, the check says so and nothing changes. Once you verify a domain, other workspaces that added it but did not verify it lose it.

Choose How people at acme.com sign in:

  • Any method: as before.
  • Google: only with Continue with Google, and only with a Google account your organisation’s Google Workspace manages. A personal Google account made with a work address is refused.
  • Microsoft: only with Continue with Microsoft, using their work account.
  • Single sign-on (your identity provider): only with Sign in with SSO, through your organisation’s own identity provider. It appears once the workspace has a single sign-on connection (see Single sign-on).

The rule covers everyone with an email at the domain, in every workspace they belong to, not only this one. People whose email is at another domain, such as consultants and agencies, sign in as before. Someone at the domain who tries their password is told which button to use.

When you choose Google or Microsoft and save, everyone at the domain who is signed in now is signed out, apart from you on this browser, and signs in again the new way. It can take up to 5 minutes to reach a browser that is open. If your own email is at the domain, sign in once with that provider before you set the rule, so you can still sign in afterwards: the section asks you to if you have not.

Choose People at acme.com who sign up join as: Nobody joins (the default), Member or Viewer. People then join when they create an account with Microsoft, or with Google using an account your Google Workspace manages, or when they confirm their email after signing up with a password. People who joined that way keep any workspace of their own.

  • People who already had an account before the domain was verified are not added: invite them as usual.
  • Someone you remove is not added back, however they sign in again.
  • Joining never makes anyone an admin or the owner.

Remove stops both rules at once. To use the domain again, add it and verify it again. If the workspace moves below Pro, or its subscription lapses, the rules stop applying and the domains are kept; they apply again when the workspace is back on Pro or Enterprise. You can still remove a domain without the plan. The activity log in Settings → Account records each domain added, verified, changed and removed, and each person who joined by domain.

On Pro and Enterprise, owners and admins can connect your organisation’s own identity provider, such as Okta, Microsoft Entra ID, Google Workspace, OneLogin or JumpCloud, over OIDC or SAML. People at your verified company domains can then sign in with Sign in with SSO on the sign-in page, by entering their work email. It is the Single sign-on section after Company domains in Settings → Members. Verify a company domain first: single sign-on serves the people at your verified domains.

  1. Under Single sign-on, choose OIDC or SAML. The section shows what to enter at your identity provider when you create an application for The Accessibility Company: for OIDC the Redirect URI; for SAML the ACS URL, Entity ID and Metadata URL. Copy them across.
  2. Enter what your identity provider gives you:
    • OIDC: the Issuer URL, Client ID and Client secret. The issuer is the address your identity provider calls its issuer, such as https://acme.okta.com; the section reads the rest from it. The client secret is stored encrypted and never shown again.
    • SAML: paste its Metadata XML, or enter its Entity ID, Sign-in URL and Signing certificate. Your identity provider must sign its assertions and send the person’s email as the NameID or an email attribute.
  3. Choose Connect, then Test sign-in. It opens the sign-in page in a new tab; signing in there signs that browser in as that person, so use a private window to stay signed in as yourself.

Sign in with SSO starts on our sign-in page. Signing in from your identity provider’s own list of apps is not supported yet.

  • Your identity provider can sign in only people with an email at your workspace’s verified domains. Anyone else it sends is refused.
  • Someone who already has an account here with the same confirmed email is linked to it the first time they sign in this way.
  • A single sign-on session lasts 8 hours and is not extended. Someone you remove at your identity provider is out here at most 8 hours after they last signed in.
  • People at a domain set to Member or Viewer join this workspace when they first sign in with single sign-on.

To require it, set How people at acme.com sign in to Single sign-on (your identity provider) under Company domains. This needs someone to have signed in with Test sign-in first, and, if your own email is at the domain, you. Everyone at the domain who is signed in now is signed out, and signs in again with single sign-on; their password, Google and Microsoft no longer work for them.

Replace settings keeps the URLs your identity provider has. Leave the client secret blank to keep the saved one. If you move to another identity provider, people are linked again the next time they sign in.

Remove stops single sign-on and removes everyone’s link to it. It is not possible while a domain requires single sign-on: change that domain’s rule first. If the workspace moves below Pro, single sign-on stops and the connection is kept. The activity log in Settings → Account records each connection added, replaced and removed.

Two-step sign-in adds a second step after your password: a 6-digit code from an authenticator app on your phone. Each person turns it on for their own account; it covers every workspace they belong to.

You need an authenticator app, such as the one built into your password manager or your phone.

  1. Open Settings → Profile and find Two-step sign-in in the Security card. Choose Turn on and confirm your password.
  2. Scan the QR code with your authenticator app. If you cannot scan it, type the Setup key shown beside it into the app instead.
  3. Enter the 6-digit code the app shows and choose Confirm and turn on. Nothing changes until you do: if you stop here, your password alone still signs you in.
  4. Save your backup codes. Choose Copy codes or Download codes (.txt) and keep them somewhere safe, such as a password manager. They are shown only this once.

We email you when two-step sign-in is turned on or off for your account. From then on, signing in asks for your password and then the current code from the app. You have 10 minutes to enter it. After five wrong codes you start again from your password, and after ten in a row your account accepts no code for 15 minutes.

You get 10 backup codes. Each one signs you in once in place of a code from the app: on the code step, choose Use a backup code. When you are running low, or think someone has seen them, choose Create new backup codes in the same card and confirm your password. The old codes stop working at once.

Two-step sign-in protects sign-in with your password. If you choose Continue with Google, you are not asked for a code: that sign-in relies on Google’s own 2-step verification, which you set up in your Google account.

If you have only ever signed in with Google, you have no password here, so there is nothing to add a second step to. To use two-step sign-in, set a password first with Send reset email in the same card, then turn it on.

Sign in with your password and one of your backup codes, then turn two-step sign-in off and on again in Settings → Profile to set it up on your new phone. If you have no backup codes left, contact us. We will need to confirm it is you before we remove the second step.

Choose Turn off in the same card and confirm your password. Your backup codes stop working too.

In Review, Filter shows the checks that suit a Developer, a Designer or Content. It is a filter for dividing up the work, not a permission: who may answer is decided by the workspace role above. See Review.