A Rhythm administrator begins on the customer page and starts workspace provisioning from there. They complete the wizard and use the job page to follow progress or retry a failure. After setup, they inspect the workspace overview and sender instructions. An initial migration uses the loading workflow before handover; business go-live remains a separate HQ action.
The Formal Contract
The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.
Goal
Establish the customer, provision its workspace, invite the initial administrator and make the business go-live decision.
End-to-end policy: required: The intended flow connects HQ screens, backend provisioning and handover. A browser run against real services is required to establish the combined experience; mock navigation and backend job tests provide separate evidence.