Tenant Setup for Multi-tenant Architectures

New in version 2.0.0: Global Report feature can be used to share system reports among all tenants, see Global Report Setup Guide.

In multi-tenant systems, tenant data is stored in similar database structures placed in

Separate Database Architecture

Each tenant data is stored in a separate database with identical structure.

Add connections to each tenant database at that tenant level.
In this sample, create 4 tenants each having one connection to its database.
Data model and other settings should be set up for one tenant, then copied to other tenants using a Copy Management setting similar to the following:

Each tenant data is stored in a separate schema in the same database.

Add connections to the shared database at that each tenant level.
Set up data model for one source tenant only.
Skip data model for other tenants (Just add the connection, test then save it).
Copy data model to other tenants using a Copy Management setting similar to the following:
The data model was successfully copied to other tenants.

Each tenant data is stored in the same tables, schema and database, identified by different values in a “TenantID” field in every table.

Add connections to the shared database at that each tenant level.
Set up data model for one source tenant only.
Skip data model for other tenants (Just add the connection, test then save it).
Copy data model to other tenants using a Copy Management setting similar to the following:
Specify this specific “TenantID” field in the “Tenant Field” advanced setting to automatically restrict report data to that of the tenant of the current logged-in user.
(This setting basically adds a filter condition “TenantID” = <value of the tenant id of the current logged-in user> to every query sources used in report)
Note: Please note that the field must be wrapped in brackets when set. For example: TenantID should be set as [TenantID]