Lietotāja rokasgrāmata Atcelt

Manage organization hierarchy

Meklēšana

Pēdējo reizi atjaunināts 2024. gada 18. jūn.

Adobe Enterprise & Teams: administrācijas ceļvedis
Plānojiet savu izvietošanu
1. Pamatjēdzieni
2. Izvietošanas rokasgrāmatas
3. Izvietot Creative Cloud izglītības iestādēm
Iestatīt savu organizāciju
1. Identitātes veidi | Pārskats
2. Iestatīt identitāti | Pārskats
3. Iestatīt organizāciju, izmantojot uzņēmuma ID
4. Iestatīt Azure AD federāciju un sinhronizāciju
5. Iestatīt Google federāciju un sinhronizāciju
6. Iestatīt organizāciju, izmantojot Microsoft ADFS
7. Izveidot organizāciju rajona portāliem un LMS
8. Izveidot organizāciju kopā ar citiem identitātes nodrošinātājiem
9. SSO bieži uzdotie jautājumi un problēmu novēršana
Pārvaldiet savas organizācijas iestatījumus
Pārvaldīt lietotājus
1. Pārskats
2. Administratīvās lomas
3. Lietotāju pārvaldības stratēģijas
4. Piešķiriet licences Teams lietotājam
5. Lietotāju pārvaldība komandām lietotnē
  1. Pārvaldiet savu komandu programmā Adobe Express
  2. Pārvaldiet savu komandu programmā Adobe Acrobat
6. Pievienojiet lietotājus ar atbilstošiem e-pasta domēniem
7. Mainīt lietotāja identitātes veidu
8. Pārvaldīt lietotāju grupas
9. Pārvaldīt direktoriju lietotājus
10. Pārvaldīt izstrādātājus
11. Migrējiet esošos lietotājus uz Adobe Admin Console
12. Migrējiet lietotāju pārvaldību uz Adobe Admin Console
Pārvaldiet produktus un tiesības
1. Pārvaldiet produktus un produktu profilus
2. Pārvaldīt koplietojamo ierīču licences
Sākt darbu ar Global Admin Console
Pārvaldīt krātuvi un līdzekļus
1. Krātuve
2. Līdzekļu migrācija
3. Atprasīt līdzekļus no lietotāja
4. Studentu līdzekļu migrācija | Tikai EDU
  1. Automātiska studentu līdzekļu migrācija
  2. Migrēt savus līdzekļus
Pārvaldīt pakalpojumus
1. Adobe Stock
2. Pielāgotie fonti
3. Adobe Asset Link
4. Adobe Acrobat Sign
5. Creative Cloud uzņēmumiem — bezmaksas abonements
  1. Pārskats
Izvietojiet lietotnes un atjauninājumus
1. Pārskats
2. Izveidot paketes
3. Pielāgot paketes
  1. Pielāgot Creative Cloud datora lietotni
  2. Paketē iekļaujiet paplašinājumus
4. Izvietot pakotnes
5. Pārvaldiet atjauninājumus
  1. Izmaiņu pārvaldība Adobe uzņēmumu un komandu klientiem
  2. Izvietot atjauninājumus
6. Adobe Update Server Setup Tool (AUSST)
7. Adobe Remote Update Manager (RUM)
  1. Laidiena apraksts
  2. Izmantojiet Adobe Remote Update Manager
8. Problēmu novēršana
Pārvaldiet savu Teams kontu
Atjaunojumi
1. Teams dalība: atjaunošana
2. Uzņēmums VIP: atjaunošana un atbilstība
Pārvaldīt līgumus
Pārskati un žurnāli
Saņemiet palīdzību

Learn how global administrators can manage the organization’s hierarchy in the Global Admin Console.

After you have access to the Global Admin Console, you can create new organizations, add existing ones to the structure, delete organizations, and change the parent organization.

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)

Sign in to the Global Admin Console. In the Organizations tab, select the organization you want to add a child organization to.
Select the Add icon.
Specify a name and the country of the organization.

The organization's simple name must be between 4 to 100 characters, maximum length for pathname is 255 characters.
Select Save.
Select Review Pending Changes after you are done editing the organizations. After reviewing, select Submit Changes to execute them.

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.

Uzmanību!

Deleting an organization impacts your users. Ensure that there is no access or information that will be lost when an organization is deleted.

Sign in to the Global Admin Console. In the Organizations tab, select the organization you want to delete.
Select the Delete icon.
Select Ok in the Delete Organization pop-up screen that appears.
Select Review Pending Changes after you are done editing the organizations. After reviewing, select Submit Changes to execute them.

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.

Uzmanību!

If products are removed as a result of reparenting, users lose access to those products.

Sign in to the Global Admin Console. In the Organizations tab, select Change hierarchy to enable reparenting the organizations.
Select Ok in the pop-up screen that appears.
To reparent, drag the child organization on top of the desired organization.
Select Save when you are done reparenting your organizations.
Select Review Pending Changes after you are done editing the organizations. After reviewing, select Submit Changes to execute them.

Once the job is complete, you can navigate to Product Allocation and change the grant values to reflect the change in allocation of product resources.

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.

Uzmanību!

You can only add child organizations to root organizations that are based on the same storage model. So, child organizations based on the user storage model can only be added to root organizations based on the user storage model. And, child organizations based on the enterprise storage model can only be added to root organizations based on the enterprise storage model.

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.

Sign in to the Global Admin Console, and navigate to Organization Mapper.
Select a parent organization from the drop-down list.

These are the organizations for which you are directly added as a global administrator. In the drop-down list, if you don't see an organization you want to use as the parent, select one higher up in the hierarchy. Once the Organization mapper operation is complete, you can use Change hierarchy to move the new organization down in the tree to have the parent you want to use.
Select the organizations to be added as children of the organization selected in the previous step.
Select Review Pending Changes. Then, select Submit Changes to execute them.
After executing the changes, you can repeat the above steps to add additional child organizations to your organization hierarchy.

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