Separate everyday viewing from server management
A Jellyfin user is local to the server, and many capabilities are configured per user. Before creating a household viewing profile, decide what that person actually needs to do: watch media, manage the server, modify a collection or delete source files. A successful login does not answer those permission questions.
Use an administrator account to review the server settings, then create or select the intended viewer profile. Keep a note of its role and intended libraries. Do not reuse the administrator merely because it makes every item visible during a test. That hides whether the ordinary viewer has the access you intended.
Review broad and narrow permissions deliberately
Jellyfin’s allow-this-user-to-manage-the-server option grants full server-management access. Treat that as a role decision rather than a troubleshooting button for a missing film. If the viewer only needs playback, investigate the relevant library and playback permissions through the user’s settings.
The developer also exposes audio and video transcoding controls per user. If a file works for one profile but not another, compare those permissions along with the selected client and track. Avoid broadening every permission at once; the goal is to understand which capability is required for the actual viewing route.
Understand deletion before enabling it
Jellyfin documents that media deletion can remove files from the filesystem, not merely hide a poster. Its behavior also depends on the server’s filesystem permissions. Decide whether deletion is appropriate for this user and, where applicable, for the specific library. Keep this separate from the server’s need to read media for playback.
Do not test deletion against a valued original. If an operational test is necessary, use an explicitly disposable sample you created for that purpose and know how your storage backups work. A file that reappears after a scan may indicate that filesystem permissions prevented removal; it is not a reason to grant unrestricted write access without reviewing the intention.
Verify through the viewer’s actual client
Sign in as the viewer on the intended client and inspect the available libraries and controls. Open one permitted item and check that the profile’s history is separate where expected. Use the administrator only to review a remaining access difference, then return to the viewer account for the next observation.
Retain the final role and permission choices in private server notes. The result should be a profile with understood capabilities, not simply a profile for which every checkbox is enabled. This is a server-administration procedure; it does not certify the suitability of a particular household’s content or replace its own access decisions.
Questions answered
Does Delete only remove a poster from the library?
No. Jellyfin documents that the permission can delete the media from the filesystem. Review both user and server-file permissions before enabling it.
Should I make a viewer an administrator to solve a missing library?
First inspect the intended library and user permissions. Server-management access is a much broader role than ordinary viewing.
Sources & further reading
Official references for the subjects discussed. Service terms and device software can change.