Skip to content
Tutorials

Rosters

Generate, edit, version, finalize, view, copy, and post roster output from event signups.

Scheduling
Who uses it
Group leads and event leads
Where it lives
Dashboard > Scheduling > Events > Event > Roster
Goal
A staff-ready roster version that can be reopened, shared as a web view, copied as Discord markdown, or posted to Discord.
On This Page5 sections

Before You Start

  • A native event with signups.
  • Mapped roles if readiness labels should matter.

Steps

  1. Generate from current signups

    The generated roster is saved as a version. Loading versions uses a selector so one active version is edited at a time.

  2. Adjust native rosters

    Use explicit edit and move controls for native events. RaidHelper snapshots are read-only analysis output because GearCheck does not own those signups.

  3. Mark final separately from posting

    Mark final sets the current web roster. Posting to Discord is a separate intentional action.

Check It Worked

  • Version name and description are saved.
  • Detailed roster opens cleanly.
  • Discord markdown can be copied or posted.

Common Pitfalls

  • Expecting GearCheck to mutate RaidHelper rosters.
  • Treating mark final as an automatic Discord post.