Share a project in Adobe Workfront

Your Adobe Workfront administrator can grant you access to view or edit projects when assigning your access level. For more information, see Grant access to projects.

Along with the access level that users are granted, you can also grant them permissions to View, Contribute, or Manage specific projects that you have access to share.

Permissions are specific to one item in Workfront and define what actions one can take on that item.

Considerations about sharing projects

In addition to the considerations below, also see Overview of sharing permissions on objects.

  • By default, the creator of a project has permissions to manage the project and is also designated as the Project Owner. If the project is assigned to another owner, that user also has permissions to manage the project. When the project creator (or owner) shares the project with other users, they grant certain permissions to those users to control what they can do as they work on the project.

    However, if a project owner does not have a Planner license, they do not have full access to manage the project. Only a user with a Plan license can have permissions to manage a project. For more information, see How access levels and permissions work together.

  • You can share projects individually, or you can share several of them at a time. Sharing projects is identical to sharing other objects. For more information about sharing items in Workfront, see Share an object.

  • You can grant the following permissions to a project:

    • View

    • Manage

    • Contribute

  • When you share a project, all the tasks, issues, and documents inherit the same permissions, unless otherwise specified.

    For information about managing the access to tasks and issues on the project based on a user’s permissions to the project, see the section in the article Edit projects.

    The Workfront administrator can specify whether documents should inherit permissions from higher objects in the user’s access level. For more information about restricting inherited permissions on documents, see Create or modify custom access levels.

  • You can remove inherited permissions from a project so that the children objects will not inherit them. For more information about removing inherited permissions from objects, see Remove permissions from objects.

Ways to share a project ways-to-share-a-project

You can share a project in the following ways:

  • Manually by doing one of the following:

    • Adding users to the project team. When you add users to the project team, they automatically obtain View permissions to the project.
      For more information about adding users to a project team, see the “Adding Users to a Project Team” section in Project Team overview.

    • Individually or bulk-sharing the projects when using the Sharing option.

      Sharing a project is similar to sharing all other objects in Adobe Workfront.

      For information about sharing objects in Workfront, see Share an object.

  • Automatically, by doing one of the following:

    • Place a project in a Portfolio or Program that is already shared with others. Users gain the same permissions to the project that they have for the portfolio or program.
      For information about adding a project to a Portfolio, see Add projects to a portfolio.
      For information about adding a project to a Program, see Add a project to a program.

      For information about viewing inherited permissions on an object, see View inherited permissions on objects.

    • Add entities to Project Sharing on a template used to create the project. For information about sharing projects from templates, see Share a template.

    • Define the project access template.

      To define the project access template, see Share an object.

      note tip
      When attaching or saving a template, you can clear the Template Project Sharing rules.
    • Edit a project and defining the When someone is given access to this project setting. For more information, see Edit projects.

Limitations for different license types

  • Users with a Worker license don’t have permissions to manage projects. For Workers, the highest sharing permission is Contribute.
  • Users with a Request license can view project information, but they have limited project access.
  • An exception to changing the status of a project occurs when a user with View or Contribute permissions is also included in an approval process. They can approve the project, which changes the status of the project, but the status is the predefined status for approval or for rejection.
  • To be able to copy a project, a user must also have access to create projects in their Access Level.

Project permission options

The following table lists the permissions that users can grant when sharing a project. For more information about the access users get based on their license, see Grant access to projects.

Add Custom Form
Update Custom Fields
Add An Approval Process
Approve a Project
Approve hours
Create A Project
Add Document(s)
Add Issue(s)
Add Task(s)
Copy Project
Delete Project
Modify Planned Dates
Share Project
Share System-wide
View Project
Updates/ comments
Change Status
Log Hours
Edit Assignments
Manage Baseline
Manage Risks*
Manage Finance*
Add/ Edit Expenses*
View Finance*
Attach Template
Save As Template
Add/ Edit Business Case
Edit Project Details
Edit Staffing
Export to MS Project
Recalculate Finance/ Timeline*
Set Queue Properties
Edit Project in Bulk in a List

*Users without access to financial data cannot manage risks and finances for projects, even if they have Edit access to projects. For information about access to financial data, see Grant access to financial data.