As an Adobe Workfront administrator, you can use an access level to define a user’s access to issues, as explained in Access levels overview.
For information about using custom access levels to manage users’ access to other object types in Workfront, see Create or modify custom access levels.
You must have the following access to perform the steps in this article:
Adobe Workfront plan | Any |
Adobe Workfront license | Plan |
Access level configurations | You must be a Workfront administrator. NOTE: If you still don't have access, ask your Workfront administrator if they set additional restrictions in your access level. For information on how a Workfront administrator can modify your access level, see Create or modify custom access levels. |
Begin creating or editing the access level, as explained in Create or modify custom access levels.
Click the gear icon on the View or Edit button to the right of Issues, then select the abilities you want to grant under Fine-tune your settings.
(Optional) To restrict inherited permissions for issues from higher ranking objects, click Set additional restrictions, then select Never inherit document access from projects, tasks, issues, etc.
(Optional) To configure access settings for other objects and areas in the access level you are working on, continue with one of the articles listed in Configure access to Adobe Workfront, such as Grant access to tasks and Grant access to financial data.
When you are finished, click Save.
After the access level is created, you can assign it to a user. For more information, see Edit a user’s profile.
For information about what users in each access level can do with issues, see the section Issues in the article Functionality available for each object type.
As the owner or creator of an issue, you can share with other users by granting them permissions to it, as explained in Share an issue.
When you share any object with another user, the recipient’s rights on it are determined by a combination of two things:
Also, if allowed by their access level, users can gain access to an issue through object hierarchy: if a user already has permission on an issue’s parent project or task, they also have permission on the issue (see Step 3 above). When you are sharing an issue, you can see a list of the users who have inherited permission to it.