When an object with advanced life cycle is created, team template defined in OIR in particular context is used to populate the roles and participants in the team. The team template is first place where Windchill will look for roles and participants, then it will add the roles/participants defined in the initial state of advanced life cycle. After adding roles from LC, Windchill will see whether this roles are defined in Context team and if a context team role with the same name exists, then the participants that are members of that role in Context team will be added to team. Roles in a team can be used to assign workflow tasks, provide access control (by defining permissions in LC or policy). Out of the box, documents and parts does not have an advanced life cycle state - so there will not be any team instance created.
The recommended approach for defining the team is to list all the roles which are involved in the business process for that object in teamTeam template or LC and use the context team to resolve it to participants.
Short of it is ,If you don't plan to have a workflow for your document or part - then you don't need a team template. If you just need a vehicle to move the documents or parts to its maturity through different LCs, use either promotion or change objects
Regards
Binesh Kumar
Medtronic - MITG
