How each company's database works

This administrator-oriented article explains how MobilityManager gives each company (tenant) its own database, how those databases are named and provisioned, and how to check their health.

One database per company

Every company's fleet data is stored in a separate database. The system database keeps the master list of companies together with each company's connection details; the operational data — vehicles, the Fahrzeugakte (vehicle file), bookings, and Belege (receipts/expense documents) — lives in the company's own database. When a request comes in, the platform reads your active company, looks up that company's connection, and opens a connection to exactly that database. This is what keeps companies isolated from one another.

Note: The platform supports two database engines, selected by the installation's configured database provider: SQL Server and PostgreSQL. All companies on one installation use the same engine.

How a company database is provided

When a company is created (which requires the tenants:create permission, normally a SystemAdmin), you choose one of two options:

1. Auto-provision — the platform generates the next free database name using the template mobilitymanager001 through mobilitymanager999, derives the connection from the system database configuration, creates the database, and applies the schema.
2. Bring your own — you supply a connection string for a database you manage yourself, and the platform records and uses it.

Auto-provisioning scans existing companies to find the lowest unused number in the 001–999 range, so names stay unique and predictable.

Checking company database health

The platform can test whether a company's database is reachable and report a status:

• Checking a single company's status requires the tenants:view permission.
• Viewing the health of all companies at once requires the tenants:manage permission and is a SystemAdmin-level overview.

Warning: If a company shows as Degraded, its users can authenticate but the platform cannot open its data. Resolve the database or connection problem before users attempt to work in that company.

When the platform cannot open a company database

The platform will refuse to open a company's data context if any of the following is true:

• The company has no connection string configured.
• The company's status is not Active (for example it has been deactivated).
• The database itself is unreachable.

In these cases the company's records are not exposed, which protects data integrity even when infrastructure is misconfigured.

Related

• Creating a new company
• Understanding companies and data isolation
• What happens to your data when a company is deactivated
• Activating and deactivating a company