You define the team members and roles for the product and library local teams that you manage. Each product team has a product manager group and each library team has a library manager group. Any individual that is a member of one of these managers groups has the rights to administer the product or library after it has been created. The creator of a library or product is automatically defined as a member of the product or library managers group, and is identified as the product or library owner, by default.

Controlling the Visibility of Actions

As the product or library manager, you can control visibility to information and actions within the product or library based on the roles in the product or library local team.

For more information, see the teams help.

Overriding Profiles

Moving Objects

Moving objects to a new folder requires different permissions depending on the move being performed. For more information on the permissions required to move an object, see thePTC Windchill Specialized Administration Guide.

Additional Product and Library Team Information

For more information about teams, see Administering Teams on page 182

Managing Folders

You can define folders and links within products and libraries.

By default, only product or library managers can define folders and subfolders in a product or library. This is typically a good policy because it prevents members from adopting a multitude of folder organization models, thereby creating folder chaos.

By default, a folder inherits the domain of the parent folder. You can change this behavior as described in Assigning Domains to Folders in Solutions with Products and Libraries on page 96 .

Managing Templates

You can define the document, CAD document, life cycle, team, option filter, and workflow templates that you want used in the context of a product or library. Each product or library inherits the templates defined by its parent organization context and the site. Additionally, you can create new productor library-specific templates. If the name you specify is the name of an inherited template, then the new template overrides the inherited template that has the same name. You can restrict which templates are made available within your product or library by choosing to hide certain templates. For more information about templates, see Templates on page 75 .

Managing Object Initialization Rules

The use of object initialization rules provides a way to specify the following:

•Default values for the attributes of a specific object type. The default values are then used when a Windchill solution creates objects of that type and the user interface does not set a value. For example, you can set the default values for numbering and versioning.

•Display characteristics that constrain attribute values. If the user interface checks for the constraints, they are then used when the attribute value is displayed in the user interface. For example, the constraints for numbering, and versioning are honored in the user interface.

Viewing and Managing Access Policies

You can view and manage the access control rules for objects (such as folders, parts, and documents) in your product or library. Navigate to the object, and select the Manage Security action. From the Manage Security window you can view and set the access control to the object for roles within your product or library team.

For more information, see the PTC Windchill Specialized Administration Guide and the online help available from the Manage Security window.

You can define policies that control the level of access to information in a product or library. When defining a policy, the object types and user-defined groups defined in the parent organization can be used as well as the system groups representing the team roles in a product or library. For example, you could create a policy that provides read access to all documents of type “Quality Assessment” to the product team role/group called “Testers”. You can also choose to extend read access to this document type to an organizational user-defined group with the name “Quality Assurance” (if such a policy is not already granted at the parent organization level).

For more information about domains and policies, see Administering Domains and Policies on page 85 .

For more information about creating or updating access control rule policies, see the Access Control chapter of the PTC Windchill Specialized Administration Guide.

Configuring Numbering and Versioning Schemes

You can configure the number and versioning scheme used to uniquely identify parts, documents and other objects in the product or library. The numbering and versioning schemes defined at the site and organization level are inherited by products and libraries by default, but each product or library can optionally define its own schemes. Use the Object Initialization Rules Administrator to configure the number and versioning schemes.

In general, when a company is hosting Windchill for its internal use, the numbering and versioning schemes should all be defined in the Site context and should not be overridden by an organization or in a product or library. The Product Design template demonstrates how to set up versioning (and other required functionality) for use in a basic life cycle management environment, where multiple life cycle templates are in use and state-based versioning is set up. If you choose to use this type of environment, consider defining the versioning (and other initialization rules) in the Site context rather than in individual product or library contexts so that all of your products and libraries use the same set of rules.

For more information, see Administering the Numbering of Parts, Documents, CAD Documents, Managed Baselines, and Change Objects on page 104 and Administering the Versioning of Parts, Documents, and CAD Documents on page 105 .

Managing the Life Cycle of Parts, Documents, CAD Documents, and Dynamic Documents

Within your Windchill solution, you have the choice of using a variety of out-of- the-box life cycle templates to help manage the life cycle of parts, documents, CAD documents, and dynamic documents. You can also create your own life cycle template or modify one of the existing templates. The options available to you range from the ability to fully automate the process of promoting a business object through maturity levels with the use of workflow processes to providing manual transition process where users in specified roles can promote objects to new states explicitly through the promote action. Default life cycle templates are established for object types through the use of object initialization rules and a default set of Site rules is loaded during the installation process.

For more information, see thePTC Windchill Specialized Administration Guide

and Understanding Life Cycles on page 299 .

Managing Viewable Publishing

You can monitor and manage the publishing of viewable files that are optionally generated when CAD models are checked into products and libraries. You can also configure and update the watermarks used by the visualization tool when viewing document and part content from the product or library.

For more information, see PTC Windchill Visualization Services Guide.

Managing Preferences

Using the Preference Management utility from Products Utilities or Libraries

Utilities, you can manage preferences at the product or library level. Preferences set at the product or library level affect the product or library for which they are set. Different preferences can be set for different products or libraries.

For example, a number of preferences are available which allow you to determine the types of content allowed for documents. These preferences are found in the

Attachments category of the Preference Management utility.

Undoing a User Checkout

If a user in your product or library has an object checked out, you can undo the checkout, reverting to the last modified version or iteration of the object. This is useful in situations where the user who had the object checked out has left the company, or if they are out of the office when the checked out object is needed.