2024-05-21, 05:29 PM
Yes and no. No because if you provide the media within a library the user has access to, they can access it.
Yes because you have a couple of ways to restrict access (well, a few, but most advanced cases seem like too much work IMO). First, restriction by obfuscation -- make sure you title these releases so that the FHD version comes first. The documentation has info on how to accomplish this via naming (alphabetically with tags or via using specific resolution designations). SEE: https://jellyfin.org/docs/general/server...of-a-movie
The easiest way -- I guess, again, in my opinion -- is to use libraries. Move the 4K/HDR/problematic content to a different folder (outside the parent structure of its current home) and add that folder to a different library, then ensure that users you're concerned about do not have access to that library.
Yes because you have a couple of ways to restrict access (well, a few, but most advanced cases seem like too much work IMO). First, restriction by obfuscation -- make sure you title these releases so that the FHD version comes first. The documentation has info on how to accomplish this via naming (alphabetically with tags or via using specific resolution designations). SEE: https://jellyfin.org/docs/general/server...of-a-movie
The easiest way -- I guess, again, in my opinion -- is to use libraries. Move the 4K/HDR/problematic content to a different folder (outside the parent structure of its current home) and add that folder to a different library, then ensure that users you're concerned about do not have access to that library.
Jellyfin 10.10.7 LSIO Docker | Ubuntu 24.04 LTS | i7-13700K | Arc A380 6 GB | 64 GB RAM | 79 TB Storage