# Feature OP-19495 - Roles and permissions: Make projects public

Project: OpenProject
Status: new
URL: https://community.openproject.org/work_packages/OP-19495

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | Wish List |
| Sprint |  |
| Backlog bucket |  |
| Votes | 1 |
| List |  |
| 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 | Administration / Roles and permissions / Project roles and permissions |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan |  |

## Details

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

## People

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

## Estimates and progress

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

## Description

**As** an instance administrator  
**I want to** be able to configure user / project admin roles such that I may enable / disable whether a user may make projects public  
**so that** we have control over the list of projects shown to users.

**Acceptance criteria**

  - Add an additional field like "Make projects public" that enables/disables the permission

**Technical notes**

  - Unfortunately, it is still not possible to configure the default view such that public projects don't clutter the project list (in default view - surely you may apply filters to prevent that). This is a recurring problem and it is a disturbance to our users. Thus, we want to disallow users to make projects public unless manually allowed.

**Permissions and visibility considerations**

  - *To whom is this feature visible? -\> Instance administrators*

**Translation considerations**

  - *Key terms and phrases in the key languages* 

<br>

*Set the* **To be informed/consulted teams** *field to include all teams necessary to be informed of the changes.*
