What Tenant means #
In the platform, a Tenant is a separate organizational perimeter where users, simulations, access, reports, limits, and configurations are managed.
A Tenant can represent a client, but not only.
It can also represent an internal structure, a department, a branch, a business unit, or an operational group belonging to the same Provider.
In other words, the Tenant should not be understood exclusively as an “external client company,” but as an autonomous organizational unit within the platform.
Tenant as an external client #
In the simplest case, a Tenant can represent a client of the Provider.
Example:
A Provider sells the platform to multiple client companies.
In this case:
- the Provider manages multiple clients;
- each client is configured as a Tenant;
- each Tenant has its own users;
- each Tenant has its own simulations;
- each Tenant has its own reports;
- each Tenant has assigned limits, minutes, and resources.
Example:
- Provider: training company
- Tenant 1: Company Alpha
- Tenant 2: Company Beta
- Tenant 3: Company Gamma
Each Tenant remains separate from the others.
Tenant as a department, division, or internal unit #
A Tenant can also represent an internal division of the same Provider.
This is useful when the Provider is not a reseller or an external company, but a large organization using the platform for itself.
Examples:
- hospital;
- university;
- large company;
- multinational group;
- public entity;
- healthcare network;
- insurance group;
- corporate academy.
In these cases, the Provider can be the main organization, while the Tenants represent its internal branches.
Examples of internal Tenants #
Hospital #
A hospital can be configured as a Provider.
Tenants can represent:
- Emergency Room;
- Cardiology;
- Oncology;
- Pediatrics;
- Medical Direction;
- Internal Training;
- Risk Management.
Each department can have its own Players, simulations, aggregated reports, and limits.
University #
A university can be configured as a Provider.
Tenants can represent:
- Faculty of Medicine;
- Faculty of Economics;
- Department of Psychology;
- Specialization School;
- Executive Master;
- Simulation Center;
- Internal HR Office.
Each Tenant can manage different training paths, with different Players and simulations.
Large company #
A large company can be configured as a Provider.
Tenants can represent:
- HR;
- Sales;
- Compliance;
- Customer Care;
- Leadership Academy;
- Country Italy;
- Country France;
- Healthcare Business Unit;
- Finance Business Unit.
In this way, the same company can use the platform in a structured manner, separating departments, functions, or countries.
What a Tenant manages #
Within a Tenant, the operational elements of the experience are managed.
A Tenant can have:
- users;
- Players;
- Tenant Admin;
- Communication Skills;
- Observation Grids;
- Guided simulations;
- Runtime access to simulations;
- reports;
- privacy configurations;
- user limits;
- monthly minutes;
- active runtimes;
- simultaneous connections;
- possible White Labeling, if allowed by the Provider.
The Tenant is therefore the operational container in which training activities are organized.
What the Provider manages #
The Provider is the superior entity that governs one or more Tenants.
The Provider can be:
- a company that offers the platform to its clients;
- a large company that uses the platform internally;
- a hospital that subdivides usage by department;
- a university that subdivides usage by faculty or course;
- an entity that manages multiple branches or operational units.
The Provider can manage elements such as:
- creation of Tenants;
- allocation of resources to Tenants;
- available minutes;
- user limits;
- runtime limits;
- simultaneous connections;
- White Label configurations;
- privacy policies;
- access to specific features;
- simulations or templates available for Tenants.
Relationship between Provider and Tenant #
The relationship can be read as follows:
Provider = main organization or entity governing multiple environments
Tenant = separate operational environment for a client, department, division, or group
Commercial example:
- Provider: training company
- Tenant: corporate client
Internal example:
- Provider: hospital
- Tenant: oncology department
Enterprise example:
- Provider: large multinational company
- Tenant: business unit or country
University example:
- Provider: university
- Tenant: faculty, course, or simulation center
Why use multiple Tenants #
Using multiple Tenants allows for keeping environments, data, and configurations separate.
This separation is useful when different groups need to have:
- different users;
- different simulations;
- separate reports;
- dedicated limits;
- different privacy configurations;
- distinct Player access;
- different White Labeling;
- independent training paths.
In this way, the Provider can govern the entire structure, but each Tenant can work within its own perimeter.
Data and report separation #
Each Tenant has its own operational space.
This means that data from one Tenant is not mixed with data from another Tenant.
The separation concerns, for example:
- users;
- Players;
- simulations;
- runtimes;
- reports;
- audits;
- limits;
- configurations.
This logic is especially important in complex organizations, where different departments or clients must remain separate for organizational, privacy, governance, or reporting reasons.
Tenant Admin #
The Tenant Admin is the user who administers a specific Tenant.
They can manage, according to available permissions:
- Tenant users;
- Communication Skills;
- Observation Grids;
- Guided simulations;
- Player access;
- reports;
- resources and limits;
- settings;
- White Labeling, if allowed by the Provider.
The Tenant Admin operates only within the perimeter of their own Tenant.
Complete example #
A large multinational company uses the platform to train multiple internal groups.
The configuration can be:
Provider #
Global Corporate Academy
Tenant #
- Sales Italy
- Sales France
- Compliance EMEA
- Customer Care
- Leadership Program
- HR Business Partner
Each Tenant can have:
- its own Players;
- its own simulations;
- its own runtime access;
- its own aggregated reports;
- its own usage limits;
- any specific configurations.
The Provider maintains a superior view and control over the overall ecosystem.
Difference between Tenant and Player #
A Tenant is not a user.
The Tenant is the organizational environment.
A Player is a person who accesses simulations within that Tenant.
Example:
- Tenant: Cardiology Department
- Player: doctor, nurse, resident, or department member
Difference between Tenant and simulation #
A Tenant is not a simulation.
The Tenant is the container in which multiple simulations can be created, published, and assigned.
Example:
A Tenant can have simulations on:
- doctor-patient communication;
- conflict management;
- managerial feedback;
- risk & compliance;
- customer care;
- leadership under pressure.
Difference between Tenant and Runtime #
The Tenant is the organizational environment.
The Runtime is the operational access to a specific simulation for certain Players, with configurations such as language, channel, voice, avatar, and attempts.
Example:
A Tenant can have one published simulation and several different runtimes:
- a Web runtime in Italian;
- a Web runtime in English;
- a Coaching runtime;
- a VR runtime;
- a runtime assigned only to a group of Players.
Why this model is flexible #
The Provider → Tenant model allows the platform to adapt to both commercial and internal scenarios.
It works for:
- providers selling the platform to different clients;
- large companies wanting to separate business units or countries;
- hospitals wanting to separate departments;
- universities wanting to separate faculties, courses, or simulation centers;
- complex entities wanting to manage multiple groups with different rules.
This flexibility avoids the need to create separate platform installations for each department or client.
Final result #
The Tenant is a central concept of the platform.
It represents not just an external client, but any organizational unit that requires a separate management environment.
It can be a client company, a department, a division, a branch, a business unit, a faculty, a hospital, or an operational group.
The Provider governs one or more Tenants.
The Tenant organizes users, simulations, access, reports, and resources.
The Player experiences the assigned simulations within their own Tenant.
This structure allows the platform to adapt to both multi-client commercial models and large organizations that need to subdivide usage by areas, departments, or internal groups.
