01
A separate database for each one.
An IT company looks after five clients (an MSP, a managed service provider). Each client is a separate organization in AverDesk with its own database. Nothing is shared at the storage level, so one client’s servers cannot show up in another client’s list through a filter mistake. We, the vendor, have no access inside your organizations.
The same works for a holding with several subsidiaries, or for one company that wants production and a test playground kept apart.
02
Many organizations, one bill.
One subscription holds several organizations plus one or more demo organizations for trying things safely. How many depends on the plan: Standard one, Pro three, Extended five, Enterprise by agreement. If you move to a smaller plan, existing organizations stay.
03
Who sees what, and who may do what.
Teams decide which assets a person can see. Roles decide what they can do with them. The two are set separately, so the same engineer edits everything for client A and only views for client B. An invitation can carry rights to a single object: a contractor gets one server, not your whole infrastructure.
04
A refusal explains itself.
What a person has no access to simply does not appear in their lists. There are no greyed-out locked entries to puzzle over. When an action is refused, the message says why, so the admin gets fewer “why can’t I see this” questions. One person counts once across all organizations, however many they work in.
05
Built in from the start.
Passwords and keys stay on the server and never reach the browser. If someone steals a login session, it is detected. The platform runs in containers, and backups are encrypted and sent to your storage (FTPS) on a schedule, with restore when you need it. If everything must live on your own servers, the OnPrem plan does that, with your own branding if you want it.
