mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-02-12 03:09:38 +03:00
Allow granular item-level permission control #3443
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 @at-ng on GitHub (Jan 12, 2023).
Describe the feature you'd like
For now you can set either of these two:
Manage all book, chapter & page permissions
Manage permissions on own book, chapter & pages
But I think there is room for something in between here. For example "Manage permissions on book, chapter & pages you allowed to update".
Another way this could be solved would be to change how ownership works so that you can have multiple owners, a group, or a role could be an owner instead. Then the "Manage permissions on own book, chapter & pages" option could be enough.
Describe the benefits this would bring to existing BookStack users
I think this would be good for all users that has multiple people responsible for a book. Since then you can't use Owner as the restriction and have to resort to allowing people to edit all permissions.
Can the goal of this request already be achieved via other means?
No, I think you are either limited to only letting the owner edit permissions or allowing users to edit all permissions.
Have you searched for an existing open/closed issue?
How long have you been using BookStack?
0 to 6 months
Additional context
Probably not a super important feature as it's only a problem when more than one person is responsible for a book (and permissions is not something you change very often) but I figured it was worth having an issue for it.
@adamzvolanek commented on GitHub (May 4, 2023):
I concur, it would be nice to set permission on a per {book, chapter & pages} level based on role.
My example use-case is you can have a public facing BookStack instance with certain pages restricted from view, however authenticated user's can view the same pages with the content present.
@at-ng commented on GitHub (May 4, 2023):
This issue is not about setting permissions but who is allowed to set permissions on an item. E.g. I want people who are allowed to update a book to be able to set it's permissions but not update permissions of books they are not allowed to update.
Books, chapter and pages already have the option of settings permissions per role.
@matthias4217 commented on GitHub (May 26, 2023):
Being able to set the owner as being a role or group of people would be great. We have several books which should be owned by several people.
@Coros commented on GitHub (Jun 21, 2023):
Adding another request here. We have several books that should own/managed by their respective role/groups. Currently only one member of each book can manage the permissions on the book itself. The ability to set their role(s) as the owner, or add a new grantable right to manage permissions on an object, would solve this problem.