> For the complete documentation index, see [llms.txt](https://wiki.crosswatch.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.crosswatch.app/crosswatch/settings/ui-settings/security/plex-sso.md).

# Plex SSO

Plex SSO adds **Sign in with Plex** to the CW login page.

It does **not** replace the normal CW admin login.

You still keep your local username and password as the fallback and recovery path.

{% hint style="info" %}
Plex SSO is separate from [Auth: Plex](/crosswatch/settings/connections/media-servers/plex.md).

Linking Plex for UI sign-in does not change your Plex sync profile.
{% endhint %}

### What Plex SSO does

* Shows a **Sign in with Plex** button on the login page
* Lets you sign into the CW web app with one linked Plex account
* Creates a normal CW session after Plex verifies your identity
* Uses the same session, logout, and remember-me behavior as local login

### What Plex SSO does not do

* It does not replace local admin credentials
* It does not let any Plex account sign in
* It does not configure Plex for syncing
* It does not change Plex Media Server authentication used elsewhere in CW

### Requirements

Before you enable Plex SSO:

* UI login must already be enabled
* You must already have a local CW admin account
* You must be able to sign in with that local account first
* The Plex account you want to use must be linked from the Security section

{% hint style="warning" %}
Keep your local CW admin login working.

If Plex is unavailable, use the local account to sign in.
{% endhint %}

### Enable Plex SSO

1. Sign into CW with your local admin username and password.
2. Open **Settings**.
3. Go to **UI Settings**.
4. Open **Security**.
5. In **Plex sign-in**, click **Link Plex account**.
6. Complete the Plex approval flow.
7. Save if the UI asks you to save changes.

After linking succeeds, the login page shows **Sign in with Plex**.

### Sign in with Plex

1. Open the CW login page.
2. Click **Sign in with Plex**.
3. Approve CW in the Plex window.
4. Return to CW.
5. CW signs you in and creates a normal local session.

If you are already signed into Plex in that browser, Plex may skip most of the prompt.

### Session behavior

Plex SSO uses the same CW session system as local login.

That means:

* **Remember me** keeps you signed in for the configured session duration
* Leaving it unchecked creates a browser-only session
* **Log out** removes the CW session the same way as local login

### Disable Plex SSO

1. Sign into CW with a local admin account.
2. Open **Settings**.
3. Go to **UI Settings**.
4. Open **Security**.
5. In **Plex sign-in**, click **Unlink**.

This removes the linked Plex account and hides **Sign in with Plex** from the login page.

### Troubleshooting quick checks

* **Button missing**: make sure UI login is enabled and Plex is linked
* **Plex window did not open**: disable popup blockers for CW
* **Plex is down**: sign in with your local CW admin account instead
* **Wrong Plex account**: unlink it, then link the correct account


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://wiki.crosswatch.app/crosswatch/settings/ui-settings/security/plex-sso.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.