Skip to main content

Ranks and permissions

Ranks mirror the in-game alliance hierarchy. R5 and R4 run alliance operations; owner-only account and lifecycle controls remain reserved. R3 and below get a useful member workspace — My Week, assignments, targets, private trends, standings and their own history — without controls that drive the alliance. Narrow capabilities can grant specific jobs without promoting someone to R4. The same permission rules are enforced in the UI and on the server.

Permission matrix

● = full access, ◐ = restricted, — = no access. Hover or tap any row with a note for context.

ActionR5R4R3 / R2 / R1
Edit alliance settings (DS day, server, branding)
Set or change Performance Expectations
Generate and share invite linksThe Recruiter capability also grants this specific action. Rotating an existing code remains owner-only.
Add or remove members
Promote / demote membersR4 can only set ranks R3 / R2 / R1
Create / edit / cancel Desert Storm matchesThe Event manager capability also grants this specific workflow.
Edit DS rosters and battlefield assignmentsThe Event manager capability also grants this specific workflow.
Record DS results and attendanceThe Results recorder capability also grants this specific workflow.
See Officer Pulse / Metrics
Capture event rankings (VS, MG, ZS, donations)
Edit Hive Map / Train Rules / Audiences
Send announcements (incl. Discord post)
Use My Week, daily checklist and seven-day agenda
See own targets, standing and roster readiness
Update status of a command-plan task assigned to you
See own private 30-day Pulse signals (Pro)
Sign up for matches / request DS slot
Submit own General’s Trial level / shield status
Edit own profile and notification preferences
See own history page

Narrow capabilities

Capabilities are additive grants for a specific job. They do not turn a member into an officer and they do not unlock unrelated controls.

  • Event manager — create and edit matches, then manage rosters and battlefield assignments.
  • Results recorder — record match results and attendance.
  • Recruiter — generate and share the alliance invite link.

// NOTE

An R1–R3 member with one of these grants gets only the listed workflow. Billing, settings, rank changes, analytics, and other officer tools stay locked.

How ranks change

R5 can set anyone's rank, including moving an R4 to R3. R4 can only set ranks at R3 and below — they can't create another R4 or modify another R4's rank. Placeholder members can't be promoted or demoted; their rank is set when the placeholder is created and only changes when the placeholder is merged into a real account.

R5 can't change their own rank from the members panel — there's a separate Transfer Leadership flow for that, which moves R5 to a target member and demotes the previous R5 to R4.

Owner-only controls

R4 and R5 share operational configuration, including alliance identity, event schedules, integrations, display rules, and Performance Expectations. The reserved boundary is ownership: billing, archive/delete, leadership transfer, co-admin management, and invite-code rotation stay with the alliance owner or an authorised web admin.

// NOTE

The platform double-checks rank, tenant membership, capabilities, and owner-only rules on the server before saving. On-screen gating is for clarity; backend authorization is the security boundary.