Access Control & Security Tiers
The Strategic Hub manages digital resource isolation through hierarchical user clearance levels, custom role groups, and automated request verification pipelines.
Clearance Level Matrix
| Platform Permission Key | Staff | Officer | Director | Chief |
|---|---|---|---|---|
files:read View and download files | Group Only | |||
files:write Upload and edit files | Group Only | |||
files:delete Soft-delete or purge file versions | Group Only | Group Only | ||
files:classify Change security classifications | Group Only | Group Only | ||
users:read View corporate user directory | Group Only | |||
users:manage Create, update, and toggle users | Group Only | Group Only | ||
users:delete Permanently delete user accounts | Group Only | Group Only | ||
governance:approve Authorize governance requests | Group Only | |||
governance:reject Decline governance requests | Group Only | |||
admin:access Access administration panel | Group Only | Group Only | ||
shares:manage Manage document sharing records | Group Only | Group Only | ||
audit:read View compliance audit ledger logs | Group Only | |||
storage:manage Configure global/user storage limits | Group Only | Group Only | ||
config:read Read global system configuration | Group Only | Group Only |
Security Classification Tiers
Open/Unclassified level. Standard documentations, resources, and shared corporate memos. Available to all system users by default.
Restricted internal level. Department files, asset references, and standard internal guides. Access requires supervisor approval or direct ownership.
Confidential clearance level. Financial budgets, project plans, and employee records. Direct sharing requires the recipient to have Director clearance or custom group override.
Secret Board level. Strategic plans, board files, and critical system configurations. Access limited to Director and Chief tiers, audit-tracked extensively.
Intranet Security Implementations
1. Classification Transition Verification
When a user requests to change a file classification rating, the backend performs array index lookup validation. It verifies that upgrade requests choose a target clearance strictly higher than the current state (e.g. from Terhad to Sulit). Downgrade requests are flagged as high risk and require senior Director authorization before database execution.
2. Soft Deletions and Lifecycle Recovery
When files or folders are deleted, they are not initially purged. The system executes soft deletions by writing a timestamp to the `deleted_at` column. Trashed files remain in the DB and are hidden from active file viewports. File owners can restore their items, preserving sharing relationships. Permanent hard deletions require Chief Administrator authentication.
3. Locking Rules and Folder Relocations
To maintain document integrity during drafting, files can be locked. Once locked, other collaborators cannot rename, move, edit, or delete the file. When relocating folders, the system executes recursive parent checks to prevent circular directory structures (e.g. attempting to move a parent directory into one of its subfolders).
File Locking Rules
Files can be locked to prevent concurrent write overrides. Standard staff can lock a document they own or edit. Higher authorization tiers (Directors/Chiefs) have direct bypass capability to override or release locks set by staff.
Immutable Activity Trails
Every file access (upload, download, edit, classification shift) generates a system audit log. Logs store caller session tokens, remote address IPs, action verbs, target entity hashes, and timestamps, serving as a non-repudiation ledger.