Skip to main content
Use this playbook to prepare your MSP’s portal for clients. Launch Center builds a plan around your goals and data sources, so the steps you see depend on what you chose. This page lists the work in the order most MSPs do it, with a guide for each part. Client onboarding is a separate workflow for individual companies.

Before you start

  • Use an MSP account with access to the settings you will change. Launch Center manage access does not replace a setup screen’s own permissions.
  • Agree on a launch coordinator, a pilot company, and where your companies, users, and devices come from.
  • Have these ready:
    • PSA API credentials, and RMM API credentials if you use one
    • A Microsoft 365 administrator for each client tenant you will connect
    • Your logo files and brand color
    • A domain you can add DNS records to, if you will send email from your own domain
Example MSP launch plan: setup progress and readiness findings are separate.

Launch Center in MSPortal Demo. Setup progress and readiness findings are separate.

Work through the rollout

1

Build your plan

Open Launch Center, click Build my launch plan, and choose your goals, data source, and rollout. See Work through your portal launch plan.
2

Set the foundation

4

Connect your systems

5

Bring in client data

Map your companies, then prepare Company users and import devices. Staged provider records are not portal records until you import them.
6

Set up client tasks

Configure ticket delivery, visibility, and templates and training. If you want email from your own domain, set up your sending domain.
7

Check readiness and launch

Open Live verification, fix every Blocking finding, review the client experience, and click Complete launch.
If you only have time for a first pass, do the company profile, staff access, branding, and your PSA and RMM. Everything else can come later.

Save and verify

Open each step from Setup guide. Each embedded screen has its own save behavior. Next saves the step and moves on, so wait for the result and check readiness. Moving to another step or clicking Do this later can also save pending changes, so neither is a way to discard a draft. Readiness covers the rollout you chose. A pilot checks its company. A wider rollout can need evidence for every active client company. One connected provider or one imported user does not necessarily satisfy the plan. Recheck after you change the scope.

Before you invite clients

1

Check access

Confirm each client user has the right company and access group.
2

Check content

Confirm their templates and training are enabled, and that records belong to the right company. See Control what Company users can see.
3

Check ticketing

Check ticket delivery separately from template visibility.
4

Invite when ready

Completing launch records setup. Invitations and other client messages are separate actions.

Troubleshooting

Frequently asked questions

No. This playbook prepares the MSP portal. Individual clients use the separate client onboarding workflow.
No. Next saves the step. Check the result before you leave.
No. Client invitations are separate actions.