# Brainstorm Team and Projects control backoffice

**URL:** <https://community.penpot.app/t/brainstorm-team-and-projects-control-backoffice/7562>\
**Category:** Help us improve Penpot\
**Tags:** team, projects, brainstorm\
**Created:** [January 15, 2025, 8:28pm UTC](https://community.penpot.app/t/brainstorm-team-and-projects-control-backoffice/7562 "2025-01-15T20:28:40Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![BDV](https://dub1.discourse-cdn.com/flex017/user_avatar/community.penpot.app/bdv/32/8012_2.png) [@BDV](https://community.penpot.app/u/BDV)\
**Post date:** [January 15, 2025, 8:28pm UTC](https://community.penpot.app/t/brainstorm-team-and-projects-control-backoffice/7562/1 "2025-01-15T20:28:40Z")

</div>

On the topic below, you can see which projects are normally scheduled.

> [@Not a roadmap! Recent, current, and 2025 initiatives](https://community.penpot.app/t/not-a-roadmap-recent-current-and-2025-initiatives/7375):
>
> What’s Penpot working on and what’s coming next? A roadmap lays out a series of steps to reach a goal, each becoming a commitment. However, when innovating, commitments can be tricky. You’re exploring uncharted territory, filled with uncertainty. Context can shift in a heartbeat, and we learn as we go, which also means that our ideas evolve. Trying to stick to commitments in this environment is an unnecessary recipe for frustration. So, instead of calling this a roadmap, thi…

 ![Penpot roadmap 24-25](https://europe1.discourse-cdn.com/flex017/uploads/penpot/original/2X/8/855206de54150c7550056e7c68999fd61c46deaa.png)  
_Keep in mind that these are just ideas, not commitments. This vision is sure to evolve over time._

**For Team and Projects control back office, I thought it might be useful to create a topic to brainstorm which features would be useful to use.**

Personally, I myself would like to see the following 3 things implemented in within Penpot that are related to team and project control:

- Creating subgroups within a Penpot project in analogy with GitLab  

- Implement Kanban  

- [Use Git/GitHub principal for teams](https://github.com/penpot/penpot/issues/5361)

---

<div class="post-metadata">

**Author:** ![myfunnyandy](https://dub1.discourse-cdn.com/flex017/user_avatar/community.penpot.app/myfunnyandy/32/54_2.png) [@myfunnyandy](https://community.penpot.app/u/myfunnyandy)\
**Post date:** [January 16, 2025, 11:31am UTC](https://community.penpot.app/t/brainstorm-team-and-projects-control-backoffice/7562/2 "2025-01-16T11:31:53Z")

</div>

To be clear about what we mean by “team & project control backoffice”, we are not referring to new capabilities for project management (planning and organizing tasks). We’re talking about an administrative interface where administrators can manage and control who-can-do-what inside a Penpot organization (permissions over users and actions).

However, I think that this is a very interesting proposal, valid by itself and aligned with some of our previous ideas of integrations with project management services (being [Taiga](https://taiga.io/) our obvious preference).

---

<div class="post-metadata">

**Author:** ![tudorcelstan](https://dub1.discourse-cdn.com/flex017/user_avatar/community.penpot.app/tudorcelstan/32/6815_2.png) [@tudorcelstan](https://community.penpot.app/u/tudorcelstan)\
**Post date:** [January 16, 2025, 9:53pm UTC](https://community.penpot.app/t/brainstorm-team-and-projects-control-backoffice/7562/3 "2025-01-16T21:53:16Z")

</div>

This would obviously not be a priority, but it’s a cool idea and worthy if not hard to implement. A kanban view for Penpot projects. No consequence to the content of the project, no automations, just a way for teams to communicate and assign status of design files.