Active development · Integration coverage varies

Permissions should follow the member into the server.

Nexus is being built as the identity, entitlement, and runtime-permission bridge between configured Discord roles, Nexus rules, and ASRP's FiveM resources. Individual bridges and runtime capabilities become authoritative only as they are implemented, tested, and enabled.

Back to Nexus hub ASRP Discord

Entitlements

From role sources to runtime capabilities.

Nexus can map stable Discord guild and role IDs plus Nexus conditions into the permissions a member needs while connected to FiveM.

Departments & jobs

Department membership, ranks, jobs, grades, duty requirements, certifications, and character conditions can contribute to runtime access.

Assets & capabilities

Vehicle, EUP, weapon, ped, radio, queue, CAD, and administrative capabilities can be granted from the same effective-permission model.

Live changes

Role or permission changes are intended to synchronize live where practical so a reconnect is not always required.

Compatibility

Native Nexus permissions without breaking existing resources.

New ASRP resources can use a native Nexus permission API, while an ACE compatibility bridge can expose appropriate runtime principals and ACE assignments for existing FiveM resources during migration.

Discord source

Configured guild roles contribute trusted membership and role signals.

Nexus rules

Department, rank, certification, duty, user, environment, and explicit grant/deny logic resolve effective access.

Runtime delivery

FiveM receives only the capabilities the member is authorized to use.

Audit & explain

Authorized administrators can see why a capability was granted or denied and track material changes.

In-game Nexus UI

Administration and utility tools powered by the same permissions.

ASRP does not need a separate unrestricted menu with its own unrelated permission model. Nexus can expose only the actions a member is authorized to use as those in-game capabilities are implemented.

Administration

Warnings, kicks, bans, notes/history, spectate, freeze, teleport, configured heal/revive, announcements, safe resource operations, diagnostics, and other approved actions.

Department tools

Duty, department actions, CAD quick actions, status controls, and other role-specific utilities can be integrated into the same menu framework.

Player utilities

A separate normal-player utility surface can provide approved personal, vehicle, and roleplay functions without exposing staff tools.

Foundation