docs: consolidate repository guides and preserve audit history
This commit is contained in:
@@ -1,43 +1,5 @@
|
||||
# Authorization
|
||||
# Authorization and tenancy
|
||||
|
||||
## Purpose
|
||||
Tenant-owned records carry `OwnerUserId` directly or through a parent. `JobTrackerContext` applies global owner filters with deny-on-null semantics; services and background work use explicit owner checks when they bypass request-scoped filters. Admin users access user management, audit, and system readiness surfaces through Identity roles.
|
||||
|
||||
Control access to resources.
|
||||
|
||||
---
|
||||
|
||||
# User Isolation
|
||||
|
||||
A user must only access:
|
||||
|
||||
- Their jobs.
|
||||
- Their CV.
|
||||
- Their files.
|
||||
- Their emails.
|
||||
- Their settings.
|
||||
|
||||
---
|
||||
|
||||
# Admin Role
|
||||
|
||||
Admins may access:
|
||||
|
||||
- System settings.
|
||||
- Provider configuration.
|
||||
- Monitoring.
|
||||
|
||||
---
|
||||
|
||||
# API Rules
|
||||
|
||||
Every protected endpoint must verify:
|
||||
|
||||
1. User identity.
|
||||
2. User permission.
|
||||
3. Resource ownership.
|
||||
|
||||
---
|
||||
|
||||
# Never Trust Frontend
|
||||
|
||||
The backend must enforce permissions.
|
||||
A browser route or hidden control is not an authorization boundary. Add server-side authorization and an ownership regression test for every new resource or endpoint.
|
||||
|
||||
Reference in New Issue
Block a user