# Epic AUTOWORK-215 - Confidential workspaces (Address needs of use cases based on security schemas)

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

## Detailed specification

### Motivation and background information

Today, OpenProject controls visibility per project: project members see all work packages they have permission to view. Many teams have public and confidential work in the same project, e.g. HR topics, security vulnerabilities or customer-confidential issues. These should only be visible to a defined group of people.

Today there is no way to:

*   hide some work packages from some project members while the rest of the project stays visible to them
    
*   apply the same confidentiality rules consistently to many work packages
    

Teams moving from Jira use issue security levels for this. Without an equivalent, confidential work can’t be migrated.

Confidential workspaces build on projects, which are already secure and fast. This also means members can get different rights (view, comment, edit), and a confidential workspace can hold more than work packages, e.g. boards, documents or meetings.

* * *

**Jira features covered by this epic (issue security levels)**

<figure class="table op-uc-figure_align-center op-uc-figure"><table class="op-uc-table"><thead class="op-uc-table--head"><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head" scope="col"><p class="op-uc-p">Jira feature</p></th><th class="op-uc-table--cell op-uc-table--cell_head" scope="col"><p class="op-uc-p">What it does in Jira</p></th><th class="op-uc-table--cell op-uc-table--cell_head" scope="col"><p class="op-uc-p">Use case</p></th></tr></thead><tbody><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">Issue security scheme with security levels</p></td><td class="op-uc-table--cell"><p class="op-uc-p">Named levels that control who can see an issue within a project</p></td><td class="op-uc-table--cell"><p class="op-uc-p">UC1</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">Level members: single users, groups</p></td><td class="op-uc-table--cell"><p class="op-uc-p">Only these users and groups can see issues with this level</p></td><td class="op-uc-table--cell"><p class="op-uc-p">UC2</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">Level members: project roles</p></td><td class="op-uc-table--cell"><p class="op-uc-p">Everyone with a certain role in the project can see the issue</p></td><td class="op-uc-table--cell"><p class="op-uc-p">UC2 (add the users or groups directly)</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">Scheme assigned to a project by a Jira admin</p></td><td class="op-uc-table--cell"><p class="op-uc-p">Levels are configured centrally and only available in that project</p></td><td class="op-uc-table--cell"><p class="op-uc-p">UC3</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">No security level</p></td><td class="op-uc-table--cell"><p class="op-uc-p">The issue is visible to everyone with access to the project</p></td><td class="op-uc-table--cell"><p class="op-uc-p">UC3 (No restriction)</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">Sub-tasks inherit the parent’s level</p></td><td class="op-uc-table--cell"><p class="op-uc-p">Sub-tasks always have the same level as their parent</p></td><td class="op-uc-table--cell"><p class="op-uc-p">UC4</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">Set Issue Security permission</p></td><td class="op-uc-table--cell"><p class="op-uc-p">Only certain users can set or change the level of an issue</p></td><td class="op-uc-table--cell"><p class="op-uc-p">UC5</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">Change history</p></td><td class="op-uc-table--cell"><p class="op-uc-p">Changes to the level are shown in the issue history</p></td><td class="op-uc-table--cell"><p class="op-uc-p">UC5</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">Hidden everywhere</p></td><td class="op-uc-table--cell"><p class="op-uc-p">Non-members don’t see the issue in search, filters, boards or notifications</p></td><td class="op-uc-table--cell"><p class="op-uc-p">UC1</p></td></tr></tbody></table></figure>

###   

* * *

**Use Cases:**

<br>

**Use Case 1 Restrict a work package to defined group of people**

Global admins create confidential workspaces with any name and their own members. Work packages in a confidential workspace are only visible to its members, everywhere in OpenProject. Public and confidential work packages can be in the same project.

Example: Project Alpha has the confidential workspace HR and only the group Management and HR is a member. Users outside this group don&#x27;t see HR work packages in lists, boards, Gantt charts or search results. They can not find out the work packages exist, not even through links, relations or mentions.

<br>

**Use Case 2 Decide who belongs to a confidential workspace**

Members are users and groups, each with a role, the same way as project membership. Global admins only have access if they are members.

Example: The workspace HR has the members group HR Team and the CFO. Each of them sees HR work packages, everyone else does not.

<br>

**Use case 3 : Confidential workspaces per project, managed by global admins**

Global admins create confidential workspaces for a project. They are only available in that project. Project admins cannot create or change them. Work packages without a confidential workspace stay visible to all project members (&quot;no restriction&quot;, the default).

Example: The global admin gives project Alpha the confidential workspace HR. All work packages in Alpha stay visible to all project members unless they are put into HR. HR is only available in Alpha.

<br>

**Use Case 4 Child work packages follow their parent**

Children are always in the same confidential workspace as their parent. This cannot be changed on the children.

Example: An HR work package has three children. All three are in HR and only visible to its members.

<br>

**Use Case 5 Choose the confidential workspace when creating, with change log/ history**

Users choose the confidential workspace when they create a work package. Only roles with a dedicated permission can set or change it. Every change is recorded in the work package&#x27;s activity.

Example: A user in project Alpha creates a work package with No restriction. Later a project lead moves it to HR. The activity shows &quot;Confidential workspace changed from No restriction to HR.&quot;

### Acceptance criteria

1.  Users with the right permission can create a confidential workspace within a project
    
2.  Admins can see and manage all confidential workspaces in the instance centrally in the admin setting
    
3.  Only Admins can create confidential workspaces
    
4.  Members of a confidential workspace are users and groups with a role
    
5.  Members of the a parent project don&#x27;t get access to a confidential workspace automatically
    
6.  A confidential workspace can&#x27;t be made public
    
7.  After creation only administrators can change the confidential setting
    
8.  Confidential workspaces are clearly marked wherever they appear
    
9.  Non-members don&#x27;t find a confidential workspace or anything in it anywhere: lists, boards, Gantt charts, search, exports, notifications and API
    
10.  Opening a confidential workspace or one of its work packages directly (URL or ID) without permission shows a not found page as something that doesn’t exist
     
11.  Relations to a confidential work package aren’t shown to non-members and mentions show without a title or link
     
12.  Users can move work packages into or between confidential workspaces they are members of
     
13.  Moving a work package out of a confidential workspace or turning off the confidential setting shows a warning saying who will be able to see the content afterwards. Actions: Confirm (danger), Cancel
     
14.  When creating content in a confidential workspace, a user can see who will have access
     
15.  Every change is recorded in the activity, only visible to people with access
     
16.  Children WPs always have their parent&#x27;s confidential workspace

### Out of scope

*   contextual custom fields
    
*   Project admins creating or changing confidential workspaces
    
*   Giving access dynamically based on author, assignee or a user field (e.g. Approvers)
    
*   Confidential workspaces shared across projects
    
*   Admin audit log for configuration changes
    
*   Overview of who can see a work package (in a separate &quot;Who can see this&quot; dialog)

| Attribute | Value |
| --- | --- |
| Mockups | https://www.figma.com/design/E0clTGRTG0cizp5bYFUbDB/Confidential-workspaces?node-id=56-2159&p=f&t=EZ9opXXfFiWK8Ksw-0 |

## Planning

| Attribute | Value |
| --- | --- |
| Roadmap | 2027 Q1 |
| Date |  |
| Votes |  |
| List | RM Jira exit, RM ITSM, TIB 2026 |
| Target versions |  |
| Sprint |  |
| Backlog bucket |  |
| Relevance | Showstopper — Go-Live Blocker |

## Subitems

_No work packages_

## Bugs and other work packages

_No work packages_

## Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Enterprise plan |  |
| Labels |  |

## People

| Attribute | Value |
| --- | --- |
| Assignee | Sonita Soth |
| Accountable | Rosanna Sibora |
| Product manager | Sonita Soth |
| Feature Lead | Oliver Günther |
| Designer | Parimal Satyal |
| Developers | OP Dev Sirius Team, Oliver Günther |
| Requested by |  |
| Interest by | Black (37919), Home (224196000003952096) |

## Estimates and progress

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

## Description

**Summary**

Global admins **can create confidential workspaces inside a project**. Work packages in a confidential workspace are **only visible to its members**. Everyone else can neither see them nor find out they exist.
