# Feature OP-5087 - Option to Create Sub Groups of Parent Group

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

## 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 |  |
| 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

In our testing of OpenProject, we found it to be an issue when tagging responsibility at the group level.  We also found permission settings of groups and what projects they belong to a pain to manage with a larger organization.

Ultimately, on the permission front, I should be able to have a group assigned to a project and a sub-group of that parent which has a modified set of permissions such that a department can be added to a project, but only a subset have the ability to conduct certain actions.  This should be able to be accomplished without setting independent groups for everything.  A sub group system would allow for much more maintainability as the operator.

The same but less important issue exists when setting responsible parties for a task or feature.
