Adding a new client
Enter client details
Provide the client’s Organization Name, Industry, and the first admin user’s First Name, Last Name, and Admin Email. The admin receives an email to set their password and finish setup.
Adopt frameworks (after provisioning)
Frameworks are not selected during provisioning. Once the client tenant exists, switch into the client’s context and adopt frameworks from Compliance → Frameworks — each Adopt click seeds that framework’s controls into the tenant.
Provisioning creates an empty tenant — no frameworks, no controls, no policies. This is intentional so you can choose only the frameworks the client actually needs and avoid pre-seeding controls they will not use.
Context switching
Use the ComplianceClientSwitcher in the sidebar to move between client contexts. The switcher lists all your managed clients and shows which one is currently selected. When you switch clients, all compliance and PSA views update to show that client’s data. Your MSP-level settings (team management, billing, integrations) are not affected by client selection.Per-client compliance
Each client tenant includes:- Controls — Framework-specific controls with status tracking (Not Started, In Progress, Implemented, Not Applicable)
- Policies — Document policies mapped to controls
- Risk assessments — Risk register with likelihood, impact, and mitigation tracking
- Evidence collection — Upload and link evidence to controls for audit readiness
Per-client portal
Each client gets their own support portal instance:- Separate branding (logo, colors, CSS)
- Optional custom domain (e.g.,
support.clientname.com) - Independent contact list (manual or synced from the client’s Entra ID)
- Isolated ticket queue — end users only see their own organization’s tickets
Portal configuration is managed within each client’s context. Switch to the client, then go to PSA → Support Portal (or click the Support Portal tile on the main Settings page) to customize.