Your key
Scopes
A key carries scopes and an operation checks its scope before it does anything else. A call never widens the key that made it: ask for an approval you do not hold and it is refused rather than escalated.
- approvals:read
- Read approvals and their recorded basis — scope, jurisdictions, artwork hash, evidence snapshot, decision. Separate from approvals:write because seeing who approved what is a different authority from approving.
- approvals:write
- Grant or withhold an approval within the scope the principal actually holds. Never widens that scope.
- billing:read
- Read plan, usage and meter state.
- billing:write
- Change plan or manage billing configuration.
- counterparties:read
- Read counterparties and the evidence they have supplied.
- counterparties:write
- Invite counterparties and manage their obligations.
- evidence:read
- Read evidence on file and the outstanding requests against counterparties. Separate from evidence:write because reading what a supplier owes is routine and uploading on their behalf is not.
- evidence:write
- Submit evidence against a counterparty obligation.
- findings:read
- Read findings raised by a run.
- findings:write
- Waive or annotate a finding. A blocking finding can only be waived by a principal holding the approval authority for that market.
- manifests:read
- Read packaging manifests and their per-market matrices.
- manifests:write
- Create and amend manifests. A manifest in an approved state cannot be amended without superseding it.
- packs:read
- Read rule packs and the rules inside them. Read-only: packs are authored in the repo, never through the API.
- products:read
- Read this tenant's products and their classification.
- products:write
- Create and amend products. Amending a classified product re-opens the checks that depended on the classification.
- releases:read
- Read print releases and verify one from its public reference.
- releases:write
- Cut a print release. Refused unless every blocking finding for the target markets is resolved or waived.
- runs:read
- Read compliance runs and their results.
- runs:write
- Start a compliance run against a manifest.
What this page will not do
It fires reads. It will not fire a write while it points at production: a Send button next to a description of an operation that revokes an approval is one mis-click from changing a real tenant, and the copyable request above each write is the same call without that hazard. Writes become sendable when the sandbox surface exists and a mistake costs nothing.