# Feature OP-20041 - Tag roles as "inherited" wherever they come from a parent group, instead of listing everything flat

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

## 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 |
| 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** a user  
**I want to** see, next to each role, whether it comes from a parent group or was assigned directly  
**so that** group and member role lists stay understandable once group hierarchies have more than one level

**Why**

Project access is inherited down the group hierarchy (parent group → child group). A child group&#x27;s role list shows everything flattened, with no way to tell what&#x27;s inherited vs. directly assigned — confusing as soon as the structure gets more complex.

**Current behaviour**

A group&#x27;s _Projects_ tab, and a project&#x27;s _Members_ list, show every project/role row the same way, whether it was assigned directly on that group/member or inherited from a parent group. No visual distinction exists (confirmed against OpenProject&#x27;s own docs — group hierarchy and inheritance are documented, a UI marker for it is not).

**Proposed behaviour**

Add a tag next to each role that comes from a parent group, e.g. **&quot;Inherited from &lt;Parent group&gt;&quot;**, in both places:

*   Admin → Groups → edit group → _Projects_ tab
    
*   Project → _Members_ list
    

Directly assigned roles stay unmarked (or get a neutral &quot;Direct&quot; tag for symmetry).

**Acceptance criteria**

*   Each role in a group&#x27;s _Projects_ tab and in a project&#x27;s _Members_ list is marked as inherited (naming the source group) or left as direct.
    
*   Works across multiple hierarchy levels (grandparent → parent → child) — the tag names the actual originating group, not just &quot;inherited&quot;.
    
*   A role held both directly and via inheritance is shown as direct, not hidden behind the inherited tag.
    
*   Purely additive: no change to sorting, filtering, or existing columns.
    

**Technical notes**

*   OpenProject already distinguishes inherited memberships internally (used e.g. to exclude them from the dashboard members widget) — this exposes that existing distinction in the UI rather than introducing a new concept.
    

**Permissions and visibility considerations**

*   _To whom is this feature visible? Visible to whoever can already see the group&#x27;s Projects tab / the project&#x27;s Members list today._
    
*   _When is it not visible?_
    

**Out of scope**

*   Changing how inheritance itself works (what&#x27;s inherited, override rules) — this request is about visibility only.
