Once you have completed the initial steps for setting up your CoreStack account, you can organize your tenants and users into a hierarchy. This will help you facilitate efficient, role-based activities inside your CoreStack account and help drive better accountability across your team(s).
In this user guide, we'll briefly explain how organizational hierarchy works within CoreStack as well as what options you have for setting that up.
CoreStack out of the box supports multi-tenancy.
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.
In an enterprise, there can be multiple departments such as Operations, Finance, and R&D. These can be considered as tenants in CoreStack. The diagram below shows a sample mapping for a similar setup:
In an IT organization, there can be multiple teams such as QA, Engineering, and DevOps. These can be considered as tenants in CoreStack. The diagram below shows a sample mapping for a similar setup:
MSP organizations typically manage multiple customers and their cloud resources across different platforms. These can be connected back to tenants in CoreStack. The diagram below shows a sample mapping for a similar setup:
It's up to you how you set up your organizational hierarchy within CoreStack, but hopefully these samples provide some good inspiration based on real use cases.
Updated about 1 month ago