You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the user's ability to add/remove a book to/from a shelf is given by bookshelf-update-own and bookshelf-update-all permissions. It would be very handy to separate the add/remove a book to/from a shelf from other booksheld editions --> introducing its own standalone permission.
The usecase description is probably obvious:
I (as an administrator) want to have fully under my control the shelves - their creation, deletion, name, description, image etc. The structure of the shelves is something I want to set from adminostrator side and then keep it "locked" for all users.
On the other hand, I want the users to create/update/delete their books - and to assign them flexibily to current existing given Shelves.
With current BookStack functionality I can't do that. Currently I have only two non-ideal options:
I will give all the users the Bookshelf Update permissions - and anyone will be then able to edit the bookshelves title, description, image... (I don't want to allow them)
Or I will not give them the permissions - and then I will have to assign/reassign/remove all the books to/from shelves by myself (I don't want to do that, that's something related much more to book edit than to shelf edit)
OR! ALTERNATIVE SOLUTION - MUCH EASIEST AND FULLY SUFFICIENT:
Instead of splitting to new permission, just use the book-update-own and book-update-all permission for adding/removing a book to/frol a shelf instead of current bookshelf-update-own and bookshelf-update-all permissions.
Describe the benefits this would bring to existing BookStack users
It will introduce much more logical split of permissions and responsibilities between shelf administrator and regular book editor.
Can the goal of this request already be achieved via other means?
No.
Have you searched for an existing open/closed issue?
I have searched for existing issues and none cover my fundamental request
How long have you been using BookStack?
Under 3 months
Additional context
No response
The text was updated successfully, but these errors were encountered:
Describe the feature you'd like
Currently, the user's ability to add/remove a book to/from a shelf is given by
bookshelf-update-own
andbookshelf-update-all
permissions. It would be very handy to separate the add/remove a book to/from a shelf from other booksheld editions --> introducing its own standalone permission.The usecase description is probably obvious:
I (as an administrator) want to have fully under my control the shelves - their creation, deletion, name, description, image etc. The structure of the shelves is something I want to set from adminostrator side and then keep it "locked" for all users.
On the other hand, I want the users to create/update/delete their books - and to assign them flexibily to current existing given Shelves.
With current BookStack functionality I can't do that. Currently I have only two non-ideal options:
OR! ALTERNATIVE SOLUTION - MUCH EASIEST AND FULLY SUFFICIENT:
Instead of splitting to new permission, just use the
book-update-own
andbook-update-all
permission for adding/removing a book to/frol a shelf instead of currentbookshelf-update-own
andbookshelf-update-all
permissions.Describe the benefits this would bring to existing BookStack users
It will introduce much more logical split of permissions and responsibilities between shelf administrator and regular book editor.
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
The text was updated successfully, but these errors were encountered: