Identity and Authorization
Authentication establishes who is present. Authorization decides whether that identity may perform a specific action on a specific resource in the current scope.
Required Checks
- Confirm the session is valid before loading private content.
- Resolve the active platform or workspace context on the server.
- Enforce the permitted role or capability for each action.
- Check ownership or membership before reading or mutating an object.
- Recheck authorization for downloads, exports, background operations, and APIs.
UI affordances can explain permissions, but they are not security controls. A direct request must receive the same decision as a button-driven request.
For sensitive changes, preserve enough evidence to identify the actor, operation, target, outcome, and time without logging secrets or unnecessary personal data.