Client projects
One workspace for your team, a project for each client
Running audits for other people is a different problem from running them for yourself. Each client site gets its own project, with its own scans, findings, schedule and report history - and what a client sees is decided by what you share with them.
What is separated, and from whom
A workspace is the boundary everything else hangs off. Projects, scans, findings, schedules, report history and API keys all belong to one, and nothing crosses between workspaces - a query that could not name the workspace is a query that returns nothing. An account owns one workspace; the team is invited into it.
Inside it, clients are separated by project, not by permission: every member, a client viewer included, can read every project in the workspace. A client who should see only their own site gets a read-only share link to their report, not a seat.
How seats are counted
Every member consumes a seat, whatever their role - a read-only client viewer, who reads every project, costs the same as an admin. A client who should see only their own site needs no seat at all: send them a share link.
Stated plainly because the opposite was once advertised. A read-only share link expires, can be revoked, and needs no account on the other end.
Roles
Five roles, and what each one may do
The read-only role lets somebody be shown the work without being able to change it - all of the workspace's work, so it suits people who may see every project.
Owner
Holds the subscription. The only role that can close the workspace or transfer ownership.
Admin
Everything an owner can do except deleting the workspace - billing included: projects, schedules, members, the plan and the readiness sign-off.
Agency
Runs the work across the workspace's projects without taking on the workspace's own administration.
Member
Starts scans, reads findings and marks them fixed, not applicable or ignored.
Client viewer
Read-only. Sees every project in the workspace, changes nothing, and cannot see the member list. For a client who should see only their own site, use a share link.
Seats and projects by plan
Read from the table the server enforces, not written out here - the two drifted once and the page sold fifteen seats where the product allowed ten.
1
1 projects
2
3 projects
5
10 projects
8
15 projects
15
25 projects · white-label reports
Custom
Custom projects · white-label reports
Start
One audit, then a project per client
The free audit needs no account. The workspace is worth setting up once you know what you are going to put in it.