Administración especializada > Seguridad de los datos > Access Control > Managing Access to Enterprise Information > Foldered Information > Domain Inheritance for Foldered Objects in Windchill
  
Domain Inheritance for Foldered Objects in Windchill
The domain association for a foldered object is inherited from its parent, unless a domain has been explicitly associated with the foldered object.
For example, assume that the following structure exists:
• A subfolder named Technical Documents, belongs to the /TechDocs domain.
• A subfolder named Installation Guides (located in the Technical Documents subfolder), inherits its domain from its parent subfolder.
In this example, both the Technical Documents and Installation Guides subfolders are governed by the policies defined in the /TechDocs domain.
The following rules govern the movement of subfolders within the same context:
• If the subfolder inherits its domain, the subfolder and all its folder members that also inherit their domain are governed by the administrative policies in the domain associated with the subfolder’s new parent, when it is moved. For example, if the Installation Guides subfolder was moved to another cabinet or subfolder, this subfolder and the folder members of the subfolder that inherit their domain from the subfolder would then be associated with the domain of the new parent.
• If the subfolder belongs explicitly to a domain, it continues to belong to that domain when it is moved. For example, if the Technical Documents subfolder is moved to another cabinet or subfolder, its domain remains unchanged and both the Technical Documents and Installation Guides subfolders and the folder members of the subfolders that inherit their domain from the subfolders are still governed by the administrative policies of the /TechDocs domain.
• When you change a subfolder to inherit its domain, the domain of the subfolder, and all its folder members that inherit their domain, are changed accordingly. For example, if you change the Technical Documents subfolder to inherit its domain, then both the Technical Documents and Installation Guides subfolders are associated with the /Documents domain.
If you want to ensure that a subfolder retains the same domain association as its current parent, even if it is moved, you must explicitly associate the subfolder with the domain of its current folder.
If you attempt to move a subfolder to a different context and the subfolder belongs explicitly to a domain, a conflict will be raised with several retry options. The following options are available:
• The subfolder can be explicitly assigned to the same domain path as in the source context, if the same domain path is available. For example, the Technical Documents subfolder is moved to another context that also has the /TechDocs domain. The domain association for the Technical Documents subfolder can be set to the /TechDocs domain in the new context. The Technical Documents subfolder and the folder members of the subfolder that inherit their domain from the subfolder would then be associated with the /TechDocs domain in the new context and governed by the policies defined in that domain.
• The subfolder can be explicitly assigned to the /Default domain in the target context. For example, the Technical Documents subfolder is moved to another context, but the /TechDocs domain is not available in the target context. The domain association for the Technical Documents subfolder can be set to the /Default domain instead. The Technical Documents subfolder and the folder members of the subfolder that inherit their domain from the subfolder would then be associated with the /Default domain in the new context and governed by the policies defined in that domain.
• The subfolder can be explicitly assigned to the same domain as the parent folder into which it is moved in the target context. For example, the Technical Documents subfolder is moved to another context under the All Publications subfolder, which belongs to the /Documents domain. The domain association for the Technical Documents subfolder can be set to the /Documents domain. The Technical Documents subfolder and the folder members of the subfolder that inherit their domain from the subfolder would then be associated with the /Documents domain in the new context and governed by the policies defined in that domain.
For more information about resolving conflicts, see Managing Conflicts.
To change the domain of a subfolder, the user must have the Change Domain permission for the subfolder in the source domain and the Create By Move permission for the subfolder in the target domain. To change the context of the subfolder, the user must have the Change Context permission for the subfolder in the source domain. For more information, see Permissions Required for Moving Objects.