mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-02-05 08:39:55 +03:00
Allow user specific permission assignments at an entity level #1424
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 @Luffyyy on GitHub (Oct 25, 2019).
Describe the feature you'd like
Add a collaborators option for pages and what not so a user who created a page/etc will be able to give permissions to other users to also edit it.
Describe the benefits this feature would bring to BookStack users
This will allow users to have shared pages/etc without needing to create special roles for each group of people.
@ssddanbrown commented on GitHub (Oct 25, 2019):
Hi @Luffyyy,
Thank you for your request.
We already have a role permission to allow users to manage permissions on their own content.
Am I correct in thinking that, to support your request, you'd just need the ability to assign permissions per user instead of per role in the page permissions view?
@Luffyyy commented on GitHub (Oct 26, 2019):
Yes
@ssddanbrown commented on GitHub (Oct 26, 2019):
Thanks for confirming @Luffyyy. I have updated the title to reflect the core feature requirement. "Permission System Review" is on the roadmap, It will likely be at that point which this feature will be considered for inclusion.
@Struki84 commented on GitHub (Oct 26, 2019):
Hi guys,
I came to this thread looking I think for the same thing, if it's ok I'll just describe shortly the feture I'm interested.
As an Admin user I can assign individual users specific permissions per shelf or per individual book.
So if I have 2 users i can select which of the users will have access to which of the books/shelfs
@ssddanbrown commented on GitHub (Oct 26, 2019):
Thanks for the input @Struki84, That use-case aligns with the updated title.
Just as an FYI, in the event that you're new to the project, you could currently achieve this but you'd need to create a custom role for those two users, to then use that role in the book/shelf level permissions pages. You may have already discovered this though.
@Struki84 commented on GitHub (Oct 26, 2019):
Wow, tnx, I wasn't aware you can create custom roles, I think that would work for me.
@cb3inco commented on GitHub (Sep 3, 2021):
I would love to see something like this at the book level too. A 'private' book that people can add and remove users and adjust permissions as needed.
@ramazanpolat commented on GitHub (Feb 12, 2025):
This is exactly what we are looking for.
We'd like to create a book and add view/alter permissions for specific user(s).
Right now, we need to create a role for this and add that person to that role and give permission to that role for the relevant book, which is too complicated. And, we'll have lots of roles to have...
@FaroJoaoFaro commented on GitHub (May 23, 2025):
I would also really enjoy this feature.
Is there any work being developed on this?
Or can I take a look into it?
@ssddanbrown commented on GitHub (May 23, 2025):
@FaroJoaoFaro I made an attempt a few years back in #3908, but that led to a dead end in regard of this feature (although this lead to a refactoring of permissions via #3986). This is something I'd like to implement (hence my prior attempt), but I don't really have the motivation to do any-time soon since the permission system is significant and complex, and there's really some substantial database structures changes to be made first which I wouldn't want to rush.
Thanks for the offer to look at this, but due to the scope & complexity of this area I would not be keen on someone else (that's not deeply involved in the project) jumping in to develop this out.