Issue Permissions

Issue permissions affect how certain members can interact with issues on a project.

Project administrators can manage issue permission levels at the user, role, and company level.

Issues Permission Levels

Use the drop-down to select the desired permission set for the selected members, roles, or companies.

Here is a quick summary of how the four permission levels can be used:

The following is a detailed outline of each permission level and what specific actions can or can't be performed:

Permission View All Create View and CreateFull Control
View issues Yes Members can only view issues that they created, issues created by their company, or issues assigned to their company or role. Yes Yes
Create issues No Yes Yes Yes
Edit isues As an issue owner or creator, members can edit any of the issue's fields such as title, description, due date, location, or root cause, as well as add responses, comments and attachments. As an issue owner or creator, members can edit any of the issue's fields such as title, description, due date, location, or root cause, as well as add responses, comments and attachments. As an issue owner or creator, members can edit any of the issue's fields such as title, description, due date, location, or root cause, as well as add responses, comments and attachments.Yes
As an assignee, members can only add a response or comment, upload attachments and photos, as well as delete their own attachments. As an assignee, members can only add a response or comment, upload attachments and photos, as well as delete their own attachments. As an assignee, members can only add a response or comment, upload attachments and photos, as well as delete their own attachments.
Reassign isues As an assignee, members can only assign the issue back to the owner, creator, or someone from their own company. As an assignee, members can only assign the issue back to the owner, creator, or someone from their own company. As an assignee, members can only assign the issue back to the owner, creator, or someone from their own company. Yes
Change issue status Members can change issue status except Closed or Draft to Open. Members can change issue status except Closed or Draft to Open. Members can change issue status except Closed or Draft to Open. Yes
Close or void issues Members can close or void issues they created and own, and the issues they own even if they didn't create them. Members can close or void issues they created and own, and the issues they own even if they didn't create them. Members can close or void issues they created and own, and the issues they own even if they didn't create them. Yes
Important: Issues can't be deleted or edited once the status has been set to VOID or CLOSED.

Members who have Full Control (including project administrators) are the only users that can close or void all issues.

Default Permissions by Role

If a member has a role assigned to them and has individual permissions assigned for issues, the higher permission is the active permission set. The following roles default to Create permissions:

The following roles default to Full Control:

Modify Permissions

  1. Click the Project Admin module.

  2. Click the Services tab.

  3. Select Issues in the panel on the left.

  4. Use the search box to select the users, roles, or companies you want to modify permissions for.

    Tip: You can select multiple users, roles, and companies, and then specify the same permission level for them all in bulk.
  5. Use the drop-down menu to modify the permission level for the selected users, roles, and companies.

  6. Click Add.

Note: Permissions can't be changed for other administrators.