Project and Task Governance
Updated
Platform Governance now centrally manages Project and Task creation/editing permissions, ensuring consistent access control across project and content management workflows. To create or view Projects and Tasks within a Portfolio/Project, users must have:
Permissions at the Global or Workspace level, and
Admin or Viewer access to the specific Portfolio or Project.
This article outlines the permissions associated with different access levels across Global/Workspace roles, and
Portfolio/Project-level roles (Admin/Viewer).
Portfolio Access Levels
Project Permissions
Project Permissions through Global & Workspace Roles: These permissions define what action a user can perform and are not specific to any particular project.
View
Edit
Create
Archive/Unarchive
Delete
Share
Clone
Note:
Creator access at the portfolio level no longer allows users to create projects. Users need the Create Project permission from Global or Workspace roles.
Users can only create projects in portfolios they own or that are shared with them (as Admin or Viewer).
Users must be Portfolio collaborators (Admin or Viewer) to create projects within that portfolio.
Project Access at the Entity Level: Entity-level permissions determine where a user can take action—specifically, within individual projects. To create a project within a portfolio, a user must be added as a collaborator (Admin or Viewer) on that portfolio.
The table below outlines the specific actions users can perform in a project, based on their assigned access level.
Note: Analytics Tab is governed via Reporting permissions in Global/Workspace roles, and not dependent on Collaborator Access on Project Level.
Task Permissions
Creating and editing tasks requires a combination of:
Admin or Editor-level access to the project, and
Appropriate Global/Workspace-level Task permissions.
Task Permissions in Global/Workspace Roles: