# Feature OP-13637 - New permissions for project attributes on project level

Project: OpenProject
Status: closed
URL: https://community.openproject.org/work_packages/OP-13637

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | 14.4.0 |
| Sprint | 14.4.0 |
| Backlog bucket |  |
| Votes |  |
| List | cProject |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Features and Chunks

_No work packages_

## Bugs and other work packages

_No work packages_

## Technical Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Feature Flag |  |
| Requires doc change | Yes |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable | Attila Dombi |
| Product manager |  |
| Feature Lead |  |
| Developers |  |
| Designer | Parimal Satyal |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| PD (min) |  |
| PD (max) |  |
| Work |  |
| Labor costs |  |

## Description

**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
            
              - The specification used to say "to all roles that have the permission "View project"". "View project" is an internal permission that every role has so the requirement is equivalent.
        
          - Seeding: Add to all roles
    
      - (2) Edit project attributes
        
          - Migration: This new permission is added to all roles that have the permission "Edit project".
        
          - Seeding: Add to all roles that currently have the "Edit project" permission.

  - The permission to "Edit project" is no longer granting view/write access to project attributes
    
      - The permissions are completely independent so a user can have "Edit project" but lack "View project attributes" and "Edit project attributes"

  - Users not having the view permission in a project cannot:
    
      - Find the project in which they lack the permission by applying a filter for the project attribute even if they have the permission to see the project attribute in another project.
    
      - See the project attributes in the overview page
        
          - The project overview spans the entire width, without the right pane
    
      - See the project attributes in the project settings
    
      - See the project attributes in the project list
        
          - Search for project attributes in the project list page, meaning projects where the user doesn't have a view\_project\_attributes will not be returned when searching attribute values.
    
      - See the project attributes in the project list export
    
      - See the project attributes in the API
    
      - See the project attributes in the Schema API

  - Users not having the edit permission (but the view permission) in a project cannot:
    
      - Write the project attributes in the overview
    
      - Write the project attributes in the project settings
    
      - Write the project attributes in the API
    
      - Write the project attributes in the Schema API (receive them as readonly)

**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
