Product and library administrators (also known as product and library managers) are responsible for managing product and library contexts. The capabilities of product and library administrators are nearly identical.

Product and library administrators control the product and library configuration, and the membership in their product and library teams within the confines of a specific product or library application context. They control access to product and library information. They define the specific life cycles, templates and processes, and they monitor and manage the product and library activities.

Product application contexts are used to define new product models or instances and collect all the information associated with the product. Product contexts are defined by product creators who are authorized by the parent organization under which a product is created. Products inherit templates, roles, user-defined groups, and policies from their parent organization context. In addition, the administrator can define product-specific templates, roles, and policies.

Library application contexts are used to manage standard parts and documents that are used across products and projects in an organization. Library contexts are defined and managed by authorized library creators in the parent organization under which a library is created. Libraries inherit templates, roles, user-defined groups, and policies from their parent organization context. In addition, the administrator can define library-specific templates, user-defined groups, roles, and policies.

If Arbortext products are installed in your environment, product and library contexts can be used to manage dynamic documents and the published documents created from dynamic documents.

For more information about context contents and how to create contexts, see Contexts – Distributed and Hierarchical Administration.