# Bug OP-8457 - Custom fields on global work package list can be added as column even when user has no access to it

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

## Open points

_No work packages_

## Details

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Low |
| Module |  |
| Target versions | 15.5.0 |
| Observed in versions | 11.2.0 |
| Sprint | 15.5.0 |
| Backlog bucket |  |
| Bug found in version (deprecated) | 11.2.x |
| Found in mobile app version |  |
| Follow-up feedback e-mail |  |
| Requires doc change | No |
| Accessibility | No |
| Pull preview |  |
| List |  |
| Labels |  |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable | Tobias Dillmann |
| Product manager |  |
| Developers | OP Dev Polaris Team |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Planning

| Attribute | Value |
| --- | --- |
| Relevance |  |

## Costs

| Attribute | Value |
| --- | --- |
| Votes |  |
| Work |  |
| Labor costs |  |

## Description

### **Environment**:

OpenProject 11.2

### **Steps to reproduce:**

1.  Create a work package custom field that is not activated for all projects.
2.  Activate this custom field in only some projects
3.  As a user who doesn't have access to the projects in which those custom fields are activated, navigate to the global work package list
4.  Open the column menu and select the custom field.

### **Actual Behavior**

The custom field can be selected as a column - even though the user is not allowed to see it (CF name could contain sensitive information).

### **Expected Behavior**

User cannot select custom fields for projects he/she doesn't have access to.
