Temporary elevation
High-risk access can be granted for a limited period instead of remaining permanently assigned.
Nexus overview · Security & audit
Powerful tools should always be attributable.
Nexus is designed around least privilege, clear effective permissions, strong separation between tenant and platform administration, and detailed auditing of consequential actions.
Least privilege
Simple presets on top. Narrow controls underneath.
Routine access should be easy to assign, while sensitive capabilities can still be scoped to a specific tenant, environment, department, rank, module, action, record type, user, role, or group.
Effective-permission viewer
Authorized administrators can see exactly which Discord role, Nexus group, department rule, override, or deny produced a capability.
Safe high-impact actions
Reasons, confirmations, step-up controls, and stronger checks can be required before sensitive changes are accepted.
Audit trail
Enough context to reconstruct what happened.
Important events should not be reduced to a vague log line. Nexus is intended to preserve the context needed to review permissions, decisions, administration, integrations, and operational changes.
Who acted?
User, bot, worker, service account, integration, or approved automation.
Why were they allowed?
The effective permission path that authorized the action.
What changed?
Target, action, reason, relevant before/after state, result, and linked workflow context.
Where did it occur?
Tenant, environment, Discord guild, FiveM instance, Nexus module, CAD record, or platform service.
Platform control plane
Nexus staff access is separate from community administration.
Platform identities such as owner, administrator, engineering, security, release management, support, and audit roles are intended to have environment- and service-scoped permissions rather than silent unrestricted access to every tenant.
Support access
Tenant support should be explicitly controlled, preferably approval-based or break-glass when emergency access is required.
No silent impersonation
A permission simulator can show what a user or role would see without pretending to become that user.
Machine identities
CI/CD, workers, integrations, and bots use scoped service identities and credentials rather than shared human accounts.