Understanding companies and data isolation
This article explains what a company (tenant) is in MobilityManager and how the platform keeps each company's fleet data completely separate from every other company's. Read it before you create or configure companies so the rest of the setup makes sense.
What a company is
A company (tenant) represents one organization that uses MobilityManager. Every company has its own vehicles, drivers, bookings, Belege (receipts/expense documents), and configuration. The platform is multi-tenant, which means a single installation can host many companies side by side while keeping each one's records isolated from the others.
Each company record carries a small set of core attributes:
- Name — the display name of the organization.
- Code — a short unique identifier used at sign-in and for single sign-on.
- Status — either
ActiveorInactive. - Configuration such as language (DE or EN), currency, and the regulatory framework for inspections.
How data isolation works
Isolation in MobilityManager is enforced at the database level, not just by filtering rows. There are two kinds of database:
- A system database that holds cross-company information: the list of companies, user accounts, roles, and each user's role in each company.
- A separate company database for each company that holds the operational fleet data — vehicles, the Fahrzeugakte (vehicle file), bookings, Belege, and more.
When you are signed in and working, the platform reads your active company from your session token, looks up that company's database connection, and opens a connection to exactly that database. You can only ever see and change data that belongs to your active company.
Note: Because each company lives in its own database, there is no way for data to "leak" between companies through normal use. Even a system administrator sees one company's data at a time and must switch companies to work in another.
What is configured per company
Many behaviors are set independently for each company, so two companies on the same installation can operate very differently. Examples include:
| Setting | Purpose |
|---|---|
| Language | Interface language for the company (DE or EN). |
| Currency | ISO 4217 code (for example EUR or CHF) used to format money. |
| Regulatory framework | HU (Germany), §57a (Austria), or MFK (Switzerland) for inspection due dates. |
| Default booking mode | How the booking screen offers vehicles (self-service, auto-assign, or manager-assign). |
| Approval settings | Whether bookings and Belege require approval before they take effect. |
Roles are per company
A user's role applies within a specific company. The same person can be a FleetManager in one company and a Driver in another. Roles are exactly SystemAdmin, FleetManager, and Driver, plus any custom roles your administrator defines. A SystemAdmin is global and can reach any company; everyone else is confined to the companies they have been given a role in.
Related
- Creating a new company
- Company codes and identifiers explained
- Giving a user access to multiple companies
- How each company's database works
