Accessing Object Templates
Administrators have access to templates from the Templates link from the following locations in the Navigator:
• From > , site administrators can create and manage templates that can then be available from
Site 
and the other contexts.
• From > , site administrators and organization administrators can create and manage templates that can then be available from within the organization.
• From > , site administrators, organization administrators, and product managers can create and manage templates that can then be available from within the product context under which the templates were created. (Windchill PDMLink, Arbortext Content Manager, or Pro/INTRALINK only)
• From > , site administrators, organization administrators, and library managers can create and manage templates that can then be available from within the library context under which the templates were created. (Windchill PDMLink, Arbortext Content Manager, or Pro/INTRALINK only)
• From > , site administrators, organization administrators, and project managers can create and manage templates that can then be available from within the project context under which the templates were created. (Windchill ProjectLink only)
• From > , site administrators, organization administrators, and program managers can create and manage templates that can then be available from within the program context under which the templates were created. (Windchill ProjectLink only)
Out of the box, Windchill provides the following types of object templates:
• Document templates provide content files and default values which are used when users create different types of documents. (Arbortext Content Manager or Windchill PDMLink only)
• CAD document templates define the content and default values which are used when users create CAD documents. (Windchill PDMLink or Pro/INTRALINK only)
• Life cycle templates define the phases and gates associated with various business objects when the objects are initialized.
• Note templates define a starting point for creating notes that contain text and attribute information.
• Report templates define default values which are used when users run reports for change management.
• Team templates define the default roles which are used when users populate teams associated with life cycles.
• Workflow templates define default values which are used when users initiate a workflow. (Arbortext Content Manager or Windchill PDMLink only)
• Task form templates define the variables and general content used in displaying information for workflow activity tasks. (Arbortext Content Manager or Windchill PDMLink only)
The details about how you can access these templates can be found in
About the Templates Table.
> , site administrators and organization administrators can create and manage templates that can then be available from within the organization.
> , site administrators, organization administrators, and product managers can create and manage templates that can then be available from within the product context under which the templates were created. (Windchill PDMLink, Arbortext Content Manager, or Pro/INTRALINK only)
> , site administrators, organization administrators, and library managers can create and manage templates that can then be available from within the library context under which the templates were created. (Windchill PDMLink, Arbortext Content Manager, or Pro/INTRALINK only)
> , site administrators, organization administrators, and project managers can create and manage templates that can then be available from within the project context under which the templates were created. (Windchill ProjectLink only)
> , site administrators, organization administrators, and program managers can create and manage templates that can then be available from within the program context under which the templates were created. (Windchill ProjectLink only)