# Feature OP-13293 - Multi-sites implementation

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

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

# User Story

**As** a big company  
**I want** to install and manage a single instance of OpenProject that allows it to be used (and managed) by different departments and teams, each with their needs, workflows and managers.  
**So that** when the need arises, all users from different departments and teams have a single place for collaboration, planning and management, eventually being able to share work or adapting their flow of states, or including users from other departments to their collaboration group without the assistant of the IT Department.

# Description

When considering the use of OpenProject in medium and large companies, certain challenges arise:

  - Each department wants to manage its own workflow, and that includes managing its statuses.
  - Departments and teams do not want to depend on the IT department to adapt the states and flow to their needs.
  - Departments and teams do not want other departments to see the statuses they have defined... or to have the possibility of modifying them by mistake.
  - The IT department does not want additional work managing states and flows for multiple departments.
  - Depending on how each company is organized, sometimes teams or departments want to be able to change permissions on their projects, manage internal groups or the members of each group.
  - Among other similar things...

OpenProject is an increasingly better product and all the work done so far is greatly appreciated. If it could meet some of these needs the level of adoption could be higher, especially in large companies where sometimes individual teams are the ones who adopt OpenProject.

One option could be a new **Multi-sites** feature, or something similar. Each site would include advanced administration options, while other current admin options would be relegated to the IT department because they are more generic or related to infrastructure, database, instance configuration, email gateway, etc. At the user level, users would be global for all sites allowing future collaborations between departments, or temporary permissions on WP as described in this ticket <mention class="mention" data-id="31150" data-type="work_package" data-text="#31150">\#31150</mention> .

Of course this opens new questions about how to organize other details, but I think the concept would be very desirable.

Feel free to change the description or WP type with any of your templates if necessary for your team management.
