For MSPs
Twenty client tenants, one console, no standing admin rights.
Most tooling was built for one tenant and grew a tenant picker later. This was multi-tenant from the first commit, which is why the order queue, the audit trail and the invoice all understand which client a change belongs to.
Tenant switching
Change client without changing tool.
An agent works in the tenant they were granted access to, for as long as the rule allows, and the switch is one control — not a second browser profile and a second set of credentials.
23
Client companies in one view
3
People in IT running them
0
People with standing rights
The queue
One queue across every client.
Requests from all clients land in the same place, tagged with the client, the requester and the approval state. Nothing waits in a mailbox, and nothing gets retyped from a ticket into a console.
Chargeback
What each client costs, per period.
License spend and platform cost are allocated per client, so the number on your invoice and the number in your tooling come from the same source. Unused licenses show up with the money attached.
Languages
Your Nordic clients read Norwegian. Your admins read English.
Your Nordic clients get the product in Norwegian, Swedish, Danish or Finnish. Their admins get it in English. Same tenant, same data, per-user language.
It costs nothing extra, it is not a separate deployment, and it is the reason MSPs with Nordic clients end up here rather than with tooling that ships English only.