# Feature OP-14838 - Multitenancy in OpenProject

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

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | Wish List |
| Sprint |  |
| Backlog bucket |  |
| Votes | 7 |
| 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

I am not sure if this is of any interest for OpenProject but I believe it would greatly enhance its use-case: Multitenancy.

OpenProject as it is now is not really intended to be used by different groups of people. Features like Groups, Roles, work package types, status or workflow can only be managed by instance administrators. Thus, already two independent groups working on one instance would need to have each at least one instance administrator, greatly enhancing the risk of making serious errors in the admin interface resp. the instance. It becomes pretty evident just by clicking through the admin-interface what might be handled on a project/group-level:

  - Users and permissions -\> Groups (creation + deletion), Roles and permissions (obviously, separating global and "local" - i.e. group/project - roles/permissions), the permissions report (as read-only, e.g. on a instance's "help-page")
  - Work packages -\> Types (creation + deletion), Status (differentiate global / "local" statuses), workflow (obviously, on a project/group level), Custom actions.
  - Custom fields
  - Attribute help texts
  - Enumerations
  - Time and costs -\> Settings, Cost types
  - Backlogs
  - File storages (connect your own - E.g. one team might use their own NextCloud, the other their own SharePoint)

This would make OpenProject easier to administer on a large instance with independent groups while giving them much more possibilities of customizing their projects and ultimately make hosting of OpenProject more cost-effective.
