Three Types of Shared Access

Data Management Capabilities > Exchanging Data Between Contexts > Three Types of Shared Access

There are three types of share access you can grant for an object. Each share type provides different levels of access to project team members.

You determine the share type when adding objects to a project:

• If you are adding PDM objects to a project, the share type for each object is displayed in the Selected Action column of the Collect Objects and Set Options table. Use the actions provided on the table toolbar to change share types.

• If you are sharing objects between two projects, use the options available in the Paste Type window to determine share type.

Contexts	Available Share Types
Library > Project Product > Project	Shared PDM Checkout Copied document
Project > Project Program > Project	Shared Copied document

For instructions on how to share an object, see Actions to Exchange Objects.

For a summary of access permissions necessary for each share type, see Permissions and Valid Object Types.

Copied Documents

When you share a document between contexts, you can elect to copy the document as a new object. The new document object retains its original content and attributes. This is similar to a Save As action.

The new document can be changed within the project, independent of the original document, and later sent back to PDM as a new object.

Shared Objects

Shared objects are available in the project folder and team members are given read-only access to the object. Shared objects can only be downloaded; they cannot be checked out to a workspace or modified within the project context. For more information, see Managing Shared Objects.

PDM Checkout Objects

You can check out a PDM object to several projects simultaneously. If an object is checked out to multiple projects, only one project can use the Send to PDM action on the object. For more information, see Managing PDM Checkout Objects and Sending Objects to PDM.

Checking out an object from PDM to a project creates a project-specific version of the object. Project team members can edit the object and later send it back to PDM. The object remains locked in PDM until the project work is complete.

For a more detailed use case example using multiple design scenarios, see Use Case Example for PDM Checkout.

You can share PDM checkout objects from one project to another project using the Copy action.