[Enhancement]: Allow permission setting for regular users to create or edit collections #1959

New issue

Open

opened 2026-02-20 02:09:42 -05:00 by deekerman · 0 comments

deekerman commented

2026-02-20 02:09:42 -05:00

Owner

Originally created by @cassieesposito on GitHub (Mar 1, 2024).

Describe the feature/enhancement

I don't want to give my users the ability to edit metadata, files, or otherwise create real chaos on the server, but it would be neat if there were a way to give them permission to edit collections. One use case for this would be a collection for individual user's recommendations.

Followup would be per-collection based permission settings so, for example.

In order to create a collection, Bob needs to have the user-setting "create collections." Any collection Bob creates, he is the owner of and can therefore change the permissions for. By default, the newly created collection gives "All Users" permission to view, but not permission to add items, remove items, or delete the entire collection. Those could each be configured separately for "All Users" or on a per-user basis.

If Bob doesn't have permission to create a collection, but still wants one or two to play with, an admin could create those collections and make Bob the owner, at which point Bob could manage the collection-level permissions.

Originally created by @cassieesposito on GitHub (Mar 1, 2024). ### Describe the feature/enhancement I don't want to give my users the ability to edit metadata, files, or otherwise create *real* chaos on the server, but it would be neat if there were a way to give them permission to edit collections. One use case for this would be a collection for individual user's recommendations. Followup would be per-collection based permission settings so, for example. In order to create a collection, Bob needs to have the user-setting "create collections." Any collection Bob creates, he is the owner of and can therefore change the permissions for. By default, the newly created collection gives "All Users" permission to view, but not permission to add items, remove items, or delete the entire collection. Those could each be configured separately for "All Users" or on a per-user basis. If Bob doesn't have permission to create a collection, but still wants one or two to play with, an admin could create those collections and make Bob the owner, at which point Bob could manage the collection-level permissions.