Accessibility Teams

Accessibility teams are named groups of users inside your organization. Scans get shared with one or more teams rather than with individual users, so membership changes automatically propagate.

Who can manage teams

Team creation, renaming, deletion and membership are org owner / admin only. Members of a team can see teammates but cannot add or remove anyone, and a plain member cannot browse or search the org's teams at all.

Creating a team

Sidebar → Teams (Accessibility workspace).
Click Create Team.
Enter a Team Name — 4 to 40 characters, unique inside your organization (e.g. Frontend Platform).
Optionally search org members by name or email and add them straight away.
Click Create Team.

TestKase assigns the team a Team ID (ATM-1234) and a two-letter nickname used in scan badges, both derived automatically from the name. The nickname is regenerated if you rename the team — you cannot set it yourself.

Adding members

From the Teams table, click the member avatars on a row (or its Manage Members action):

Search org members by name or email.
Toggle each user's membership; the modal lists the current members and what has changed since you opened it.
Click Save — the button stays disabled until something changes.

Members are emailed when they are added and when they are removed.

What the Teams table shows

Team Name, Team ID (ATM-1234), Team Members (initials avatars), Created On, and row actions.

There is no per-team page and no list of the scans shared with a team. To see which teams a scan is shared with, open the scan and use Share with team — and note that only the scan's creator can do that.

Deleting a team

Deleting a team:

Removes the team's membership records.
Removes the team from any scan it was shared with (the scan itself stays; only the share is dropped).
Retires the team's ATM- ID — it is not recycled for a new team.
Is destructive and cannot be undone.

Only admins / owners can delete teams.

Best practices

Create teams along responsibility lines, not project lines — e.g., Frontend, QA, Compliance, not Redesign 2026.
Keep teams small enough that notifications stay relevant (3–15 members is a sweet spot).
Add the scan creators themselves to the teams they need to share with — sharing only offers teams the creator belongs to.