# Epic AUTOWORK-282 - Affiliation-based (internal/external) and group-based contexts for custom fields

Project: Stream Workflows & Automations
Status: new
URL: https://community.openproject.org/work_packages/AUTOWORK-282

## Detailed specification

### Motivation and background information

Organizations using OpenProject often store sensitive information in custom fields - such as internal cost estimates, legal notes, risk classifications, or vendor details. Currently, there is no native mechanism to mark a custom field as 'internal' and restrict its visibility based on project permissions.

| Attribute | Value |
| --- | --- |
| Mockups |  |

## Planning

| Attribute | Value |
| --- | --- |
| Roadmap | 2027 Q2 |
| Date |  |
| Votes | 5 |
| List | RM Jira exit, RM ITSM |
| Target versions |  |
| Sprint |  |
| Backlog bucket |  |
| Relevance |  |

## Subitems

_No work packages_

## Bugs and other work packages

_No work packages_

## Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Labels |  |

## People

| Attribute | Value |
| --- | --- |
| Assignee | Sonita Soth |
| Accountable |  |
| Product manager | Sonita Soth |
| Feature Lead |  |
| Designer | Parimal Satyal |
| Developers | OP Dev Sirius Team |
| Requested by |  |
| Interest by | Black (37919), Bowling (40324) |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| Work | 90d 0h |

## Description

**As a** user

**I want to** store all relevant information (both internal and external) of an item in one place, however making sure there is various visibility/privileges for the stored information

**So that I** can share the issue with external project members (e.g. clients) being sure that they can access only information which is external.
