Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unexpected behaviour with shelf create permissions #2690

Closed
maggie44 opened this issue Apr 19, 2021 · 4 comments
Closed

Unexpected behaviour with shelf create permissions #2690

maggie44 opened this issue Apr 19, 2021 · 4 comments
Labels
Milestone

Comments

@maggie44
Copy link

maggie44 commented Apr 19, 2021

With the custom permissions indicated in the attached image set on a shelf, I expected the behaviour to be:

Users can View + Users can Create new books + Users cannot update the shelf details + Users cannot delete the shelf

Instead, the Create permission does not appear to have any affect unless Update is also ticked. This in turn means I cannot let people contribute books to my shelf, without also allowing them to edit my Shelf details.

Screenshot 2021-04-19 at 14 02 50

BookStack v21.04

@maggie44 maggie44 changed the title Unexpected behaviour with permissions Unexpected behaviour with custom permissions Apr 19, 2021
@ssddanbrown
Copy link
Member

Thanks for raising @Maggie0002.

Yeah, The create permissions are currently redundant, likely originally copied from the permission options of books.

This in turn means I cannot let people contribute books to my shelf, without also allowing them to edit my Shelf details.

Is this just an example of a flow that may be broken from the current permission behaviour? Or is this an ability that you actually desire for your usage? If you desired this permission to allow the adding/removing of books I think we'd want to rename "Create" to "Curate" or "Manage Assigned Content". That would also need some more complex changes in functionality since the behaviour is not set-up for separate editing and curation.

@maggie44
Copy link
Author

maggie44 commented Jun 1, 2021

Thanks for raising @Maggie0002.

Yeah, The create permissions are currently redundant, likely originally copied from the permission options of books.

This in turn means I cannot let people contribute books to my shelf, without also allowing them to edit my Shelf details.

Is this just an example of a flow that may be broken from the current permission behaviour? Or is this an ability that you actually desire for your usage? If you desired this permission to allow the adding/removing of books I think we'd want to rename "Create" to "Curate" or "Manage Assigned Content". That would also need some more complex changes in functionality since the behaviour is not set-up for separate editing and curation.

It is something I desired for my usage. Although it's not time sensitive. Perhaps best to flag this one for thought as part of the broader permissions review you note is scheduled in the readme?

@ssddanbrown ssddanbrown changed the title Unexpected behaviour with custom permissions Unexpected behaviour with shelf create permissions Oct 3, 2022
@ssddanbrown
Copy link
Member

A note that #3073 and #4326 have had different expectations to this, in expecting to be able to create new books within this shelf (Which would raise other concerns due shelf->book relationship).

I think for now it'd be better to be pragmatic and go ahead to remove this option from view (and delete existing entries) so that it's not causing confusion. User abilities/actions that may have been desired from this can then be raised independently of this specific check-box/implementation.

@ssddanbrown
Copy link
Member

Create permission now removed from view as per above, within 847a57a. Will be part of the next feature release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

2 participants