Skip to main content
Audience: MSP staff responsible for setting up the organization’s portal. Launch Center is not the onboarding task list for a Company user. For client onboarding, use the client onboarding guides. Launch Center organizes configuration around your rollout goals. It checks stored configuration and data alongside your progress, so a completed step and a ready client experience are not the same thing.

​
Access and prerequisites

Open Launch Center from the sidebar, or select Launch in the top bar when offered. Availability also depends on your organization’s setup history and whether Launch Center was dismissed. Reading requires Launch Center read/manage access or the applicable tenant-settings access. Changing the plan requires Launch Center management or tenant-settings management; the primary administrator also has management access. Company users are excluded. Individual embedded setup screens can require their own settings permissions and provider access. Have the intended rollout goals, responsible staff member and authoritative data sources ready. Connecting integrations, importing users, changing branding and billing are real configuration actions; a launch plan is not a sandbox for those changes.
Example MSP launch plan with incomplete readiness findings.

Example MSP launch plan with incomplete readiness findings.

​
Choose a plan

1

Choose how to start

On the welcome screen, select Build my launch plan for a guided questionnaire or Explore first for an exploration plan. Both start a saved setup workflow. Explore first does not certify the portal as ready for clients.
2

Choose your focus

Select the outcomes you need: client ticketing, self-service, security training, vCIO planning, compliance or a client data foundation. The complete rollout option combines the tracks. Answer the questions about data sources and the pilot or wider rollout.
3

Build and review

Select Build my plan. Review the phases and dependencies before changing configuration. Edit launch plan lets an authorized manager revisit the goals later; review the resulting steps after saving.
The plan can include Foundation, Connect, Client data, Ticketing, Training, vCIO, Compliance, and Review and launch. Which steps are required depends on the selected goals and systems. Optional work may appear under Explore later.

​
Complete setup work

  1. Select a step in Setup guide. Read its purpose, affected areas and verification guidance.
  2. Review the embedded setup screen or follow its configuration link. Check the selected integration or company before any save or import.
  3. Use that screen’s labeled Save, Connect or Import action where offered. Wait for its result. Some controls save immediately; others stage changes.
  4. Select Next when ready. It runs the step’s registered save or continuation flow and can require readiness evidence before marking the step complete.
  5. Check the resulting step status and any error before moving on.
Back and choosing another step are navigation actions. Do not use them as a guaranteed discard operation: some workspaces save pending changes during navigation. If Do this later is offered for an optional step, it can save the current workspace before recording the deferral. It does not undo configuration already saved. Collapse Setup guide to make more room for the workspace, and expand it again to choose another step. Your stored plan can be resumed later, but unsaved text in an embedded form is not guaranteed to survive leaving the page.

​
Read readiness findings

Use the readiness summary and Live verification to inspect the evidence. Read both the severity and the outcome of each finding. Integration and data steps can complete from evidence without a manual checkmark. A later configuration change can make a previously passing check fail. Review the displayed check time and current findings before inviting clients; a progress percentage is not a guarantee that every client workflow works. Review the client experience inspects the selected company and role’s readiness and access information. It does not sign you in as that client or replace testing the actual Company experience.

​
Complete or hand off the launch

On Complete launch, review all blocking findings. Completion is available only when the required readiness evidence passes. An exploration-only plan must be expanded into a launch plan before it can certify a rollout. Completing the launch records its completion; it does not itself send client invitations. Readiness monitoring can later report Needs attention if required configuration regresses. Resolve the reported cause and recheck the current state. The Launch coordinator identifies the accountable person. Where its selection control is offered, the current coordinator, primary administrator or tenant owner can choose an eligible replacement. Selecting a replacement can save immediately; wait for the result and confirm the displayed coordinator. This transfers launch responsibility, not ownership of the tenant or unrestricted settings access.

​
Dismiss Launch Center

An authorized manager can select Dismiss Launch Center, review the tenant-wide confirmation, and choose Remove for everyone. This hides its sidebar and top-bar entry for the organization. It does not delete the saved setup configuration or undo integrations. Choose Cancel to keep it available. If it was dismissed accidentally and no restore control is offered, contact support rather than repeating setup or disconnecting services.

​
Troubleshooting

​
FAQs

No. It is an MSP setup workflow for the organization. Client onboarding has separate portals, tasks, forms and access.
It starts a saved exploration workflow. It does not complete a full client rollout or make subsequent configuration changes temporary.
Check the action result and readiness status. A validation, permission, connection or evidence failure can prevent completion.
No. On supported optional steps it saves the workspace before recording the deferral. Review saved configuration before retrying or moving on.
No. It proves the specific checked evidence met the rule. Test the actual Company role and workflow before rollout.
Completion records setup readiness. Client invitations and communications are separate actions.
No. Remove for everyone changes organization-wide navigation visibility and leaves saved configuration in place.
No. Plan mutations require management access, and individual setup screens can impose additional permissions.