Your own organization as a tenant
Your MSP’s own organization appears as a distinct row at the top of MSP → Clients, labeled Your organization, so it’s never confused with an actual client. This is also where your own organization’s compliance activation lives: if you want to run your compliance program on Regentra the same way your clients do, that’s a separate action from provisioning a client — click Manage Compliance from the MSP dashboard to start your own compliance trial or subscription.Your organization’s compliance usage counts toward your plan’s compliance tenant allocation just like a client’s would — see Compliance tenant billing.
Adding a new client
Clicking New Client on MSP → Clients opens a chooser with two distinct options — pick the one that matches what the client actually needs:- Compliance Client — provisions a full managed organization with its own compliance workspace and user logins. Counts against your compliance-tenant allocation and requires an active compliance subscription or trial.
- PSA Company — creates a customer record for ticketing, assets, and billing inside your PSA org. No app login, and it doesn’t consume a compliance-tenant slot. You can promote it to a Compliance Client later from the PSA company detail page.
1
Start provisioning
Navigate to MSP → Clients, click New Client, and choose Compliance Client. (If the client list is empty, a Provision Client shortcut on the empty state goes straight to this same form.)
2
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.
3
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.
4
Configure portal (optional)
Switch into the client’s context and open PSA → Support Portal to brand the support portal, attach a custom domain, and enable Microsoft SSO.
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, Needs Review)
- 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.