Where my data is stored: multi-tenant isolation explained

MobilityManager is a multi-tenant platform, which means several customer organizations can be served by one installation while their operational data stays separate. This article explains how that isolation works and what it means for your data.

How the platform separates data

The platform uses two kinds of database:

• A single system database holds platform-wide records: user accounts, the list of companies (tenants), roles and permissions, and the software license.
• Each company (tenant) has its own separate tenant database that holds that company's operational data, such as vehicles, drivers, bookings, damage cases, expenses, and documents.

Every company record carries its own database connection, so when you work inside a company, the application connects to that company's dedicated database. One company's operational data is never mixed into another company's database.

Note: Because operational data lives in per-company databases, your role and permissions are also evaluated for the company you are currently working in. Switching companies connects you to a different database and applies your role there.

What this means for you

• Isolation: Vehicles, bookings, documents, and other records you create in one company are visible only within that company. A user must hold a role in a company to reach its data at all.
• Your identity is shared, your data is not: Your single user account can be granted roles in more than one company. The account lives in the system database, but the work you do is stored in each company's own tenant database.
• Documents: Uploaded files are stored through the company's tenant context, so document operations require an active company context and the right permission to access them.

Where the databases physically live

MobilityManager runs on standard relational databases and supports both PostgreSQL and SQL Server. The physical location of those databases, whether hosted by your organization on-premises or by a provider, is determined by how your instance was deployed. If you need to know the exact hosting location or region for compliance reasons, ask your administrator or MobilityManager support; that detail is specific to your deployment and is not something an end user configures.

Tip: If you can see a company at login but none of its data, you are likely missing a role in that company rather than looking at the wrong database. See the related article on Access Denied.

Related

• A company (tenant) is not showing at login
• "Access Denied": understanding permissions and roles
• What MobilityManager does and who to contact for support
• A document will not download