Teams
Teams and team templates are used throughout Windchill.
To manage teams, you need to be aware of the different ways that teams are used in Windchill.
• When business objects (such as parts and documents) are created, a unique team is created as its own object and is associated with the business object. This team contains all the roles consolidated from the team, life cycle, and workflow templates. The roles get mapped to end users; ad hoc access permissions can be defined for the participants in the life cycle and workflow templates. For more information, see Team Association Rules.
• At the context level, the manager can create a context team specific to a particular project, library, program, or product. Each context team identifies the members of the specific project, library, program, or product and assigns the members to roles that have been established in the context. Each context team can be made up of a local team, a shared team, or the combination of a local team and shared team. For additional information about context teams, see About Context Teams.
Context teams are also used when creating the team that is associated with a specific business object. For additional information, see Team Roles Resolution.
A team template is an object managed by administrative users. This object can map participants and actor roles to roles. The team template can be assigned to a life cycle or workflow-managed business object, when it is created, to use as a template for roles resolution for the team.
 |
Windchill ProjectLink does not use team templates.
|
For more information, see Team Template Administration.
To understand teams, you should be familiar with the following terms:
• A participant is an individual user, group, or organization. A participant is also an actor that has been mapped to a specific role in a team.
• A role is a function that can be fulfilled by some participant. A role is mapped to participants. A list of predefined roles is available when you define a team.
• An actor represents a user who performs a specific action within the context of a specific business object. Currently, Creator is the only actor defined.
Teams are managed through the Teams page, which is accessible in each application context. To navigate to the Teams page, you must be a member of the context team. Others who are not members of the team but who have permissions to modify the team can search for the application context using an advanced search.