mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-02-06 09:09:38 +03:00
add unauthenticated special role for unauthenticated users
#124
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 @squiddle on GitHub (Jul 3, 2016).
That would allow to configure individual books to be publicly viewable or even editable (not sure about drafts, as there is no real user identity and garbage drafts could accumulate). But at least view should be selectable to allow public viewing in a single book.
Why use the role system for this? It adds not another mechanism into the authentication system, but builds on the existing one.
It also allows the removal of the public-viewing setting, which currently also acts as a second authorization information source. With an unauthenticated role it just means view for the unauthenticated user role and could be managed from the role settings page together with all other authorization settings.
@ssddanbrown commented on GitHub (Jul 4, 2016):
Hi @squiddle, Thanks for the suggestion. This should be fairly simple since that's exactly how the public permissions are currently handled! The system just hides the public role from any view.
If you view the
rolestable in your database you'll see a public role. Changing thehiddenvalue from 1 to 0 will make it show up. Things do get funky when trying to edit as a public member though since they're not technically a user.@riorii commented on GitHub (Sep 22, 2016):
Hey @ssddanbrown , any idea if this enhancement is gonna be on the next release?
@ssddanbrown commented on GitHub (Sep 29, 2016):
@riorii Yes, it will be. Although next release may not be for a small while.