For ops teams
Roles and permissions
The right people should see reports, and only the right people should act on them. Four roles keep it that simple.
- AdminEverything, including keys and seatsAdverse action
- ReviewerReads reports and decidesAdverse action
- Read-onlySees reports, can’t actView only
- Agent keyStatus-only by defaultScoped
Four roles, one table.
Give each person the seat that matches what they decide.
Every person on your team gets a seat with one role. Agents and services get keys instead of seats. Here is what each can do.
| Role | Start a check | Read reports | Export | Take adverse action | Manage keys and seats |
|---|---|---|---|---|---|
| AdminRuns Roster for your team | Yes | Yes | Yes | Yes | Yes |
| ReviewerReviews reports and decides | Yes | Yes | Yes | Yes | No |
| Read-onlyNeeds to see, not act | No | Yes | No | No | No |
| Agent keyAn agent or a service | With checks:write | With reports:read | No | No | No |
Agent keys get only the scopes you give them.
Status-only by default. Reading a report is a scope you add on purpose.
An agent key starts status-only: checks:write and checks:read, so it can start a check, see where it stands and explain a delay with explain_status. It can’t open a report. That needs reports:read, which most teams keep for their ops tools.
No scope lets a key take adverse action or sign consent. What agents can and can’t do.
| Key | Scopes |
|---|---|
sk_test_status_…Your agents | checks:write, checks:read |
sk_test_…Onboarding service | checks:write, checks:read, webhooks:manage |
sk_test_ops_…Ops tools | checks:read, reports:read |
A person approves every adverse action.
On the report page, from an admin or reviewer seat. Roster enforces it.
Deciding not to onboard a provider, or to remove one, starts on the report page and waits for a person on an admin or reviewer seat. A read-only seat can’t take the step, and neither can any key, whatever its scopes.
Roster prepares the letters and the dates; the person on that seat approves, sends and decides. When a record shows up.
Adverse action
Who can take the step
- A person on an admin seat
- A person on a reviewer seat
- Never a read-only seat
- Never an API key or an agent
Who gets which seat.
A starting point. Your admin can change it any time.
- Admin: the ops or trust lead who owns screening, and one backup.
- Reviewer: the people who read reports and make provider decisions.
- Read-only: support, finance or anyone who needs to see a status or a report, not act on it.
- Agent key: each agent and each service, with its own key and the fewest scopes it needs.
Set up your team in the sandbox.
Tell us how your ops team works today. Sandbox keys right away if your engineers want to try it first.
- A report page and PDF for every check, signed by the analyst who reviewed it, with a way to message them from the report page.
- Status in the dashboard and by webhook. explain_status says which court a check is waiting on.
- Every possible record is confirmed at the court before it’s reported, on every package.
- Notices and letters prepared with the dates filled in, behind an approval gate only admin and reviewer seats can pass.
- Your team reviews, sends the letters and makes every decision.
Reviewed November 6, 2026 by Ben Drellishak, Owner.