mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-05-04 18:08:46 +03:00
Deny View Access to certain pages or chapters? #1731
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 @mikeyz24 on GitHub (May 13, 2020).
Is it possible to deny a user view access to certain chapters or pages while being able to view other chapters or pages within a book? With my testing, it seems like I can only allow users to view all or view none.
I'm trying to mimic the behavior of ABE (Access-based Enumeration) in NTFS when it comes to who can view what within a book.
Does anyone have some tips or workarounds on getting this type of behavior work?
@ssddanbrown commented on GitHub (May 14, 2020):
Hi @mikeyz24,
BookStack has role-based-access that can be applied per shelf/book/chapter/page. Permissions set upon books & chapters will cascade to child items, unless they have their own permissions set.
To configure this you can just view any of those items and you should see "Permissions" under actions. You'll then get a view like this:
@mikeyz24 commented on GitHub (May 14, 2020):
How do I deny access to users to certain chapters or pages while allowing them to view other chapters/pages within a book/chapter? There is no check box to mark as "deny".
@ssddanbrown commented on GitHub (May 15, 2020):
@mikeyz24 Unchecked is essentially "deny". If you only checked the top "Enable Custom Permissions" checkbox and no others, then only users of the original built-in admin role would be able to view/create-within/update or delete that item.
@mikeyz24 commented on GitHub (May 15, 2020):
@ssddanbrown Thanks for the explanation, I understand how this works now.