Using Anchor's multitenant web portal, you can create and manage organizations and suborganizations for all of your clients. These organizations will be organized in a hierarchy within the Organization navigation menu, allowing for a scalable environment that can grow and change according to your needs.
The master organization—which is system generated—will display at the top-level of the hierarchy, and all other organizations that you create will sit below the master organization. You can optionally create suborganizations, which will sit below the organizations that you create.
For example, you might configure your organizations and suborganizations in the following hierarchy:
Master Organization—each new system is populated with a master organization, which displays at the top-level of the hierarchy. The name of your master organization is based on your registration settings. The master organization should remain empty, and can be used to see an overall view of all of your organizations. Additionally, it is important to only add a minimal number of administrator accounts to this top level, as accounts added to this level will have access rights to every organization in the system.
An Internal Organization—you can create a separate organization for your company’s own use.
A Customer’s Organization—you can create organizations for each of your customers. Optionally, you can assign organization administrators to specific organizations; these organization administrators will only have privileges to administer the organization to which they have been assigned.
A Suborganization—you can optionally create lower-level organizations that sit under the parent organization. you can optionally create lower-level organizations that sit under the parent organization.
Best Practice: The master organization should remain empty; except for a few trusted administrators, users should not be given access to the master organization, and it should never be configured for internal or customer use.
Best Practice: By default, suborganizations inherit many features and settings from parent organizations, but also allow you to configure different settings. For example:
- If you want to turn on Privacy Mode for one or two users (for example, a CEO), create a suborganization, add this user, and then turn on Privacy Mode at the suborganization level.
- If you want to restrict storage quota for a Team Share, create a suborganization for this Team Share, and configure storage quota policies accordingly.
For information about managing inherited policies, please reference the How to Manage Inherited Policies in Suborganizations Knowledge Base article.