Overview

Once you have completed the initial steps for setting up your account, you can organize your tenants and users into a hierarchy. This will help you facilitate efficient, role-based activities inside your account and help drive better accountability across your team(s).

In this user guide, we'll briefly explain how organizational hierarchy works within the platform as well as what options you have for setting that up.

Tenant Organization

The platform supports multi-tenancy by default.

In enterprises and IT organizations, there will be multiple departments. Associates and resources under each department are normally isolated from each other. This isolation is needed not only for financial accounting but also for security and management. Though the associates can have access to multiple departments, their permissions will vary.

Tenant Structure for Enterprises

In an enterprise, there can be multiple departments such as Operations, Finance, and R&D. These can be considered as tenants in the platform. The diagram below shows a sample mapping for a similar setup:

Tenant Structure for IT Organizations

In an IT organization, there can be multiple teams such as QA, Engineering, and DevOps. These can be considered as tenants in the platform. The diagram below shows a sample mapping for a similar setup:

Tenant Structure for MSP Organizations

MSP organizations typically manage multiple customers and their cloud resources across different platforms. These can be connected back to tenants in the platform. The diagram below shows a sample mapping for a similar setup:

It's up to you how you set up your organizational hierarchy within the platform, but hopefully these samples provide some good inspiration based on real use cases.

Please refer to the user guide pages for Account Management, Tenant Management, and Identity and Access Management for more detailed information.