# Epic OP-5635 - Speed up on working on new projects and reduce project related work for OpenProject Administrators

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

## Detailed specification

### Motivation and background information

### Acceptance criteria

### Out of scope

| Attribute | Value |
| --- | --- |
| Mockups |  |

## Planning

| Attribute | Value |
| --- | --- |
| Roadmap |  |
| Date |  |
| Votes |  |
| List |  |
| Target versions | Wish List |
| Sprint |  |
| Backlog bucket |  |
| Relevance |  |

## Subitems

_No work packages_

## Bugs and other work packages

_No work packages_

## Details

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

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Feature Lead |  |
| Designer |  |
| Developers |  |
| Requested by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| Work |  |

## Description

As an OpenProject Administrator   

I need the users to work as independently from me as possible.  

so that there is no unnecessary delay when users starts working on new projects.



To cover this goal I opened an Epic because several aspects are involved.



### Missing permissions (for role project admin):



*   Archive project (by the particular project admin)

*   Unarchive project (by the particular project admin, if still existing)

*   Create group (which is &quot;dedicated/fixed assigned&quot; to the project, see below feature request &quot;&quot;1. Project based group management&quot;)

*   Assign members to a group (See below feature request &quot;&quot;1. Project based group management&quot;)



### Feature Requests



1\. Project based group management



Present:  

Currently the project admin creates a project and aks the system admin to create a group and add members to it, and only then the project admin can grant project based permissions to that group. Same procedure when the members change.  

That takes too much time, is complicated and delays the work with projects too much.



New features:



*   Create group automatically when create a project.

*   Permission: Assign/delete members to/of that group for the project admins (aside from the system admins)



Reason:  

To avoid to involve the system admin when it comes to grant permissions to groups the project admin should be able to create and edit a group.  

A group can be created automatically when a project is created. As default the group name is the same as the project name. This group is &quot;dedicated/fixed assigned&quot; to the project but could be deleted to keep the total number of groups as small as possible.  

The project admin should be able to assign members (from all users) or groups to that group and grant permission to that (and other groups) based on the roles.



Thoughts:  

\-Groups should be available in all projects



### BUGs



Permission &quot;Create subprojects&quot; needs permission &quot;Edit project&quot;.  

https://community.openproject.com/projects/openproject/work\_packages/29773/activity



Length of group names is limited to 30 characters  

https://community.openproject.com/work\_packages/29770/activity



Group names should have a description field  

https://community.openproject.com/work\_packages/29766/activity



Excel import does not work  

https://community.openproject.com/projects/openproject/work\_packages/29776/activity
