# Feature AUTOWORK-304 - Add permission to allow project administrators to contextualize custom fields

Project: Stream Workflows & Automations
Status: review approved
URL: https://community.openproject.org/work_packages/AUTOWORK-304

## Planning

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

## OPEN POINTS / FEEDBACK

_No work packages_

## Use cases

_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 | No |
| Enterprise plan | Enterprise / Premium (PRE) |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |
| Build Number |  |
| Found in mobile app version |  |
| Follow-up feedback e-mail |  |
| Accessibility | No |

## People

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

## Estimates and progress

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

## Description

**As** a project admin  
**I want to** manage the project-specific values of work package custom fields in my project  
**so that** my team can use values tailored to the project without asking a global administrator

**Acceptance criteria**

*   A new project permission &quot;Manage work package custom field values&quot; (`manage_work_package_custom_field_values`) exists.
    
*   On upgrade, every role that currently has &quot;Manage type variants&quot; (`manage_project_variants`) is granted the new permission.
    
*   On new installations, the project admin role has the permission.
    
*   Once the UI exists, users with this permission can, for custom fields used in the project:
    
    *   enable and disable global values (if the custom field restricts values per project and it is allowed for project admins)
        
    *   add, edit and delete the project&#x27;s own values (if the custom field allows projects to add values)
        
*   Once the UI exists, users without the permission cannot see or reach the management page.
    

**Technical notes**

*   Permission defined in `config/initializers/permissions.rb`, `permissible_on: :project`, `require: :member`.
    
*   Migration uses `Migration::MigrationUtils::PermissionAdder.add(:manage_types, :manage_work_package_custom_field_values)`.
    
*   The project settings UI reuses the components and services of the global administration (values list, add/edit/delete dialogs, &quot;make available to all projects&quot; stays admin-only).
    

**Permissions and visibility considerations**

*   _To whom is this feature visible?_ Project members with the new permission, and administrators.
    
*   _When is it not visible?_ When the custom field neither restricts values per project nor allows projects to add values, or when it is not used in any form of the project.
    

**Translation considerations**

*   &quot;Manage work package custom field values&quot; — permission label.
    
*   Keep &quot;project-specific value&quot; consistent with the existing admin UI terminology.
    

**Out of scope**

*   The project settings UI itself (separate ticket).
    
*   Making project values available to all projects from within a project.
    
*   Changing the parent of a hierarchy value.
