Child Organizations
You can use parent-child associations to represent hierarchical relationships among organizations. Parent-child relationships enable you to collectively administer certain aspects of the associated organizations. For example, after you establish a parent-child relationship between organizations, administrators can collectively grant roles and permission to users that belong to a parent organization or any of its children. The administrator of a parent organization also has administrative control over the organization's descendants, the parent organization can manage users, assets, policies, lifecycles and so forth within the parent organization and all of its descendants.
To create a parent-child relationship, you must create the child organization from within the parent organization. A child organization does not inherit any characteristics from its parent. It has its own administrator, although the administrator of the parent organization also has administrative privileges in the child organization and it has its own set of users, policies, lifecycle models and assets. A child organization can have additional child organizations of its own.
As you define the organizational structure for your registry, identify organizations that you want to relate in a hierarchical form and use parent-child relationships to reflect the hierarchy.
When defining your organizational structure, keep the following points in mind with respect to parent-child relationships:
A child organization can belong to only one parent.
You must create the parent organization first and then create the child from the parent. In other words, you cannot create two unrelated organizations and then, at a later time, establish a parent-child relationship between them.
Once you associate organizations in a parent-child relationship, you cannot disassociate the organizations.
You cannot move a child organization to a different parent.
You cannot promote a child organization to become top-level parent organization.
A child does not inherit properties or objects from its parent and organization administrators in the parent organization are automatically allowed to administer the child organization. The parent's organization specific policies and lifecycles do not apply to its children. A child organization creates and maintains its own policies and lifecycles independent of its parent. In this respect, it is like any other organization. To impose policies and lifecycles on all organizations in the registry, you can create system-wide policies and lifecycles.
