BookStack icon indicating copy to clipboard operation
BookStack copied to clipboard

Per page Public flag

Open pth0rn opened this issue 7 years ago • 6 comments

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.

pth0rn avatar Aug 21 '18 23:08 pth0rn

Hi @Vicvinegar0,

Is is kind of possible to do this. Non-logged-in visitors receive the Public role. 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.

ssddanbrown avatar Aug 23 '18 19:08 ssddanbrown

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.

thomasmoors avatar Jun 10 '22 05:06 thomasmoors

@thomasmoors Is public access enabled in your BookStack settings?:

image

ssddanbrown avatar Jun 10 '22 12:06 ssddanbrown

@thomasmoors Is public access enabled in your BookStack settings?:

But then everything is public, so maybe I misunderstood? I would like to create "opt-in" public pages. Not opt-out.

thomasmoors avatar Jun 13 '22 10:06 thomasmoors

@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.

ssddanbrown avatar Jun 13 '22 11:06 ssddanbrown

Thank you for your awesome work and active support, I know it's not "nothing".

thomasmoors avatar Jun 14 '22 07:06 thomasmoors

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.

ssddanbrown avatar Nov 08 '22 11:11 ssddanbrown