Basic Administration > Managing Data > Context Template Administration > Working With Context Templates > Using the Current Context as a Template
  
Using the Current Context as a Template
The recommended method for creating a context template is to create a context (product, library, project, or program) using an existing template and then modify the context settings. After the modifications are complete, select either of the following actions from the details page of the context:
• The Export as Template action is available to the project, product, and library managers as well as the site and organization administrators. The action allows you to export the current product, library, or project context as a template, creating a ZIP file on your system. For the export, a ZIP file containing the framework options you selected is created and downloaded to your system. Depending on your system configuration, you may be prompted to save the ZIP file.
Using the ZIP file as the content for a new template, you can then create a product, library, or project template in the site or an organization context (if you have the correct access permissions) by importing the template. For more information, see Importing a Context Template.
• The Save as Template action is available to site and organization administrators and provides a way to create a new product, library, program, or project template in the current organization context. The type of template created is determined by on the context from which you select the action. For example from a product context, you create a product template and from a project context, you create a project template.
A newly created product, library, program, or project template is saved in the current organization context and appears enabled in the Templates table of that context when the table view is of the type of templates created. For example, library templates are shown when the table view is Library Templates.
(The Export as Template action and Save as Template action are not available for organization contexts.)
An easy way for administrators who are not members of a project to access the project is from the Organizations  > Reports table, which displays all projects within the current organization. For product and libraries, administrators can go to the View All link under Products  and Libraries  access products and libraries.
* 
The Save As action that is available from the details page of each template allows you to save a template with a new name. The content of the new template is the same as the content of the template from which it was saved. The Save As action is only available from the details page if you have been granted Create permission for the context where the template resides. Use the Save As action from the context templates table in a context for which you have Create permission to save a template to that context from a context for which you do not have Create permission.
Selecting either the Export as Template or Save as Template action opens a window from which you do the following:
• Name the template that is being exported or saved.
• Enter a description of the template (for product, library, program, or project contexts).
• For product and library contexts, select which of the following framework options to include in the template data file:
◦ Folder Structure (not including the folder contents). If you created a domain structure, the structure is exported through this option. Also, if you are using folder domains, these folders are exported. Folder domains are available when the Security > Display Folder Domains preference is set to true.
◦ Team Members
◦ Document Templates (Windchill Arbortext Content Manager or Windchill PDMLink only)
◦ Object Initialization Rules
◦ Template Visibility
◦ Preferences
* 
Access policy rules and team roles are automatically included in the template.
• For project and program contexts, select which of the following framework options to include in the template data file:
◦ Folder Structure (not including the folder contents)
◦ Folder Links and Structure
◦ Project Plan
◦ Deliverables
◦ Team Roles
◦ Team Members
◦ Documents
◦ Document Templates (Windchill Arbortext Content Manager or Windchill PDMLink only)
◦ Discussion Spec
◦ Discussion Template
◦ Object Initialization Rules
◦ Template Visibility
◦ Preferences