Only Owners and Admins (the Manage projects permission) can read or change this page. Everyone else sees a read-only note and no controls.
Detector packs
The Detector packs card lists one row per pack with what it checks, its Mode, and the number of checks (with how many of them are still in preview).
When you choose On for a pack that is not on yet, Zespan asks Turn on ? first and tells you that findings the pack proves will show to your team and can become Issues. Choose Turn on to confirm or Cancel to leave the mode as it was.
If detectors are off for the whole project, the card says Detectors are off for this project, so no pack runs. and no pack’s mode takes effect. That setting is outside this page; on a self-hosted deployment your operator sets it (see Issues → Kinds of issue).
Confirm your tools
Some checks cannot tell what a tool does from its name alone, so Zespan suggests a role for each tool it has seen in your project in the last 7 days (up to 500) and lets you confirm it. The Confirm your tools in card is for the pack you pick in the selector at its top right. It lists only packs that have roles to confirm. A pack that reads tool names and results directly shows Nothing to confirm, and a project with no tool calls in the last 7 days shows No tools yet. Each row shows the tool, the Suggested role, What confirming changes, and the actions.1
Pick the pack
Use the pack selector. A confirmation belongs to the pack you are looking at: the same tool can have a different role in another pack, and the other pack does not use it.
2
Read the suggestion
Zespan suggests a role from the tool’s name and description. A tool with no suggestion reads No suggestion. Tools with a risky role are listed first.
3
Confirm, change, or reject
Choose Confirm to accept the suggested role. Choose Change to pick a different role from the pack’s list. Choose Not this to say the suggestion is wrong; the tool is then marked Not this and no role is used for it.
4
Confirm risky roles one at a time
A role that can move money, delete, send, post publicly, write to memory, approve, block or escalate is risky. Confirming it opens Confirm for this tool? with the checks it changes. Choose Confirm in the dialog; each risky tool needs its own confirmation, and the dialog is shown again for the next one.
A confirmation is per pack and per tool definition. If a confirmed tool is renamed or its parameters change, its row shows Changed since you confirmed and you confirm it again; until you do, the pack does not rely on it. The last role you confirmed is the one suggested again.
What confirming changes
Each role lists the checks it affects, and a finding a check reports has a confidence of flag (a signal), likely or proven. Only proven findings can become Issues. Without a confirmed role, a check stays at the lower confidence. A row with no listed change shows Nothing changes yet. The checks the catalogue lifts today are: Checks for AI products
The other roles in this pack (reads private customer data, looks up a claim, a booking or a ticket, reads content from outside, and asks for an approval or confirmation) can be confirmed, and show Nothing changes yet.
Marketing and analytics checks
Fields
The Fields card for the selected pack shows where in your tool calls each value the pack reads can be found. It is used by Checks for AI products (order total, amount, price, floor price, cost, reported figure, subtotal, discount percent and tax rate percent), Customer support checks (order total and refund amount) and Data analysis checks (the data as-of date). A pack with nothing to map shows No fields.
Choose Confirm on a row to save its path. A field you have not confirmed keeps the check that reads it at likely; confirm the field and the tool role together to let the check reach proven.
New checks in preview
These checks were added in November 2026. They run in Preview only, whatever the pack’s mode, until each one passes its accuracy tests on data its builders never saw and on real transcripts. Their findings stay out of Issues until then.Strongest result is the most a finding of that check can be. Without the confirmations in the fourth column, a finding stays at likely or below. Checks marked likely can never become Issues on their own.
Four more packs: E-commerce, Sales and CRM, Scheduling, Coding agent
These four packs are on by default for every project, but every one of their checks runs in Preview until it passes its accuracy tests, so nothing they find reaches Issues yet. Turn a pack Off on this page if you do not want its previews. Like the other packs, they read the spans Zespan stored and never call a model.
What each pack’s roles mean, for Confirm your tools:
Without confirmed roles and fields a finding stays at likely at most. Time zones whose abbreviation has several meanings (IST, CST, BST) are skipped, not guessed. Test output that was cut at the storage limit, or in a format outside the list above, gives no finding.
API
The page uses these project routes. They need a dashboard session and the Manage projects permission. See the API reference.
Mode changes, tool confirmations and field confirmations are written to the audit log.
Next steps
- Issues — where findings a pack proves show up once the pack is On
- Findings — what a pack’s checks report on a trace
- Instrumentation — which inputs your traces recorded, so checks have what they need
- Traces — open the trace behind a finding