One ASRP member identity across connected systems.

Nexus is built around Discord as the authoritative account identity, with configured Discord memberships and roles combined with Nexus groups, departments, ranks, certifications, duty state, temporary grants, and explicit permission rules. Availability of individual login and permission features depends on the current deployment state.

Open Nexus Back to Nexus hub

Authentication

Discord sign-in, not another password.

Nexus is designed so members authenticate with Discord and return to the same Nexus identity on web and future clients. Mobile login is intended to use secure Discord OAuth flows rather than requiring a nearby computer.

Discord-authoritative

Stable guild and role IDs are used as permission sources rather than relying on role names that can change.

Multiple communities and guilds

Configured Discord guilds can contribute to one Nexus member's effective access without creating separate Nexus accounts.

Returning devices

Biometric, passkey, device-unlock, or short-lived pairing methods can protect returning sessions while Discord remains the account authority.

Permission engine

Easy presets with granular control underneath.

Nexus should be simple to administer for routine access while still supporting narrow controls when a sensitive workflow needs them.

Sources

Discord roles, Nexus groups, department, rank, certification, duty, character, user-specific rules, and environment.

Logic

ANY, ALL, and NOT conditions; inheritance; source priority; explicit allow; configured deny precedence; and temporary permissions.

Scope

Tenant, module, action, record type, department, user, role, group, environment, and other configured data scopes.

Explanation

An effective-permissions view should show exactly what granted or denied each capability instead of making administrators guess.

Why it matters

Different members should see different tools.

A civilian, recruit, dispatcher, trooper, fire officer, department commander, developer, and Homeland Security leader have different responsibilities. Nexus navigation and actions are intended to reflect that automatically.