Ranks and permissions
Ranks mirror the in-game alliance hierarchy. R5 is the leader with full access. R4s share most of the officer toolkit but can't change the alliance settings R5 holds exclusively. R3 and below get a useful member workspace — My Week, assignments, targets, standings and their own history — without controls that drive the alliance. The same permission rules are enforced in the UI and on the server.
// ON THIS PAGE
Permission matrix
● = full access, ◐ = restricted, — = no access. Hover or tap any row with a note for context.
| Action | R5 | R4 | R3 / R2 / R1 |
|---|---|---|---|
| Edit alliance settings (DS day, server, branding) | ● | — | — |
| Set or change Performance ExpectationsR4 can read but not edit, by design | ● | — | — |
| Generate and revoke invite links | ● | ● | — |
| Add or remove members | ● | ● | — |
| Promote / demote membersR4 can only set ranks R3 / R2 / R1 | ● | ◐ | — |
| Create / edit / cancel Desert Storm matches | ● | ● | — |
| Edit DS rosters and battlefield assignments | ● | ● | — |
| Record DS results and attendance | ● | ● | — |
| 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 | ● | ● | ● |
| 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 | ● | ● | ● |
How ranks change
R5 can set anyone's rank, including promoting 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.
Why R4 is restricted
The asymmetry between R5 and R4 is deliberate. R4s do most of the officer work — match planning, recording results, chasing reshields — but the things that change the bar itself (Performance Expectations, alliance settings) sit with R5 alone. This stops a well-meaning R4 from quietly lowering the donations target to mask a recruitment dip, or turning off the public server-directory listing without the leader knowing.
// NOTE