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 Begin of the insertioncross-project.End of the insertion Begin of the deletion cross-project. End of the deletion

**Permissions**

* Begin of the insertionHow would moving thisEnd of the insertion Begin of the deletion Would permissions for theEnd of the deletion module Begin of the deletion need updatingEnd of the deletion to a Begin of the insertionhigher-levelEnd of the insertion Begin of the deletion higher levelEnd of the deletion (similar to News and Time and Begin of the insertionCosts) affect which permissions are available for it? Would it be treated differently, as a module?End of the insertion Begin of the deletion Costs)?End of the deletion
* Would you still need Begin of the insertiontheseEnd of the insertion Begin of the deletion theEnd of the deletion three?
* "View team planner"
* "Manage team planner" and
* Make it public/private (phrasing to be confirmed)

**Accessing the module**

* The "module" would then also "live" 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**

Begin of the deletion * End of the deletion Assignees would have be governed by groups Begin of the insertion

End of the insertion Begin of the deletion
End of the deletion * Does this mean that a planner is &quot;owned&quot; by a group? Or that a group is &quot;assigned&quot; to it? Begin of the insertion
End of the insertion Begin of the deletion
End of the deletion * 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? Begin of the insertion
* 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?End of the insertion