Give clients a viewer seat to see their test results
A viewer sees projects, tests, runs and the proof, and changes nothing. When to invite a client as a viewer, when a share link is enough, and when to split workspaces.

Some clients want to look for themselves#
Most clients are happy with a link in a monthly report. Some want to see the checks whenever they like: a marketing manager who wants to know the form is fine before a campaign, an in-house developer who wants the replay of a failure.
The viewer role#
Testsy has four roles. From team and roles:
| Role | Can |
|---|---|
| Viewer | See results only: projects, tests, runs, the proof. For clients and managers. Can ask to be emailed a run's result. |
| Member | Write and run tests, sign-in accounts, schedules, share links. |
| Admin | Also manage the team, API keys, integrations, billing and settings. |
| Owner | Everything; one per workspace. |
Invite from Team → Invite someone with their email and the role. The invitation works for 7 days. Inviting people is on paid plans, up to the plan's member count.

A viewer sees the whole workspace#
A viewer sees every project in the workspace. If you test several clients in one workspace, a client viewer would see the other clients too. So:
- One client, or clients who may see each other's checks: a viewer seat in your workspace is fine.
- Clients who must not see each other: give that client their own workspace (each workspace has its own projects, team, plan and billing) and invite them as a viewer there. See one project per client.
- Just one result: a share link shows one run and nothing else, with no account needed.
What a viewer can do#
Open runs, watch replays, read each check and its value, and tick Email me the result on a run that is going. They cannot run tests, edit them, see sign-in passwords (nobody can) or change settings. Emails the runs received are shown inside the workspace (share links leave them out), so check what your tests receive, such as reset links, before inviting someone outside your agency.
This post is part of Find the bug before your client does.
Filed underWebClient sitesSharing and alerts