Reviewer
Advanced
Promotion reviewer
Use member case files and the Promotion Board together. Readiness is where candidates surface. The board is where formal decisions should happen.
Where to click
Dashboard -> Promotion Board and Members -> select member
Session host
Advanced
Session operator
Create sessions, track attendance, and keep game links correct per session type so records stay useful later.
Where to click
Dashboard -> Sessions
Moderator
Advanced
Warning and leave staff
Use warnings, leave, and notes as case context. The goal is to help promotion reviewers understand a member, not bury the story in Discord.
Where to click
Dashboard -> Warnings, Leave, and Members -> case file
Readiness answers “who looks promotable.” The board answers “what decision did staff make, with what context, and why.” Keep those two ideas separate.
Where to click
Dashboard -> Promotion Board or Dashboard -> Move to promotion board
1
Move eligible members from readiness into the board instead of approving directly from the queue.
2
Open the case detail, read the requirement snapshot, activity snapshot, warnings, leave, and reviewer history.
3
Approve, deny, mark needs info, or cancel with a note so the next staff member understands the decision trail.
Use “Needs info” when
You are waiting on follow-up, clarification, or more staff input. This keeps the case open without pretending the member is denied.
Use “Cancel” when
The review is no longer valid for the current rank or should be closed without treating it like an approval or denial.
The case file is now the one place where a member’s operational story should come together. Staff should not have to rebuild context from memory.
Where to click
Dashboard -> Members -> click a member card
1
Check the summary strip first: promotion status, warnings, leave, inactivity, and activity totals.
2
Read the pinned note if there is one. Treat it like the main handoff note for the member.
3
Use the timeline to confirm what actually happened before issuing another action.
Sessions are useful because they feed requirements, activity, and case context. If session setup is vague, every downstream workflow gets weaker.
Where to click
Dashboard -> Sessions and Settings -> Operations -> Session announcements
1
Enable sessions, pick the session channel, and set the default session embed message in Settings.
2
Add session types like training, patrol, or raid and set a game link for each if you want the embed button to stay useful.
3
When a session is completed or cancelled, Soler updates the same announcement so staff are not chasing multiple messages.
Activity is modular. Use it to support your real operational standards, not as a giant generic stat bucket.
Where to click
Dashboard -> Activity and Settings -> Operations -> Promotion rules
Good fit
Minutes, hosted sessions, attendance, points, or a custom metric that your promotion rules already care about.
Good habit
Use the activity page to edit mistakes and reset the leaderboard only when you intentionally want totals and attendance history cleared.
Leave requests should start pending and move through staff approval. Once active, they can excuse inactivity and optionally block promotion review.
Where to click
Dashboard -> Leave and Settings -> Operations -> Leave policy
1
Members or staff submit the request, but it stays pending until someone with leave approval access acts on it.
2
Use the Leave view as the queue. Do not run approvals through DMs or side chats if you want the case history to stay clean.
3
Check how your leave settings affect inactivity and promotion review before assuming a blocked case is a bug.
