mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-02-05 00:29:48 +03:00
Per page Public flag #790
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 @pth0rn on GitHub (Aug 22, 2018).
Sorry I did not see any submissions regarding this, if it's already been brought up.
I wanted to suggest having an option for each page to make it public/private, instead of making the whole site public or requiring a public user login.
@ssddanbrown commented on GitHub (Aug 23, 2018):
Hi @Vicvinegar0,
Is is kind of possible to do this. Non-logged-in visitors receive the
Publicrole. You can make the whole site public but then adjust permissions for this role. Removing the 'View' permissions on items should prevent them seeing anything by default.For items you do want them to see you can then set custom permissions per book, chapter or page to allow the 'public' role to view. Permissions to trickle down from Books > Chapters > Pages.
The only annoying thing at the moment is that when you select custom permissions on a book/chapter/page you have to set them for all roles (Apart from admins) but this is something I want to improve in the future.
@thomasmoors commented on GitHub (Jun 10, 2022):
Hi, could it be this feature is no longer working as intended? I have 2 pages that have public viewing assigned, but are still not visible without logging in.
@ssddanbrown commented on GitHub (Jun 10, 2022):
@thomasmoors Is public access enabled in your BookStack settings?:
@thomasmoors commented on GitHub (Jun 13, 2022):
But then everything is public, so maybe I misunderstood? I would like to create "opt-in" public pages. Not opt-out.
@ssddanbrown commented on GitHub (Jun 13, 2022):
@thomasmoors Yes, but the public access can be controlled via the Guest user as per the message shown for the option. Please see my original 2018 comment above for achieving an opt-in style public setup.
@thomasmoors commented on GitHub (Jun 14, 2022):
Thank you for your awesome work and active support, I know it's not "nothing".
@ssddanbrown commented on GitHub (Nov 8, 2022):
I'm going to go ahead and close this off since there's been relatively little demand since opening.
I still intend to implement #288 in the future. Between that and the above explained setups, I think that can cover most use-cases.