> 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/connections/media-servers/plex.md).

# Plex

{% tabs %}
{% tab title="End users" %}

<figure><img src="/files/h8wxRy6cS9zQVLnV4euR" alt=""><figcaption></figcaption></figure>

### Connect Plex

1. Click **Connect Plex**.
2. A new tab opens and asks for a PIN.
3. Copy the PIN from **Link code** in CrossWatch. Paste it into the Plex page.
4. After Plex accepts the PIN, close the Plex tab.
5. Back in CrossWatch, open **Settings** for Plex.
6. Verify these values are filled:
   * **Server ID**
   * **Username**
   * **Account ID**
7. Click **Save**.

### Plex users: owner, managed users, and friends

Plex can return several user types in the user list:

* **Owner** — the Plex account that authenticated CrossWatch
* **Managed user** — a user inside the owner’s Plex Home
* **Friend or shared user** — a separate Plex account with access to one or more shared libraries

A friend or shared account is **not** the same as a Plex Home managed user.

#### Friend and shared account support

CrossWatch stores the token from the Plex account that completed the sign-in flow.

When you select a friend or shared user, CrossWatch can try to use Plex’s server-scoped shared token for that user.

That token is limited to your Plex Media Server.

It does **not** give CrossWatch full access to the friend’s Plex account, profile, watchlist, ratings, or other cloud data.

Current support:

* ✅ **History** — supported
* ✅ **Progress** — supported
* ❌ **Ratings** — not supported
* ❌ **Watchlist** — not supported

{% hint style="warning" %}
This depends on Plex’s shared-server token behavior.

Plex has changed this path before and may change or remove it again.
{% endhint %}

When requested user scope cannot be applied, CW stops the operation.

#### Plex Home managed users

Plex Home managed users work differently from friends.

CW can try to switch the authenticated Plex Home account into the selected managed user.

If the managed user is protected by a Plex Home PIN, configure the correct PIN too.

Use the server owner’s Plex profile for Plex Home managed users.

Use a separately authenticated Plex profile for friends when you need personal account features like watchlist or ratings.

### Optional: whitelisting (libraries)

If you don’t see your libraries:

1. Click **Load Libraries**.
2. Pick the libraries you want CW to use.
3. Click **Save**.

Guide: [Library Whitelisting](/crosswatch/settings/connections/library-whitelisting.md).
{% endtab %}

{% tab title="Power users" %}

### Config keys

Stored under:

* `plex.*`

Common keys:

* `plex.account_token`
* `plex.server_id` / `plex.account_id` (when present)

### Related docs

* Sync module: [PLEX module](broken://spaces/3rh5THg1PdhVsBt3GALo/pages/35fa1d8db98b0b38d8f267852d3687b2a8ac4dd2)
* Adapter: [Adapter: Plex](/crosswatch/settings/synchronization/media-servers/plex.md)
  {% endtab %}
  {% endtabs %}


---

# 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/connections/media-servers/plex.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.