# Idea OP-9497 - A cross-project, transversal Team Planner

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

## RICE

| Attribute | Value |
| --- | --- |
| Reach |  |
| RICE Score |  |
| Votes |  |

## Requires

_No work packages_

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |

## Details

| Attribute | Value |
| --- | --- |
| Roadmap |  |
| Date |  |
| Target versions | Wish List |
| Module |  |
| Priority | Medium |
| List |  |
| Interest by |  |
| Labels |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| PD (min) |  |
| PD (max) |  |

## Description

This work package seeks to explore and gather thoughts on extending the Team planner from a project-based module to something that is transversal and cross-project.

**Permissions**

*   How would moving this module to a higher-level (similar to News and Time and Costs) affect which permissions are available for it? Would it be treated differently, as a module?
*   Would you still need these three?
    *   &quot;View team planner&quot;
    *   &quot;Manage team planner&quot; and
    *   Make it public/private (phrasing to be confirmed)

**Accessing the module**

*   The &quot;module&quot; would then also &quot;live&quot; at a higher level, for example on the top-level menu next to the notification bell:

<figure class="image op-uc-figure" style="width:50%;"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/23701/content"></div></figure>

**Group-based logic**

Assignees would have be governed by groups

*   Does this mean that a planner is &quot;owned&quot; by a group? Or that a group is &quot;assigned&quot; to it?
*   Are groups a starting point (as part of the initialisation process for example) that merely populate the team planner with a certain set of assignees and permissions, which can then be modified; or are they simply the basis of a team planner, and to change the assignees, you need to change the members of the group?
*   Would there be different roles to members of the group? (Admin vs. viewer)
*   How would project-level permissions interact with group-level permissions, in terms of being able to view or edit certain workpackages?
*   If we have different roles for members of a group, would any of these rules be unique to the team planner?
*   How would filters work in a cross-project context? Logically they would work the same way as today, except, for the &quot;Project&quot; filter, you could pick any project- or sub-project in that instance. (Does this mean that having the permission to create a planning calendar almost implies having the permissions to be able to view all projects in that instance?)

**Assignees**

Normally, the assignees that are displayed would correspond to the members of the group:

*   Should it be possible to &quot;hide&quot; certain assignees?
*   Or to &quot;invoke&quot; certain others outside of the group? (To be able to compare or to get context?)

**Sharing**

*   Should it be possible to share the team planner outside of the group? 
    *   As a read-only, perhaps?
    *   With a public link, even?
