Manage organization hierarchy

An organization (org for short) is a structure used to manage Adobe products and users. The Adobe Admin Console lets administrators manage the deployment and configuration of products and users in their organizations. The Global Admin Console lets global administrators create, manage, and delete multiple orgs.

Create a child organization

As a global administrator, you can create child organizations of any organization in the hierarchy and set the name, country, user groups, products, product profiles, administrators, and policies.

When a new child organization is created, the following are automatically inherited from the immediate parent:

• Organization's policy settings (including locks if present)
• The list of system administrators (controlled by Inherit System Admins on creation policy). The following can prevent system administrators from being inherited:
  • Lack of domain trust
  • User type restrictions (Add Adobe ID/ Enterprise ID/ Federated ID users policies). Learn about the policy details.
    
• Access to FederatedId or EnterpriseId users from domains to which the parent org has access. This makes the domain users in the parent available in the child org. Inheritance of user access is controlled by Inherit users from directories managed by the parent organization policy.
• Sharing policy, password policy, and security contacts (controlled by Inherit asset sharing settings when child organization is created policy)

Delete a child organization

As a global administrator, you can delete child organizations. The delete operation cannot be undone, and the root organization cannot be deleted. The resources allocated to the deleted organization are returned to its parent. Also, before an organization is deleted, its parent becomes the parent of its child organizations, if it had any.

An organization can be deleted only if the following criteria are met:

• There are no Sign accounts, Adobe Stock purchases, or storage repositories in the organization.
• There are no claimed domains in the organization.
• There are no instantiated products in the organization.
• There are no Experience Cloud products which can include instantiations in the organization.

Change the parent of an organization

As a Global Administrator, you can reparent an organization in the organization hierarchy using the Change hierarchy button. 

Changing the parent of an organization has the following impact:

• Reparenting an organization moves the entire subtree rooted at the reparented organization with it. The pathnames of the reparented organization, and its children are updated to reflect their new location.
• Organization policies of moved organizations are updated so that any locks on policies are held by an organization in the new hierarchy.
• Changing the position of an organization in the hierarchy can change the global administrators for that organization. Global administration roles are inherited down the hierarchy so any global administrators of the new parent organization automatically become global administrators of the moved organization. Likewise, global administrators can lose their role in the moved organization if they had that role by virtue of being a global administrator of the old parent. The inherited global administration roles are not listed in the Admins pane of the organization.
  
• Reparenting also affects the available products in the moved organizations. When possible, product allocations are updated so they come via the new parent location.
• If product allocations cannot be updated to come from the new parent, the products are removed along with the product profiles of those products. Users can lose access as a result of this operation. For the product to be available in the new location, the closest common ancestor of the old and new locations must have the product available.

Add existing organizations using the Organization Mapper

As a Global Administrator, you can add existing organizations that are not currently part of your Global Admin Console hierarchy to the organization hierarchy.

You can also add team organizations to the org hierarchy. Team orgs don't participate in product allocation or product usage rollup, and management of team organizations in the Global Admin Console is limited. You can add them to the org hierarchy to keep track of them and have visibility into the products they purchase. Team organizations cannot have child organizations under them and don't have many of the features of enterprise organizations.

Learn more about the limitations on product allocation.

The Organization mapper tab shows:

• In step 1, a dropdown with a list of possible parent organizations under which you can add a child. These are organizations that you are a global administrator of.
• In Step 2, it shows you a list of child orgs that can be added under the parent you selected in Step 1. These are organizations that you are a system administrator of and that are not already a child of another organization.
  

When an organization is added to global administration, products in the organizations that are added using Organization mapper remain as purchases, Product Allocation numbers stop rollup at these organizations.

Once an organization is in the hierarchy, you can adjust organization policies, administrators, or other settings by navigating to the Organizations tab.