Closed mnaoumov closed 7 months ago
I also created a thread on Discord about it: https://discord.com/channels/578552496637739008/1029530651797499945/threads/1195035048152420512
Thanks for the request @mnaoumov. Personally though, I wouldn't be keen on supporting the additional permission system complexity for something like this just for this specific kind of scenario, as I think the general benefits to existing BookStack users are quite limited.
If you're confident with PHP, you could use our logical theme system to build and maintain a customization, to watch for page creation and apply permissions as required.
@ssddanbrown thanks for the quick reply. However, I wonder if my request is so special and unique? I am using BookStack for a few days only, but for me it seems like a basic scenario. Maybe there are better ways to achieve what I am trying to do without you breaking your permission system?
The only other thing I can suggest is categorizing your public/private content into different books to simplify the permission management.
@ssddanbrown no, this is also a workaround. The separation between public/private content is already done via permissions.
We just need a bit more granular control over them.
From the programming point of view, I think, it is the matter of adding an optional override permission
, which as you said 99% of users won't use.
So main permission will be inherited as in your current logic, but override permission
can override the main permission for the object itself, not for its children
Would you be interested if I make a PR?
Would you be interested if I make a PR?
No. As above I wouldn't want to add the extra complexity into the permission system, especially upon little proven benefit to our audience base.
If you have the PHP skills to make a PR, then taking advantage of the logical theme system as advised above may well cover your needs.
Thanks for the feedback
Describe the feature you'd like
Sometimes, we need to allow access to a book but deny access to every future new pages. Currently every new page will inherit allow access permission.
I would like to be able to allow access to the book but make new pages by default inherit deny access.
Describe the benefits this would bring to existing BookStack users
I have Book1 with Page2 Page3. And I want to open to external world only Page2
Granting Public view permissions for Page2 is straightforward.
Both options seem to be annoyingly unfriendly.
Can the goal of this request already be achieved via other means?
No
Have you searched for an existing open/closed issue?
How long have you been using BookStack?
Under 3 months
Additional context
No response