Issue Permissions


Users are first given system-wide access to perform specific actions, through the access level they are assigned to. For example, the ability of creating issue is given through the access level of the license assigned to the user. Then, users can gain access to specific issues by other users sharing the issues with them. 

For more information about the various layers of the Workfront access model, see "Understanding the Access Model." 

Issue Access by License Type

The level of access around issues is defined at the system level by the license type the user is assigned to. For example, Reviewers cannot log time and Workers cannot share system-wide. Keep these things in mind when sharing issues with these users. 

For more information about issue access for various license types, see "Issue Access."

The owner and the creator of an issue has default Manage permissions, within the limits of their access level. As the owner or the creator of an issue, you can share access with other users through permissions. 

Issue access is also controlled through object hierarchy. If the user already has permission on the parent object, like a project or a task, those permissions will transfer to the issue.  Users who have permissions to an issue coming from the parent objects of the issue are listed under Inherited Permissions.

Issue Permissions on Request Queues

Permissions can automatically be granted to users when they submit a request to a Request Queue. During the creating of a request queue, identify what permissions users will be granted when they submit a request. 

Furthermore, determine whether people within the same company will have the right to view each others submitted requests.

Issue Permissions

You cannot give a user permissions that are higher than their access level. For example, External Users have no access to view issues at all, so you cannot share issues with them.

If the access level allows a user to create issues, they automatically have Manage permissions on the issues they create. Outside the issues they create themselves, they can only View, Contribute, or Manage issues that are shared with them. 

The owner of an issue typically shares permissions with other users through sharing. When sharing permissions, owners determine the level of access users have to the issue.

They have the following options to choose from:

The following table displays the permission options for issues and it should be read with issue access level in mind. For more information about the access users get based on their license, see "Issue Access."

Actions Manage  Contribute  View


Add Issue(s)

Attach Custom Form    
Edit Custom Fields  
Approve Issue
Add  An Approval Process    
Add Documents
Copy Issue*
Move Issue    
Log Hours  
Convert to Project*    
Convert to Task*    
Accept Assignment  
Updates/ comments
Modify Planned Dates    
Make Assignments  
Share System-wide    

*A user needs to have project or task access to perform these actions, and they must have the correct access level. Some access levels prohibit these actions. 

Linked elsewhere, don't remove/ rename/ change link.