Write the partner permission matrix from existing routes
The portal has three roles, but engineers infer permissions from page names. A read-only agent can discover an Edit route that was added for partner administrators.
- Focused work estimate
- 2h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Threat modeling · Authorization design · API inventory
Estimated field mix
- Security80%
- System design20%
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 manufacturing company shares purchase-order documents with partner organizations. Buyers, partner administrators, and read-only agents use the same API. Recent support reports suggest list filters and background downloads disagree about who may see an order.
Setup prerequisites
- HTTP APIs
- Session authentication
- Tenant-scoped data access
Preceding work
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- Inventory order, document, invitation, and export actions at route and service boundaries.
- Define allowed actions for buyer, partner administrator, and read-only agent.
- Mark unspecified combinations as denied and identify ownership or tenant conditions.
Implementation constraints
- A hidden button is not an authorization rule; include non-UI callers.
Verification to include
- Map each fixture route to exactly one documented action.
- Show explicit denials for agent edits and cross-partner document reads.
Deliverables
- Permission matrix and route-to-action inventory
Rollout and recovery
Review the matrix before enforcing new checks; record intentional compatibility changes for test clients.
Value of the work
For the engineer: Practice authorization as a service-level invariant, including revocation timing, concurrent membership changes, and asynchronous data delivery.
For the team: Inspect a concrete record of cross-organization denial, least-privilege decisions, and access-recovery behavior using fictional partner records.
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.