Define partner scopes from concrete API operations
A single automation scope permits every operation in the organization.
- Focused work estimate
- 1h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Authorization design
Estimated field mix
- Security70%
- API design30%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional operations platform lets customers connect automation clients. Broad API keys and inconsistent tenant checks make delegated access difficult to review.
Setup prerequisites
- Create a local authorization service and synthetic partner clients for two organizations; generate disposable test credentials only.
Preceding work
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- Map scopes to specific operation classes.
- Separate read, write, and administrative authority.
- Document unsupported scope combinations.
Implementation constraints
- Do not derive permissions from client-provided role names.
Verification to include
- Authorize a read-only synthetic client.
- Deny a write under the read-only scope.
Deliverables
- Partner scope matrix.
Rollout and recovery
Review least-privilege defaults before issuing credentials.
Value of the work
For the engineer: Practice delegated authorization, resource scoping, and secure public API ergonomics.
For the team: Provide usable partner access that remains least-privilege and revocable.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.