Jellyfin Quick Connect: the new screen and approving screen have different jobs

Identify the screen waiting for approval

On the client being added, select Quick Connect where supported. Jellyfin says some clients first require Manual Login, while others show the code directly. Keep that screen open so the approving person can use the current six-character code.

For an illustrative living-room setup, the television is the waiting device and the household member’s signed-in browser is the approving device. Entering the television code back into an unrelated television menu does not complete those two roles. First check the intended Jellyfin server and account on the browser.

Choose a client able to approve another one

The official client table separates logging in with Quick Connect from authorising another client. For example, it lists Jellyfin Android TV as supporting the login role but not the approval role; Jellyfin Web supports both. Consult the current table for the actual client rather than extending that example to every platform.

On the authenticated client, the documented route is Settings, Quick Connect, then entry and confirmation of the code. Use the account whose library access is intended for the new device. Code approval should be a deliberate account action, especially on a shared television.

Resolve an unavailable or expired flow

Jellyfin documents a server-wide Quick Connect control in the administrator dashboard. If the feature is unavailable, ask the authorised operator whether it is enabled and whether the particular clients support the required roles. Repeated password changes do not answer those capability and policy questions.

An invalid or expired code requires another attempt with the current code. Do not reuse an old photograph as a permanent sign-in credential or approve a code sent by someone whose device you cannot identify. Keep account recovery separate if the approving device itself is no longer signed in.

Check the account after approval

Once the new screen signs in, inspect the displayed account and expected library before starting a programme. Successful approval establishes that login step; it does not establish that every title can play in that client or that the account has administrative permission.

A useful support report names the two clients and versions, which displayed the code, which attempted approval and the visible result. Exclude the code and credentials from a public report. This workflow follows Jellyfin’s documentation and an illustrative household example; no private Jellyfin account or television was tested.

Questions about this guide

Sources and further reading

• Jellyfin: Quick Connect