Sign in a Jellyfin client through an already authenticated device

The useful distinctions

• Quick Connect uses a temporary six-character code and an already authenticated client.
• Client support differs between logging in and authorizing another client.
• The authenticated client uses Settings, Quick Connect to enter the displayed code.
• An invalid or expired code requires another attempt.

Assign the two roles

Pairing involves one client requesting a session and another client approving it. A client that can display a code is not necessarily able to approve a different device. Check those roles before troubleshooting the server or repeatedly restarting the new client. For a shared television, also verify which existing account is open on the approving device so the result matches the intended user.

Use the live display

The example describes the two devices without supplying a reusable code. Read the temporary value from the new device at the time of authorization and keep that screen open. If the value expires, generate another attempt through the client’s normal sign-in flow. Do not treat a code copied from an old screenshot or tutorial as a server identifier; it is a short-lived approval value for one pending request.

Confirm the resulting account

Once the new client opens, check the visible user identity and expected library access. Successful pairing only establishes a session; it does not prove that every library or playback format is available to that account. If authorization fails, record the two client names, their versions and whether the code was fresh. That information is more useful than sharing the temporary value publicly or changing unrelated account permissions.

A focused way to proceed

1. Check the current client support matrix for both login and authorization roles.
2. On the new client, choose Quick Connect and keep its code screen visible.
3. On your already signed-in client, open Settings and Quick Connect.
4. Enter the currently displayed code and confirm only for the device you intend to authorize.
5. Verify that the new client enters the intended account.

Worked example · synthetic

Device A: owned living-room client displaying a fresh code
Device B: already authenticated Jellyfin Web session
Action: Device B authorizes Device A using the current on-screen value
Check: intended account appears on Device A

Read the comparison

Login and authorization are distinct capabilities; a client can support one without supporting both.

When to stop or ask for help

If a fresh attempt fails on supported clients, provide their versions and observed error to the server administrator.