Global Administration | Set up organizations

Following are some key terms and concepts:

Navigation bar

The Global Admin Console acts as an organization's central management hub for Adobe resources. Global Administrators can create child organizations under their organization and assign System Administrators to manage them.

Resources can be distributed to child organizations for management and assignment to users in those organizations. Users and administrators in an organization do not have visibility to users, storage, or other resources outside their organization.

Organizations tab

An organization (org for short) is a structure used to manage Adobe products and users. The 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.

To view and modify product profiles, user groups, administrators, and organization's policies, see Edit organizations.

System restrictions

Select your organization

Execute jobs

Changes in the Global Admin Console are done in two phases, making changes to the organizations or allocating products as needed, then reviewing and executing these changes from the Job Execution tab.

You can sign out and back in or even refresh the page without losing edits. Unexecuted changes are discarded after 30 days. However, pending changes are cleared if you close the browser tab or window.

As a Global Administrator, you can review the list of changes and initiate the execution, or continue to make changes. To execute the changes, do the following:

Job history

To view the jobs executed in the past 30 days, do the following:

Create an organization

As a Global Administrator, you can create child organizations of any organization in the hierarchy. You can set the name, country, user groups, products, product profiles, administrators, and policies for the new organization.

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 an 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 below 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 on the moved organization if they had that role by virtue of them 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 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 do not 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 purchased. Team organizations cannot have child organizations below them and do not 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.

Export and import organization structure

As a Global Administrator, you can export the organization hierarchy. You can download a JSON, CSV, or XLSX representation of the entire organization hierarchy, or a subset of it. You can then use this data to analyze or make modifications.

Similarly, you can import potentially modified data. When uploaded, the new data is compared with current data and any changes are applied to the organization hierarchy.

Export the organization structure

The export format chosen impacts the structure of the exported data.

• CSV format allows exporting only one kind of data at a time. When exporting product profiles in CSV format, the profiles and resources are combined into one table. There are multiple entries for the product profile, one for each resource.
  
• XLSX format results in each organization detail displaying in a separate sheet.
  Records are connected between the different object types by a reference id. In some cases, there may be multiple rows for a particular object, such as in the case of Resource objects when there are a set of values associated with a given resource.
  
• JSON format is the most flexible. It can take advantage of structural relationships between exported objects. For example, products in an organization appear directly in the organization element. The same fields are exported in all three formats but some values are redundant in the JSON format.

Import the organization structure

All import operations are performed on the updated copy of the organization hierarchy. If you have any pending changes, the import changes will be added on top of the pending changes in the hierarchy.

Export and import schemas

While importing data using a CSV file, the fields can appear in any order but must always match their header row. 

While importing data, you must specify an operation for each element. The operation can be any one of the following:

• Update: indicates an edit.
• Create: indicates to creating a new object (For example, organization, user group, or administrator).
• Delete: indicates deletion of an object (For example, organization, user group, or administrator).

Input records with no or blank operation field are ignored.

More like this

Once the organization hierarchy is set, you can edit the organizations and allocate products to the organizations. If you still don't have access to the Global Admin Console, submit a support case using your Admin Console to request the same.

• Global Administration | Overview
• Edit organizations
• Allocate products
• Explore insights