Authorization
Authorization decides what an identified person or service may read, change, or run. It's often shortened to AuthZ.
Another example
A project member can edit tasks, but only the owner can manage billing.
Main parts
- 01Identity or input
- 02Policy or transformation
- 03Stored result and audit evidence
Use it when
Check permission on the server for every protected resource and action.
Do not use it when
Never treat a hidden button or a client-side role as real permission control.
Name used in code
RBAC / ABAC / policy check Before you ship
Check contracts and invariants, authorization, and input limits. Test retries, one-time effects, timeouts, and partial failures. Verify data integrity, compatibility, monitoring, recovery, and rollback.
Outcome: Design or review Authorization for this system while keeping data correct, secure, and easy to operate. User context: A project member can edit tasks, but only the owner can manage billing. Technical concept or control: Authorization. Why it fits: Check permission on the server for every protected resource and action. Do not use it when: Never treat a hidden button or a client-side role as real permission control. Engineering requirements: Define inputs, outputs, contracts, and rules that must always hold. Set authorization and input checks. Define failures, timeouts, retries, one-time effects, data moves, and compatibility limits. Operations: Add useful signals and logs that hide sensitive data. Set capacity limits and write an operator guide. Test recovery and rollback. Acceptance criteria: Contract and failure-path tests pass. Data and authorization rules still hold during retries and partial failures. Check performance limits, monitoring, recovery, and rollback. Evidence and limits (evidence boundary): No single official standard controls the whole term. Its meaning may change across teams, platforms, or frameworks. Unknowns to confirm: Where the code runs, data stores, traffic shape, consistency needs, and the security boundary. Also confirm the compatibility period, service goals, and rollback limits.
Check this request
Review the current use of Authorization. Definition: Authorization decides what an identified person or service may read, change, or run. It's often shortened to AuthZ. Release checks: Check contracts and invariants, authorization, and input limits. Test retries, one-time effects, timeouts, and partial failures. Verify data integrity, compatibility, monitoring, recovery, and rollback. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.