Sharing Scans
Share scans with accessibility teams so everyone works from the same report.
Sharing a scan lets every member of the chosen team(s) open the report — without needing a separate link or access request.
Share a scan
- Open any completed scan you created (or use the row action in the Website Scanner list).
- Click Share with team.
- Select one or more accessibility teams from the list.
- Click Share.
The scan row in the list now shows a badge for each team it's shared with, and the report becomes visible to those teams' members under All scans.
Who can share
Only the scan's creator can share a scan, unshare it, or see which teams it is shared with. Team members who can view a shared report cannot re-share it — they don't get the share control at all.
The creator can only share with teams they belong to themselves; the picker is built from your own team memberships. If you belong to no teams the picker is empty and reads "No teams available. Ask your admin to add you to a team." — a plain member cannot browse or search the organization's other teams, so you have to ask an admin to add you.
If you select several teams at once, they are processed one by one: a team you are not a member of is rejected on its own and the rest still go through. A team the scan is already shared with is skipped rather than duplicated.
What a recipient sees
There are no public share links. A shared report is not a URL you can forward — there is no token, no expiring link and no "anyone with the link" mode anywhere in accessibility scanning.
To open a shared report, the recipient must be signed in to TestKase, be in the same organization, and be a member of a team the scan was shared with. Someone without an account, or in another organization, cannot be given access at all — invite them to the organization first, then add them to a team.
Who can see a shared scan
Members of any team the scan has been shared with can:
- Open the report and read the summary, the WCAG conformance matrix, the issue list, every issue's detail, and the History tab.
- Include the scan in a consolidated report alongside their own.
Two parts of the report do not travel with the share:
- Page snapshots. Element inspection is creator-only — the snapshot request checks that you created the scan, so a shared viewer sees the issue detail without a snapshot and without the red outline.
- Version comparison. Compare reads only runs you created; see Comparing & consolidating.
Re-scanning is creator-only: only the scan's creator can re-run it (the API returns a 403 for everyone else). Shared viewers also cannot edit the scan, and they cannot delete it — neither can an org admin or owner. Only the creator can delete a scan.
@mentions on individual issues. There's no in-report discussion thread yet; today, collaboration happens by sharing the report and coordinating in your own tools.Unsharing
From the share modal (creator only):
- Uncheck a team to revoke its access.
- The scan row's badge for that team disappears immediately.
- The team can no longer open the report.
Revoking is immediate and total — a former viewer loses the report, its history and its exports at once. Nothing they already downloaded is recalled, and they are not told access was removed.
Deleting a team has the same effect on every scan shared with it. See Accessibility teams.
Finding scans shared with you
From the scan list's scope filter:
- My scans — only scans you created.
- All scans — scans you created + scans shared with any team you belong to.
There is no separate "shared with me" list; shared scans appear under All scans with a team badge. Filter further by team from the team multi-select to focus on one team's queue.