Start with the public tools
You do not need an account to use the launch checklist or roster template. Both are useful for collecting decisions before connecting any game data. They save on the current device and offer text downloads; they do not automatically import into the shared workspace.
The product tour uses fictional characters to explain the questions a roster can help answer. It is an illustration, not a live guild or evidence of WoW Forever client compatibility.
Open the app and create your account
Choose Open app, then ‘New to RaidMuster? Create an account’. Enter your name, email and password. Complete email verification if requested, then sign in. Existing members can use the same sign-in form or the password-recovery option.
Create a workspace when prompted, or follow a workspace invitation supplied by your guild. Keep invitation and device-pairing links within the intended group; public guides do not need them.
Find the right workspace view
The sidebar separates your day-to-day views from management settings. Begin with Overview to understand the current workspace, then inspect Roster for the characters and observations available.
- Roster: review available character data and its freshness.
- Professions: inspect profession and crafting information where supported observations exist.
- Raid Setup: configure the preparation and raid information your team will use.
- Tonight: explore the planning workflow once its inputs have been configured.
- Sync: connect and manage approved observation sources.
- Account: manage your account and sessions.
Connect data only after checking compatibility
RaidMuster’s data path uses an addon, its SavedVariables file and a companion uploader. It does not mean that every field in every game client is supported. Before installing or pairing anything, read the current sync and compatibility guide.
The development preview preserves capture time separately from receipt time. After an upload, check the character identity, capture time and available facets. An upload acknowledgement alone does not prove that all the character data you wanted was available.
Aim for one clear first outcome
For a new guild, the first useful outcome is a recorded roster and an agreed next action. For a supported sync test, it is a correctly linked character with a visible observation time. Start small enough that an officer can verify the result.
Do not configure final Forever readiness requirements from sample data. Confirm the relevant game content and client support first. Where a field is absent, treat the answer as unknown until someone provides a suitable update.