# Settings

Use **Settings** to configure CrossWatch.

Start with **Providers** and **Sync pairs**.

{% hint style="success" %}
CW has lots of knobs. Most users can leave the defaults alone.

Focus on the few things that matter:

* Connect providers in **Providers**
* Configure **TMDb** metadata
* Create a **Sync pair** and enable the feature you want
  {% endhint %}

### Settings overview

The **Overview** screen is a dashboard.

Use it to spot missing config fast.

#### Quick actions

Use **Quick actions** to jump straight into common setup:

* **Open providers** (auth, sync, metadata)
* **Open sync pairs** (create source/target pairs)
* **Open scrobbler** (routes, webhook, filters)
* **Open UI settings** (UI, security, CW Tracker)

#### Status overview

Use **Status overview** to confirm what CW currently detects:

* Connected **Authentication providers**
* Configured **Synchronization providers** and pair count
* **Metadata providers** detected vs configured
* **Scheduling** status (enabled/disabled)
* **Scrobbler** status (running/stopped) and active routes

### Providers

**Providers** is the home for:

* **Authentication** (tokens, URLs, profile IDs)
* **Synchronization** provider configuration (what adapters are available)
* **Metadata** (TMDb)

#### Authentication

Connect providers like Plex, Jellyfin, Emby, Trakt, SIMKL, and MDBList.

Providers appear in **Sync pairs** only after they connect.

Related: [Authentication](/crosswatch/providers/authentication.md).

#### Metadata

Metadata (TMDb) improves matching. It reduces wrong links and missing peers.

Related: [Metadata](/crosswatch/providers/metadata.md).

### Sync pairs

Sync pairs define what syncs with what.

{% hint style="info" %}
The default pair settings are good for most users.

Start with **one-way** + **one feature** + **Dry run**.
{% endhint %}

* **Direction**: source → target (example: Plex → Trakt).
* **Mode**: one-way or two-way.
* **Features**: Watchlist, History, Ratings, Progress (where supported).
* **Writes**: allow **Add** and/or **Remove**.

Related:

* [Syncing](/getting-started/first-time-setup/what-do-you-need/syncing.md)
* [Configure Pairs](/crosswatch/configure-pairs.md)
* [Synchronization](/crosswatch/providers/synchronization.md)

### Scheduling

Configure periodic runs.

Avoid overlaps. Start daily and tune later.

Related: [Scheduling](/crosswatch/scheduling.md).

### Scrobbler

Real-time scrobbling uses **Watcher** (preferred) or legacy Webhooks.

It requires connected providers (example: Plex + Trakt).

{% hint style="info" %}
Defaults are good here too. Add your scrobble **routes**, then enable **Watcher**.
{% endhint %}

Related:

* [Scrobble](/crosswatch/scrobble.md)
* [Watcher](/crosswatch/scrobble/watcher.md)

### UI settings

UI settings covers:

* dashboard visibility
* web sign-in
* protocol and TLS
* CW Tracker defaults

Related: [UI settings](/crosswatch/navigation/ui-settings.md).

#### Security (UI login)

Enable login to protect CW with a username and password.

CW now enforces credential setup.

Set a username and password before login becomes active.

Click **Log-in to activate** after enabling.

Session persistence is configurable.

By default, persistent sessions are disabled.

Users sign in again after the browser closes.

You can enable persistent sessions for `1–365` days.

Security also shows the current browser session and other active browser sessions.

Use **Log out other sessions** to clear old browser logins without signing out the browser you are using now.

**Plex SSO**

You can optionally add **Sign in with Plex** for the web app.

This is an extra sign-in method.

Local CrossWatch credentials stay as the fallback and recovery path.

Guide: [Plex SSO](/crosswatch/navigation/ui-settings/security/plex-sso.md).

**Trusted reverse proxies**

If you run CrossWatch behind a reverse proxy, set **Trusted reverse proxies** here.

This makes forwarded client IPs and scheme accurate.

It improves secure cookies and rate limiting.

Related: [Reverse proxies](/related-information/reverse-proxies.md).

### Maintenance

Operational tools:

* Enable debug logging.
* Clear state and cache.
* Reset statistics.

Related: [Maintenance](/crosswatch/maintenance.md).

{% hint style="warning" %}
Clearing state changes the next plan.

Use it after changing direction, features, or provider identity.
{% endhint %}

### Saving and applying changes

* Use **Save** to persist changes.
* If a run is active, changes apply on the next run.


---

# Agent Instructions: 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:

```
GET https://wiki.crosswatch.app/crosswatch/navigation/settings.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.