Complete the Onboarding Stage
Use Playbook stage Onboarding to set company profile, module scope, implementation roster, and role coverage before Kickoff.
Where: Mission Control → W.A.T. Implementations → Implementation Playbook → Onboarding
Route: /missioncontrol/implementations/playbook (stage Onboarding)
For company selection, stage strip, and exports, see Run the Implementation Playbook.
Steps in this stage
| Step | Title | You must finish before Next unlocks |
|---|---|---|
| 1 | Welcome to the playbook | Company context ready (after Get started or an existing company) |
| 2 | Company profile and modules | Name, abbreviation (implementation ID), start + target go-live dates, at least one module |
| 3 | Team selection and new users | At least one team member on the roster |
| 4 | Implementation role matrix | At least one implementation role assigned |
| 5 | Review and confirm | Company, team, and roles all ready → Complete onboarding and start kickoff |
Next saves pending work for the current step when needed, then advances. Footer hints show when a save/sync is still running.
Step 1 — Welcome
- Open Onboarding (first-run users may see the full-page welcome first—click Get started).
- Read the orientation cards if useful; they do not change data.
- Wait until company context is ready if the footer says the workspace is still preparing.
- Click Next.
If bootstrap fails, use Retry setup.
Step 2 — Company profile and modules
Under Company Profile:
- Set Company Name and Abbreviation (maps to implementation ID).
- Set Start Date and Target Go-Live Date (target must be after start).
- Under Module Groups, click module badges to include scope. Groups:
- Core — AP, AR, CM, GL, JC, JB, HQ, VA
- HR / PR — HR, PR
- Commitments — PO, SL
- Service — SM
- Misc — EM, IN, MS, PC, PM
- Wait for status to settle (changes save in the background), then Next.
Next stays disabled until name, abbreviation, both dates (valid range), and at least one module are set.
Step 3 — Team selection and new users
Registered Team
- Review people from the Mission Control team roster.
- Use each row checkbox to include or exclude them from this implementation roster.
- You need at least one selected member before Next unlocks.
Supplementary Members
Optional people not already on the team:
- Click Add member.
- Enter Name. Expand (+) for Email and TUDS role (Cadet, Bounty Hunter, or Captain).
- Save the row (save / invite-and-save control). Name is required for every started row; email is required when expanded for a true team invite.
- Delete a saved row only after confirming Delete supplementary member? → Delete.
Next syncs pending team selections, then opens the role matrix.
Step 4 — Implementation role matrix
- Confirm the matrix loaded (if you see Syncing team members..., wait).
- Rows are selected roster members; columns are implementation roles from the catalog.
- Check roles for each member. Changes save per member in the background (Saving / Queued badges may appear).
- Assign at least one role somewhere on the matrix, then Next.
No company selected → Select a company first to configure role assignments.
Step 5 — Review and confirm
- Check Readiness summary (company, dates, modules, team + roles).
- Validation must show Ready to complete.
- Click Complete onboarding and start kickoff.
If something is missing, fix it in the earlier steps (use Back). If saves are still flushing, wait and try again.
On success, the Playbook moves you into Kickoff. Continue with Complete the Kickoff stage.