mirror of
https://github.com/plankanban/planka.git
synced 2026-07-16 05:53:57 +03:00
Intermediate role between "Board user" and "Project Owner" #750
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @valcriss on GitHub (Jul 5, 2025).
Is this a feature for the backend or frontend?
Frontend, Backend
What would you like?
I believe it would be useful to introduce an intermediate role between "Board user" and "Project Owner". Currently, a Board user can only participate in projects they've been invited to, while a Project Owner can create both private and team projects.
In many cases, users would benefit from having their own private project to manage daily tasks, a kind of personal todo list. However, granting them full Project Owner rights might be too permissive, especially if they shouldn't be allowed to create team projects.
That's why I think adding a new role that allows users to create private projects but not team projects would offer a better balance in terms of permissions and usability.
A more advanced approach could be to allow administrators to define custom roles, including permissions for which types of projects users can create, and even set a maximum number of private projects per user.
Why is this needed?
Many users want to use Planka not only for collaborative team projects, but also for personal task management. However, the current roles don’t allow this flexibility, users must be granted full "Project Owner" rights just to create a simple private board. This can be too permissive in some organizations, as it also gives the ability to create team projects.
Introducing a new intermediate role (or customizable role permissions) would allow better control over who can create what, enabling personal productivity without compromising team governance or access control.
Other information
I’d be happy to work on this feature if you think it would be a valuable addition to the project.
@valcriss commented on GitHub (Jul 6, 2025):
Another possible solution would be to add an option in a global settings page (which doesn’t exist yet) to allow Board users to create private projects.
This could be implemented as a simple checkbox like “Allow Board users to create private projects”, or alternatively, through an environment variable.
@meltyshev commented on GitHub (Jul 7, 2025):
Hi! We've discussed something similar here: https://github.com/plankanban/planka/issues/1111#issuecomment-2890852551.
Adding a "Can create [private] projects" switch in user settings could potentially solve the issue. However, we need to test how it would work, since Board Users don't have access to all users - meaning they wouldn't be able to add members to their private boards. We'd also need to remove the ability to convert a Private project to Shared.