An organization context can define a number of document, life cycle, and workflow process templates that can be used by all the application contexts within the organization. To ensure consistency and maximize efficiency, an organization may want to define templates for specifications, presentations, reports, proposals, meeting minutes, and so forth. Life cycle and workflow process templates may be associated with each of the defined templates. Each organization inherits the templates defined in the site and can either use these site-defined templates or override them by defining organization-specific templates with the same name.

The organization can inherit the product, library, project, and program templates defined at the site level, or you can override these templates by defining templates for your organization. If Windchill ProjectLink is installed, you can create project and program templates. If Windchill PDMLink is installed, you can create product and library templates. For more information, see Understanding Context Templates.

You can restrict which templates are made available to the applications within your organization by choosing to hide certain templates at the organization level. By only hiding templates, you limit the templates displayed by default and still allow context managers to override which templates are hidden in their particular application context. If you want to prevent a template from being used, you can disable it.

For more information, see Working with Object Templates and Working With Context Templates.