TestKase
TestKase
|Docs
Accessibility TestingCollaboration

Sharing Scans

Share scans with accessibility teams so everyone works from the same report.

Sharing Scans

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

  1. Open any completed scan (or use the row action in the Website Scanner list).
  2. Click Share with team.
  3. Select one or more accessibility teams from the list.
  4. Click Share.

Screenshot (TODO): Share with team modal with team list and selected state

The scan row in the list now shows a badge for each team it's shared with, and the report appears in each team member's shared-with-me list.

🚧 Coming soon — a notification when a scan is shared with your team. Sharing today updates access silently; team members will see the scan in their shared list but won't get an email or in-app ping about it yet.

Who can share

  • The scan's creator can always share.
  • Any member of a team the scan is currently shared with can share it with additional teams.

Who can see a shared scan

Members of any team the scan has been shared with can:

  • Open the report and read every part of it — summary, conformance matrix, issue details, and element inspection.

Re-scanning is owner-only: only the scan's creator can re-run it (the API returns a 403 for everyone else). Shared viewers also cannot delete or edit the original scan.

🚧 Coming soon — inline comments and @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:

  • Uncheck a team to revoke its access.
  • The scan row's badge for that team disappears immediately.
  • Existing notifications are not retracted, but the team can no longer open the report.

Shared-with-me scans

From the scan list's scope filter:

  • Mine — only scans you created.
  • All — scans you created + scans shared with any team you belong to.

Filter further by team from the team multi-select to focus on one team's queue.