What is real here: the PR-gate policy is the actual sovra-policy.json the CI gate reads. The tracker profile is saved in this browser only, to prefill Publish. Roles are read live from the enforcement layer.
Enter your API key in the field at the top of the page to load your policy and roles.
Your tenant's own gate policy, stored server-side. The CLI's sovra gate reads a local sovra-policy.json; export this one there to use the same rules in CI.
0 means no minimum. A scan scoring below a floor fails the gate.
Saved in this browser's local storage only. It is never sent to Sovra's server except when you click Publish tickets on a scan. It prefills the Publish panel so you stop retyping it.
Live from the enforcement layer (governance.ROLES), not a separate ACL that can drift out of sync. Explicit-actor forms elsewhere ask you to pick one of these; the server re-checks it on every call regardless of what the form allowed you to select.
| Role | Scope | May invoke |
|---|