Managing Access to Data through Team Memberships
Another aspect of managing user access to data can be found in managing who becomes a member of an application context. The context team associated with a product, library, project, or program establishes which users are members of a specific application context. A context team can be made up of the following teams:
• A shared team that is established by the site or organization administrator (or by others given the rights to create shared teams) in the context of an organization and selected when creating the application context.
• A local team that is established by the application context manager as part of creating and managing the application context.
• Both a shared team and a local team.
Team members are added to a shared team according to their established role in multiple application contexts. For example, you could have a group of engineers who fill the Design Engineer role for many of the products or projects managed by your organization. This user-defined group could then be added to a shared team that is then selected when the application context is created.
Team members are added to a local team according to their role in a specific product, library, program, or project. For example, you could have an individual who will be in the Reviewer role for only a specific product or project. Then, this individual could be added to the local team for that product or project. The initial roles that are available for shared and local teams are determined when the teams are created; however, additional roles can be added.
For each role used in a context team there is a corresponding system group created that administrators can use to create access control rules for the members assigned to the role. The
Team link under
Products 
,
Libraries 
,
Programs 
, or
Projects 
in the
Navigator provides access to the interface for managing local teams. > provides access to the interface for managing shared teams. Use the
Policy Administration utility to create access control rules.
Your
Windchill solution also uses roles and corresponding users defined in life cycle templates and team templates (if they are defined for an object). For additional information about teams, see
Teams.
For additional information about access control rules, see
Administering Domains and Policies.
> provides access to the interface for managing shared teams. Use the Policy Administration utility to create access control rules.