mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-05-04 18:08:46 +03:00
Permissions Feature Requests #192
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 @pinglanyue on GitHub (Oct 31, 2016).
In settings/roles page,can add 3 other permissions:
1.Lock : If locked,can't edit and delete (until unlock it).
2. Delete Forever and Delete:If DELETE a book,viewer can't see it,but didn't delete it from database,admin can recovery/reopen it.But if Delete Forever (only admin or settting roles ),the book will delete from database.(If a book was locked ,can't delete and "forever delete".)
3. Except the own and all permissions setting,can add a group setting.(Also should add a 'setting/group' page to set/control group.Or 'settings/roles' can have admin,editor,group,viewer by default setting )
@pinglanyue commented on GitHub (Nov 15, 2016):
Hi,@ssddanbrown .I use 0.13 and see new permission control.Consider current open issues about permissions:
#112
#299
#299
I have a idea about the permissions setting:
Now role setting
Use Group
Users page:
Individual: Own setting just here,user sign up have no role ,Individual role user can create book,and make a book private or public.
Group:later ~
Roles page:
Admin
Editor
GroupSuperAdmin
Group
Individual
Public
....(custom setting)
Group's role permissions（only Admin and GroupSuperAdmin can setting）:
GroupAdmin
GroupEditor
GroupViewer(default)
no other role setting
Groups page:
User:Group=>N:N
(Admin/GroupSuperAdmin can create a group.One group only have one GroupSuperAdmin,but can have many GroupAdmin.GroupAdmin can't create book,but can manage all other thing.)
Example:
User1 create GroupA and GroupC。
Add user and setting user's pressions:UserA is GroupA's editor,can User3 is Group's admin.
Create a book/project named Book1,so this book can setting this permissions:Public(everyone can view,default setting)or Group(only selected group's user can see)。chapter and page 's permisson setting is inherit book permisson's setting.but also do this special thing：Book1 have Chapter1 and Chapter2,in Chapter permission setting,you can select by role or by group.ex:only want to GroupA manage Chapter1's content and GroupB manage Chapter2。
another case : Book2 is GroupA 's private book ,user can join GroupA to see it.Different group can make own project book.music group,movie group etc...if have a group setting,is onvenient on these scene.
Create a group is easy to manage content control.And create more and more custom role to control will became more and more diffculte.In some case ,Like javabook only who like java can see,
Also can make role control group,group control user.Admin is admingroup,editor is editorgroud,and single use alos can meaning only a user in a group...
@ssddanbrown commented on GitHub (Aug 4, 2018):
I'll be honest, I've never responded to this since I've never really understood the request here. After re-reading I still don't really understand. I appreciate the effort you've gone to here though.
This may even be solved with the good amount of permission system changes since this original request.
If you still require change in the permission system please open a new request with an example that's as simple as possible. Thanks.