List support actions with required permission and disclosure level
Support agents share an admin role because nobody has separated read diagnostics from account-changing actions.
- Focused work estimate
- 1h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Authorization design · Least privilege
Estimated field mix
- Security100%
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 support console can reveal protected account settings and run repairs. The team needs bounded elevation, clear reasons and durable records of what happened.
Setup prerequisites
- Create synthetic support actors and organizations.
- Implement a local authorization boundary and append-only audit store.
Preceding work
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- Classify each action by permission and exposed fields.
- Default unknown actions to denied.
- Keep read-only diagnostics separate from mutation authority.
Implementation constraints
- Use six concrete fictional support actions.
Verification to include
- Map an allowed diagnostic read to its minimal permission.
- Attempt an unlisted action and deny it before data access.
Deliverables
- Support permission matrix
Rollout and recovery
Review the matrix before enabling new actions; retain unknown operations as disabled.
Value of the work
For the engineer: Practice privileged workflows, denial paths and audit integrity.
For the team: Review accountable support operations without unnecessary access to customer data.
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.