Content
View differences
Updated by Jens Ulferts about 2 years ago
**As an** Project admin
**I want to** provide permissions team members to view and edit project attributes
**So that I** can better control who gets the information.
**Acceptance criteria**
* There are two new permissions on project level:
* (1) View project attributes
* Migration: This new permission is added to all roles that have the permission "View project"
* Users without the permission see the project overview span the entire width, without the right pane
* (2) Edit project attributes
* Migration: This new permission is added to all roles that have the permission "Edit project"
* The view/edit permissions are adhered to on the API level
* Users lacking the view permission will not have the property listed
* Users lacking the edit permission will see the property but it is not writable
**Out of scope**
* Permission on individual project attributes <mention class="mention" data-id="50179" data-type="work_package" data-text="#50179">#50179</mention>
* Global permissions
**I want to** provide permissions team members to view and edit project attributes
**So that I** can better control who gets the information.
**Acceptance criteria**
* There are two new permissions on project level:
* (1) View project attributes
* Migration: This new permission is added to all roles that have the permission "View project"
* Users without the permission see the project overview span the entire width, without the right pane
* (2) Edit project attributes
* Migration: This new permission is added to all roles that have the permission "Edit project"
* The view/edit permissions are adhered to on the API level
* Users lacking the view permission will not have the property listed
* Users lacking the edit permission will see the property but it is not writable
**Out of scope**
* Permission on individual project attributes <mention class="mention" data-id="50179" data-type="work_package" data-text="#50179">#50179</mention>
* Global permissions