Multitenancy

Overview

The Devo platform is a multitenant application, which means that customers are able to keep data segregated in as many domains (or tenants) as they need in the same cloud.
In Devo, a tenant can be completely independent (single tenant) or it can be part of a multitenant structure. A multitenant structure in Devo is a group of tenants or domains that belong to the same customer and share some common characteristics:

• The names of all the tenants in a multitenant structure end in the same way, following this structure: <prefix>@<name-of-the-mutitenant-structure> (for example, domain1@multi, domain2@multi…). Learn more about naming rules in multitenant structures here.

• All the tenants have a customized look and feel (company logo, login page, etc.)

• Inside a multitenant, you can create plans for different licensing models. One tenant belongs to a specific plan.

• Inside a plan, you can create roles that are shared across all domains inside that plan to facilitate role management.

Contact Devo if your company is interested in using a multitenant structure for its users.

Who can benefit from multitenancy?

These are some of the common use cases for which it can be interesting to create a multitenant structure inside Devo:

MSSPs

MSSPs where a tenant is created for each managed customer. MSSPs are able to onboard each customer of theirs into their own Devo domain, which allows the company to have its own view, users, use cases, etc.

Companies with different business units

Large corporations with different business units (BU) where one tenant is created for each BU. Corporations that have business units in countries with different legislations can choose to have the data for those units stored on regional data nodes to comply with data residency laws.

Any customer that wants to have both a production and a testing domain

Multitenant domains are common among companies that require using more than one domain, for example, to have separated production and testing environments.

Partners or companies reselling Devo

A multitenant setup is typical of companies that have rebranded domains of their product or services.

Naming rules

The name of a domain inside a multitenant structure will always follow this format:

<prefix>@<name-of-the-mutitenant-structure>

For example, us_bu1@xcycorp is the tenant or domain of U.S. business unit 1 and belongs to the multitenant structure xyzcorp of XYZ Corp.

The name on the left side should represent the data contained in that domain, for example, only United States data. It is OK to use underscores in the names of domains both in prefixes and suffixes.

Example

Let's suppose there is a large corporation called XYZ Corp that has multiple business units (BU) and we want to keep the data separated for each one in Devo. 

To do that, we can create a multitenant structure called @xyzcorp and then create one Devo domain inside this multitenant for each business unit.

These are the domains in our example multitenant structure:

• central@xyzcorp

• us_bu1@xyzcorp

• us_bu2@xyzcorp

• eu_bu1@xyzcorp

• apac_bu1@xyzcorp

It is possible to have as many multitenant structures as required.

How to manage multitenant domains in Devo

Multitenant admins are in charge of managing the domains in their multitenant structure and defining specific data access rules across them. They can do this in the Administration → Multitenancy area and only from the root domain of the structure.

This area has 2 different tabs:

Open

• Overview - This is the default tab when you access the Multitenancy area. You will see a table listing all the domains in your multitenant structure. Click a domain name to check extra details.

• Custom data access - Define and manage data access rules across the domains in a multitenant structure. Learn more about this feature in this section.