User able to manage collections but not view them #6201

Closed
opened 2026-02-07 03:15:37 +03:00 by OVERLORD · 3 comments
Owner

Originally created by @GSDan on GitHub (Aug 15, 2024).

This issue respects the following points:

  • This is a bug, not a question or a configuration issue; Please visit our forum or chat rooms first to troubleshoot with volunteers, before creating a report. The links can be found here.
  • This issue is not already reported on GitHub (I've searched it).
  • I'm using an up to date version of Jellyfin Server stable, unstable or master; We generally do not support previous older versions. If possible, please update to the latest version before opening an issue.
  • I agree to follow Jellyfin's Code of Conduct.
  • This report addresses only a single issue; If you encounter multiple issues, kindly create separate reports for each one.

Description of the bug

When given the 'Manage collections' permission, users are able to create a collection without having access to the 'Collections' library. As a result, the confusing situation arises where you can create and add items to a collection, but not view or edit it after moving away from the initial creation view. The dropdown in the 'add to collection' modal only ever showed 'New...'.

Suggestions:

  • The Collections library should exist by default when creating a new server or upon granting a user the manage collections permission for the first time, not just be created upon the first collection being instantiated.
  • Users granted the manage collections permission should always have access to the Collections library

Reproduction steps

  1. Give a user the manage collections permission, but not access to the collections library (if it exists)
  2. Have them try to add content to a collection.

What is the current bug behavior?

The user is only given the ability to create a new collection. If they enter the same collection name twice, it will show with any prior changes.
The collections library now exists if it did not previously, and the user does not have access to the collection they have made.
Trying to add another piece of content will still only show the 'New...' option in the 'add to collection' modal.

What is the expected correct behavior?

The user has access to the collection that was created

Jellyfin Server version

10.9.9+

Specify commit id

No response

Specify unstable release number

No response

Specify version number

No response

Specify the build version

10.9.9

Environment

Latest docker container 10.9.9
Accessed via web 10.9.9

Jellyfin logs

No relevant output

FFmpeg logs

No response

Client / Browser logs

No response

Relevant screenshots or videos

No response

Additional information

No response

Originally created by @GSDan on GitHub (Aug 15, 2024). ### This issue respects the following points: - [X] This is a **bug**, not a question or a configuration issue; Please visit our forum or chat rooms first to troubleshoot with volunteers, before creating a report. The links can be found [here](https://jellyfin.org/contact/). - [X] This issue is **not** already reported on [GitHub](https://github.com/jellyfin/jellyfin/issues?q=is%3Aopen+is%3Aissue) _(I've searched it)_. - [X] I'm using an up to date version of Jellyfin Server stable, unstable or master; We generally do not support previous older versions. If possible, please update to the latest version before opening an issue. - [X] I agree to follow Jellyfin's [Code of Conduct](https://jellyfin.org/docs/general/community-standards.html#code-of-conduct). - [X] This report addresses only a single issue; If you encounter multiple issues, kindly create separate reports for each one. ### Description of the bug When given the 'Manage collections' permission, users are able to create a collection without having access to the 'Collections' library. As a result, the confusing situation arises where you can create and add items to a collection, but not view or edit it after moving away from the initial creation view. The dropdown in the 'add to collection' modal only ever showed 'New...'. Suggestions: - The Collections library should exist by default when creating a new server or upon granting a user the manage collections permission for the first time, not just be created upon the first collection being instantiated. - Users granted the manage collections permission should always have access to the Collections library ### Reproduction steps 1. Give a user the manage collections permission, but not access to the collections library (if it exists) 2. Have them try to add content to a collection. ### What is the current _bug_ behavior? The user is only given the ability to create a new collection. If they enter the same collection name twice, it will show with any prior changes. The collections library now exists if it did not previously, and the user does not have access to the collection they have made. Trying to add another piece of content will still only show the 'New...' option in the 'add to collection' modal. ### What is the expected _correct_ behavior? The user has access to the collection that was created ### Jellyfin Server version 10.9.9+ ### Specify commit id _No response_ ### Specify unstable release number _No response_ ### Specify version number _No response_ ### Specify the build version 10.9.9 ### Environment ```markdown Latest docker container 10.9.9 Accessed via web 10.9.9 ``` ### Jellyfin logs ```shell No relevant output ``` ### FFmpeg logs _No response_ ### Client / Browser logs _No response_ ### Relevant screenshots or videos _No response_ ### Additional information _No response_
OVERLORD added the bugstale labels 2026-02-07 03:15:37 +03:00
Author
Owner

@jellyfin-bot commented on GitHub (Dec 14, 2024):

This issue has gone 120 days without an update and will be closed within 21 days if there is no new activity. To prevent this issue from being closed, please confirm the issue has not already been fixed by providing updated examples or logs.

If you have any questions you can use one of several ways to contact us.

@jellyfin-bot commented on GitHub (Dec 14, 2024): This issue has gone 120 days without an update and will be closed within 21 days if there is no new activity. To prevent this issue from being closed, please confirm the issue has not already been fixed by providing updated examples or logs. If you have any questions you can use one of several ways to [contact us](https://jellyfin.org/contact).
Author
Owner

@jellyfin-bot commented on GitHub (Jan 5, 2025):

This issue was closed due to inactivity.

@jellyfin-bot commented on GitHub (Jan 5, 2025): This issue was closed due to inactivity.
Author
Owner

@mark-harmison commented on GitHub (Dec 4, 2025):

I see this issue was closed for inactivity a long time ago, but the problem still exists and I just spend several hours pulling my hair out before I found this bug report. This is very confusing since you can perform many collection-related operations that appear to just have no effect whatsoever until you make this library available. If this information is covered in any documentation they I cannot find it. There are a lot of posts in various places but this appears to be the only place where we are told to enable the collections library.

@mark-harmison commented on GitHub (Dec 4, 2025): I see this issue was closed for inactivity a long time ago, but the problem still exists and I just spend several hours pulling my hair out before I found this bug report. This is very confusing since you can perform many collection-related operations that appear to just have no effect whatsoever until you make this library available. If this information is covered in any documentation they I cannot find it. There are a lot of posts in various places but this appears to be the only place where we are told to enable the collections library.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/jellyfin#6201