Brief summary of this article:
Permissions for users to view, add, edit, and delete entities in Targetprocess are managed on a per-role basis and defined by membership lists.
Each user has a default (system) role, plus a specific role for each particular project or team they are a member of. Roles for a user may vary between projects and teams. The list of Roles and settings of permissions in the system is global.
How to configure Roles
List of Roles
Navigate Settings → Roles menu item to see list of all Roles added to the system.
Only Administrators are authorized to modify permissions of Roles, create new Roles, and delete Roles from the system.
Settings and permissions for any role can be modified within Edit links. The Add link creates a new Role and Del link removes a Role from the system completely.
These settings affect all users, projects, and processes in your Targetprocess system. Be extremely careful when making modifications to existing Roles. Deactivation of the Has Effort setting for a Role and deletion of a Role may cause massive loss of data.
Settings and Permissions of a Role
This screen is displayed when you Add a new Role or Edit an existing Role. Make your selection and press Save button to apply it to the Role.
Here you can view and change the permissions for the add, edit and delete actions for specific entities.
There is no way to restrict view permissions by Role. For example, when Jonny D. has access to project DM then with any role permissions he is able to view all entities in this Project, including User Stories, Bugs, comments, attachments, time records, custom fields.
Besides roles, permissions for users to view, add, edit, and delete entities in Targetprocess are granted according to multiple different settings. More information: Permissions for work items.
There are a few more permissions related to specific actions:
- Allow access to Time sheet
- Allow access to People area (checkbox is outdated and has no impact on Role configuration. We have plans to completely remove it in the future)
- Has Effort
- Can change creator
- Can prioritize
A role can be renamed using this settings page as well.
Add Role to Assignments
When you add a Role to the system it does not appear as an available option in the Assignments section of work items automatically. Instead, you have to modify process settings for each entity type and process where you want to add the Role. Use the guide below:
Introduce modified Role for a specific subset of users
If you need to change permissions for a specific subset of users, we recommend doing it step-by-step:
- Create a new Role with the permissions specific to this group
- Edit personal settings for each user. Modify Default role and Project / Team membership role if needed
More information: How to select a Role for a User in a Project or Team.
Default Role for New Users
All Targetprocess users always have a Default Role selected. By default, if none is explicitly selected, the first Role from the list of available ones is set as Default Role for all newly created users.
Roles and custom Terms
Your current projects and teams selection influence the terms displayed. Should you have a project with customized names specified, you will see these new names on the screen instead of the defaults.
In the screenshot below Bugs are renamed to Defects.
See also
Still have a question?
We're here to help! Just contact our friendly support team.