There are two pieces to onboarding. The wizard handles the one-time technical setup: integrations, roles, branding, billing. The playbook is the order to do everything else in so your first client engagement actually reaches a QBR. Run the wizard once. Run the playbook for each new client.Documentation Index
Fetch the complete documentation index at: https://docs.msportal.ai/llms.txt
Use this file to discover all available pages before exploring further.
Before you start
Have these on hand:- PSA API credentials (ConnectWise, Autotask, HaloPSA, or SyncroMSP)
- RMM API credentials (Datto RMM, NinjaOne, Asio, Syncro, Addigy, or Meraki)
- Microsoft 365 global admin consent on your tenant, plus each client tenant you’ll connect
- Your logo and brand color
- A domain you can add DNS records to, for sending email
The wizard
The wizard sits in the bottom-right of the screen the first time you sign in. It auto-completes most steps as you save settings, you can minimize or dismiss it, and progress is saved to your tenant. If you close it, click the rocket icon in the sidebar to bring it back.Setup steps
Foundation- Tenant Details. Address, timezone, basics.
- AI Settings. How the AI assistant talks about your business.
- Branding. Logo, primary color.
- Tenant Roles. Roles for your internal team.
- Company Permission Groups. Permission bundles for client users.
- Company Roles. The roles your clients’ users get assigned.
- Integration Selection. Pick your PSA and RMM.
- PSA Integration. Connect the PSA.
- Ticket Settings. Sync direction and status mappings.
- RMM Integration. Connect the RMM.
- Device Import. Pull devices in.
- Email Domain. Send email from your own domain.
- Training. Optional. Configure training courses.
- Billing. Subscription and payment.
- Company M365 Setup. Connect M365 for a client.
- Company Users. Import client users.
Setup Playbook
The order to roll MSPortal out for a real client. Six stages, ending in a presented QBR.Connect integrations
PSA, RMM, M365, and Backup & Security. The wizard covers this. Don’t skip ticket status mappings or device import. Every later stage depends on the data these connectors pull in.See: Integration Selection, PSA, RMM, Device Import, Company M365 Setup.
Seed the planner and compliance
Pre-load the Planner with what you already know: your standard roadmap, the work the client has already agreed to, and obvious near-term items (firewall refresh, contract renewal, server EOL).Build Compliance checks against your MSP’s standard so every client gets scored against the same baseline.If a client onboarding is coming up in the next two months, build it out now so the kickoff survey has something to link against.
Run the kickoff survey, turn responses into goals
Build a budget and forecast
Import products from your PSA. Build a Budget from the planner items’ hours and cost estimates, then use the forecast view to project it forward. The forecast also drops in as a reporting widget for the QBR.
Build the report and QBR meeting
Make a test narrative report with the client’s real data, and add a budget widget. Create the upcoming QBR meeting and attach the budget and report. Turn on agenda automation so Claude drafts the agenda from live data. Approve it a week ahead so the client gets the pre-read on time.
Present, then loop
Run the QBR live in presentation mode. Take notes as action items in the meeting. Those become planner items automatically. Send the summary when you’re done. As you close out compliance checks during the quarter, the planner updates. Next quarter, start over at the kickoff survey.
Next
- Data flow. How records move through MSPortal once integrations are live.
- Create a tenant role. So you don’t run setup as one person.
- Hide items from clients. Tighten what client-portal users see before you invite them.