Skip to main content
Sengol ships twelve role templates. Each grants a fixed set of permissions. Map your IdP groups to them, or assign them to local users.

Roles

approver is powerful despite its name. agents:admin lets it reveal captured raw traces, and sod:override lets it authorize same-person steps where policy allows. It cannot decide human-review items: that needs audit:write, held by member, developer and admin.
List the templates, with descriptions, as an admin:
You can also create organization roles. A caller can never grant a permission it does not hold itself.

Four-eyes controls

Several actions are four-eyes controls. Erasure and governed transitions always need two different people. An intake needs two only when your organization sets it: An agent must have an approved intake before it can be registered. Until then, the Agents page stays empty even while the agent writes evidence:
Agents page reading No agents to show, with a Submit an intake link

Agents lists the registry, not evidence. Unregistered agents do not appear.

A developer submits an intake at Govern → Intakes → New. An approver approves it from the intake’s page. Out of the box one approver is enough, and that can be the person who submitted it. An operator can require more people or a different person per risk tier (Set who approves intakes). The fields are described in the AI developer journey:
New intake form with agent id, use case, owner, risk tier and policies

A new intake. The agent id stays reserved while the intake is submitted and after it is approved or rejected. Only a withdrawn or expired intake releases it.

Interactive sign-in

Certifying an agent, promoting a judge, activating an obligation, and confirming, revising or approving an agent intake need an interactive sign-in: SSO, a password login, or sengol login --device approved in the Console. An sk_ API token or a CI credential is refused. To require MFA for the most sensitive steps, set SENGOL_SOD_REQUIRE_STEP_UP=true. It applies to objects at the CRITICAL risk tier. For MFA everywhere, enforce it at your IdP.

What is and is not signed evidence

Signed records cover evaluations, certifications, gold scores and erasure tombstones. Account administration is not signed: creating users, assigning roles, SCIM changes and break-glass sign-ins leave logs, not records an auditor can verify offline. Keep your IdP’s own audit log for those.