Portfolio Definition Access to Content

Portfolio Definition uses direct access responsibilities, instead of baseline behavior responsibilities, to determine whether you can access a specific portfolio version or sellable item, and whether you have permission to perform specific actions on it. For more information, see Controlling Direct Access to Content.

This page discusses:

Content Creation

Any user with the Portfolio Manager role can create a portfolio version or sellable item. The user who creates the portfolio version or sellable item is automatically assigned the Owner responsibility for it. Each portfolio version or sellable item is accessible only by its Owner when it is created.

Responsibilities

The Owner of the portfolio version or sellable item can share the portfolio version or sellable item with other users and user groups to assign them one or more responsibilities. Each responsibility defines a group of permissions for a specific object, including the ability to access it. For more information, see Sharing Objects with Other Users.

The following responsibilities and permissions are available for portfolio versions and sellable items:

Permissions Responsibilities
Owner Manager Contributor Reader
Create
Search
View
Add or remove related project plan1
Set or unset governing project
Modify image and properties
Add, remove, or replace content2
Attach and detach documents3
Delete
Create new revision or branch
Manage maturity
Create from existing
Share and revoke responsibilities from other users or groups
Transfer ownership

1 The Add or remove related project plan permission is tied to your permission to contribute to the project plan and your access to add or remove it from other objects. These permissions are managed by the app and collaborative space in which the project plan was created. In Portfolio Definition, you must have at least the Reader responsibility for the project plan; otherwise, it is not visible to you.

2 The Add, remove, or replace content permission is tied to your permission to view the object you want to add to the portfolio version's or sellable item's content. These permissions are managed by the app, and sometimes the collaborative space, where the object was created.

3 The Attach and detach documents permission is tied to your permission for the document itself and depends on the source of the document:

  • A 3DSpace document's permissions are controlled by its collaborative space and your responsibilities in that collaborative space. You must have a responsibility that allows you to view the document in the collaborative space to add it to the content of a portfolio version or sellable item. You must have additional responsibilities to create a document in that collaborative space to be able to upload and create a document in portfolio version or sellable item content.
  • A 3DSwym post's permissions are controlled by its 3DSwym community and your responsibility in that community. You must have a responsibility that allows you to view the post in the community to add it to the content of a portfolio version or sellable item.
  • A 3DDrive document's permissions are controlled by its 3DDrive folder and your responsibility for the folder. You must have a responsibility that allows you to view the document in the 3DDrive to be able to add it to the content of a portfolio version or sellable item.
Note: The app where an object is created determines the permissions available for that type of object in Portfolio Definition under the following conditions:
  • The associated object was created in and is managed by another app.
  • The object is associated with or attached to a portfolio version or sellable item.
  • The associated object's collaborative space and responsibilities are controlled by another app.
For Portfolio Definition, these objects are documents and project plans.

Content Lifecycles

Portfolio versions and sellable items have the following lifecycle maturity states:

  • Private
  • In Work
  • Under Review
  • Released
  • Obsolete
Anyone with the Owner or Manager responsibility can change a portfolio version's or sellable item's lifecycle maturity state. Access to content is not dependent on the lifecycle maturity state. Access to actions is dependent on the content's lifecycle maturity state.
Actions Maturity State
Private In Work Under Review Released Obsolete
Create
Search
View
Add or remove related project plan
Set or unset governing project
Modify image and properties
Add, remove, or replace content
Attach and detach documents
Delete
Create new revision or branch
Manage maturity
Create from existing
Share and revoke access to other users or groups
Transfer ownership