# Feature OP-20125 - Improve roles and permission selection for project admin adding a member

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

## 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 |  |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan |  |

## Details

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

## People

| Attribute | Value |
| --- | --- |
| Assignee | Oliver Günther |
| 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** a project admin  
**I want to** improve the role selection and management of members  
**so that** I understand what I am assigning

**Motivation**

*   As a project admin, it is currently impossible to find out what roles I need to grant to give a user specific permissions. I cannot review roles, filter them, and select the ones relevant to me
    
*   This is potentially dangerous when I grant too many permissions
    

**Acceptance criteria**

*   Editing the roles of a member in a project opens a dialog
    
*   The dialog could resmseble somewhat the sharing dialog
    
*   I can see which roles the user/group currently has, which of them are inherited and from where
    
*   I can add new roles through an autocompleter
    
*   When selecting new roles, I can _somehow_ find out what this roles entail
    
*   Possibly, I can also search for permissions rather than roles
    

<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/924464/content">

<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/924459/content">

**Technical notes**

*   <br>
    

**Permissions and visibility considerations**

*   _To whom is this feature visible?_
    
*   _When is it not visible?_
    

**Translation considerations**

*   _Key terms and phrases in the key languages_&nbsp;
    

**Out of scope**

*   <br>
    

_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._
