Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 16 Next »

 Watch video tutorial

Watch the last two chapters of this video for a general overview on rule creation and data access.

Introduction

However, multitenant structures support data access across the domains. This means that some domains can access data tables across several domains inside the multitenant structure by defining data access rules. These rules are defined by an admin who can set up as many rules as required to share data grouped in tables across the required domains in a multitenant structure.

The custom data access feature allows your organization to self-manage data access in their multitenant domains. Organizations can set up rules to let some specific domains in the multitenant structure access the data in some other domains as required.

Basic concepts

Check the following concepts to understand how data access across domains works in a multitenant structure:

Multitenant admin

The multitenant admin is in charge of defining specific data access rules across the domains in the structure. They can do this in the Administration → Multitenancy area and only from the root domain.

Multitenancy administration permission

To access this area, the admin must have the Multitenancy administration permission. This permission is not visible by default and only Devo admins have it. If you need other users to have it, please contact us.

Root domain

Root domains can access data owned by other domains inside the multitenant structure. There can be multiple of them with different data access set up as required by the multitenant admin.

Check the child domains data that a root domain can access and how to do it in this article.

Child domain

Child domains are the tenants included in a rule set up by the multitenant admin. A root domain will have access to the data in the child domains under the rule set up by the admin.

Levels of hierarchy

Only two levels of hierarchy are supported. However, it’s possible to simulate as many levels as required using a naming schema or even without any naming schema.

Example with naming schema:

Example without naming schema:

  • No labels