These groups and any other groups established when your Windchill solution is installed are used during the normal operation of your Windchill solution and should not be removed. Domain-based access control rules can be automatically loaded in the site context /System domain granting permissions to members of these groups, except the Unrestricted Organizations group. The rules for the members of the Unrestricted Organizations group are loaded in the site context /User domain.

Editing Context Participation

Context participation is set by the template selected when the context is created. The roles defined in the template can be modified in the organization context as well as in an application context. Those roles defined in the organization are inherited by the child contexts of the organization.

From within an organization, use the Groups link to add or update user-defined groups and use the Roles link to add or remove roles from the organization.

From within a product, library, project, or program, use the Team link to add or remove roles. From the Members table, you also add and remove members from the roles. For additional information, see Teams and Team Template Administration on page 297 .

Context Policies

Context policy items can include the following domain-based rules:

•Access control rules that establish the access control against specific participant, object type, life cycle state, and domain combinations.

For example, there can be an access control rule for objects with the wt.doc. WTDocument object type in the /Default domain that gives read permission to the Engineers system group.

•Indexing rules that define which collections an object is included in when the object of a specified object type and domain combination moves to a specific life cycle state. Collections are used to create indexing lists which help improve performance when searching for objects.

•Notification rules that define which participants get notified when a specified event occurs for an object type and domain combination.

Contexts provide a means for controlling access to the contained information. In application contexts, access is controlled through context team membership, policy rules, and ad hoc rules. Context contents can be restricted so that access is limited to the members of a context team, or so that the context information can be made more broadly available to the enterprise through policies that grant additional participants (such as users, groups, or organizations) access to specific object types.