Cross-tenant administration
The core of CrossTenant: work across your whole book from one governed view while every customer environment and authority boundary remains independent. One scope picker, fleet-wide pages, and writes that always route to the owning tenant.
Prefer email? Get in touch and we run onboarding with you.
What's included
One scope picker
Work at the altitude the job needs: all tenants, a tenant group, or a single customer. The same pages follow you at every scope: no separate "MSP view" with half the features.
Fleet-wide pages, per-tenant attribution
Users, groups, organizational units, licences, domains, and policies aggregate across every customer, and every row is tagged with the tenant it belongs to. Unreachable tenants are surfaced explicitly, never silently skipped.
Writes route to the owning tenant
Any change made from an aggregated view is executed against the tenant that owns the row, behind an explicit confirmation. Read-only customers are enforced server-side: mutations are refused even where the separately customer-approved domain-wide delegation grant may include write-capable scopes. Google OAuth consent is separately limited to read-only scopes.
Bulk actions with dry-run previews
Cross-tenant bulk operations show you exactly what would change, per customer, before anything runs, and each tenant is applied independently, so one failure never cascades into the rest of the fleet.
Tenant groups
Group customers however you run your book (by SLA tier, size, or industry), then scope pages, schedules, and alert rules to the group.
External collaboration governance
Record which independent customer organisations intend to collaborate, in which direction, for which domains and resources, and when the relationship needs review. Guest, group and Drive review status can be recorded without disguising a manual attestation as provider evidence, so an unchecked or stale side is never presented as trusted.
Guided offboarding
The guided leaver workflow runs suspend, sign-in reset, Drive and Calendar transfer, and delegate/forwarding cleanup as one audited sequence, instead of a checklist across five Admin console tabs.
Customer health
A book-of-business dashboard scores each tenant's readiness and security posture, worst-first. The customer that needs you today finds you on the first screen.
Here, cross-tenant means governed administration across independent Google Workspace customers, including review of intended external collaboration. It does not create native trust between customers, provide automatic directory synchronisation, or migrate mailbox and Drive content between independent customer tenants.
Feature availability by tier is summarised under pricing. MSP priorities shape how the catalogue grows next, and guided onboarding gives you a direct line to the team building it.
Cross-tenant
See your whole book on one screen
Connect your first customers and the scope picker does the rest: all tenants, a group, or one, on every page. See it in the demo first, or book a call and we onboard your first tenant together.