MSP pricing is handled separately
The MSP portal at a glance
- Fleet view: a single view across every customer tenant — posture score, last scan, open-priority count, and trend.
- Per-customer drill-down: click into any customer to see the full ScanPosture dashboard for that tenant, with the same controls a direct customer would see.
- Branded outputs: upload a logo and brand colour pair per customer (or one set across the fleet). PDF reports and the scheduled email summary use the customer’s branding when enabled.
- Cross-tenant search: find a finding type across the entire fleet — e.g. “which customers still have legacy SMTP auth enabled?” in one query.
Role-based access
- MSP adminFull access across the MSP portal — onboard customers, manage MSP team, manage branding, configure billing.
- MSP analystRead access across every customer tenant — can run scans, view findings, generate reports. Cannot manage MSP team or billing.
- Customer adminFull access to their own tenant only — same as a direct customer admin. Used when the customer wants to see their own posture alongside MSP oversight.
- Customer viewerRead-only access to their own tenant. Suitable for the customer’s leadership or compliance officer.
MSP roles and customer roles are independent. An MSP analyst can access every customer tenant in the fleet; a customer admin can only see their own tenant. There’s no path for one customer’s users to see another customer’s data — RLS enforces tenant isolation at the database level, not in application code.
Onboarding a customer tenant
From the MSP portal, the flow per customer is the same three-minute path a direct customer would take, with one difference: the MSP’s admin holds the relationship, so the customer’s Global Administrator only needs to grant the Microsoft admin consent — not create an account, not pick a subdomain, not set up MFA.
Add customer in MSP portal
Send admin-consent link
First scan runs
(Optional) Invite customer-side users
Branded customer-facing reports
With branding enabled, the PDF executive report and the scheduled email summary use the customer’s logo and colour palette — not the MSP’s and not ScanPosture’s. This is what most customers expect when the report lands in their leadership’s inbox. MSP attribution stays on a small footer line so it’s clear who’s producing the report.
Billing model
- Billing relationshipThe MSP is the billing customer. ScanPosture invoices the MSP, the MSP invoices their customer.
- Pricing inputsNumber of customer tenants, total managed Entra users, branding requirements, and reporting cadence.
- Volume bandsPer-user rate steps down at 1k, 5k, and 25k managed users. Specifics agreed in the MSP order form.
- Customer additionsNew customers added mid-cycle are pro-rated on the next invoice. No per-customer setup fee.
- CancellationCancel any time. Final invoice prorated to the cancellation date.
Common questions on a partner intro call
- Can MSP analysts trigger scans on customer tenants? Yes — that’s the point of MSP analyst.
- Can a customer revoke MSP access? Yes — by removing ScanPosture from their tenant’s enterprise apps. Revocation is immediate, total, and surfaces in the MSP portal as a connection-lost state.
- Can the MSP brand the ScanPosture login screen? Not yet — the login screen is the standard ScanPosture brand. Branding applies to outputs (reports, emails) only.
- Is there an API for MSP automation? Not yet — the in-product webhooks and AI helpers documented under Integrations cover most workflows. A REST API is on the roadmap; if you need it, tell us at the partner call.
Still got questions? Email hello@scanposture.com — UK working days, real human, same-day reply.