Structure items identify the domains, cabinets, folders, notebook folders, discussion topics, and reference folders for notebooks that are in the context and the domain inheritance scheme that is in place. Contexts define a structure in which related information is organized. This structure can be represented by a domain hierarchy, folder hierarchy, product structure hierarchy, collection of discussion topics, or predefined milestones in a schedule. The structure defined by the context enforces consistency and improves efficiency.

The use of the context structure is very apparent when you look at how domains can help organize rules for users. For example, the Administrator user is associated with the site context /System domain and, therefore, is segregated from other users by default. The other users are associated with child domains of the /User domain. The User domain is in the site context, and the child domains of the /User domain can be in the site context or in an organization context.

The site context has the top-level / (root) domain, the /System, /Default, /User, and /SessionIterationDomain domains that are children of the root domain, and the /Unaffiliated domain that is a child of the /User domain. (For an explanation of these domains, see Administering Domains and Policies.)

For Windchill PDMLink, Arbortext Content Manager, and Pro/INTRALINK, there are no folders installed in the site context.

For Windchill ProjectLink, the following folders, which are associated with /Default domain in the site context, are installed:

The context structure is set either by the load files used (in the case of the site context) or by the template selected when the context is created. The template (and its underlying code) sets the domains, cabinets, folders, notebook folders, discussion forum topics, and reference folders that are in the context and the domain inheritance scheme, which identifies parent and child domain relationships.

Although you can modify the set of domains in a context using the Policy Administration utility, you should refrain from doing so unless the purpose of the domain is clearly defined. For example, a new domain may be needed to provide a unique set of access control policy rules for a specific folder.

Windchill solutions do not expose the creation of cabinets through their user interface. Use the default cabinets defined. Administrators can update the set of folders available in a context by navigating to the specific product, library, project, program, or organization and then clicking the Folders link. Similarly, discussion forum topics can be created in a product, library, project, or program by clicking the Discussions link that is available from the product, library, project, or program.