(8.6.1) Permissions approach
- Federico Baronti Beltramo
Permissions are a very important part of Project tracking. Here you will find the Permissions table where you will be able to see what kind of permission Projectrak can provide in your instance, the level where they apply, and where to set them.
Permission | Level | Where to set |
Projectrak administrationProjectrak administrators can create fields and layouts, and associate projects with layouts. | GLOBAL | Jira administration |
Project bulk operationsModify or delete several projects, roles, project leads, layouts, categories, components, and project fields at the same time. | GLOBAL | Jira administration |
View project fields valuesAbility to view the values of the project fields. It can be limited if fields have restricted visibility. | PROJECT | Two paths: Project (for a specific project)
Jira administration (all projects)
|
Edit project fields valuesAbility to view the values of the project fields. | PROJECT | |
Associated layoutsAbility to associate existing layouts to projects | PROJECT | |
Watch projectsAbility to receive email notifications when project values change. Except for script and cumulative fields. | PROJECT | |
Restrict field visibilityProjectrak administrators can restrict the visibility of any Projectrak fields by choosing the project role that will be able to view this field. | FIELD | Projectrak
|
Default permissions
At the installation of Projectrak your permissions are set up like this:
Permission | Jira administrator | Projectrak administrator | Project administrator | Project user | Jira bulk user |
Projectrak administration |
|
| |||
Project bulk operations |
| ||||
View project fields values |
|
|
| ||
Edit project fields values |
|
| |||
Associate layouts |
|
|
| ||
Watch projects |
|
| |||
Field visibility |
|
|
|
|
|
