> 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/main-dashboard/navigation.md).

# Navigation

Use the UI to connect providers, configure pairs, and run syncs.

Most setup problems come from [**Connections**](/crosswatch/settings/connections.md), [**Pairs**](/crosswatch/settings/configure-pairs.md), or [**Metadata / ID Mapping**](/crosswatch/settings/connections/metadata.md).

{% hint style="success" %}
If you feel lost in the UI, start from **Settings** and **Main**.
{% endhint %}

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

### Start here

Use these pages most often:

* [Main dashboard](/crosswatch/main-dashboard.md) — overview and top actions
* [Status dashboard](/crosswatch/main-dashboard/status-dashboard.md) — live system status
* [Dashboard widgets](/crosswatch/main-dashboard/dashboard-widgets.md) — watchlist, history, ratings, and scrobble widgets
* [Watchlist](/crosswatch/main-dashboard/navigation/watchlist.md) — unified watchlist view
* [Quick Add](/crosswatch/main-dashboard/navigation/quick-add.md) — manual history, watchlist, and rating actions
* [Playback](/crosswatch/main-dashboard/navigation/playback.md) — unfinished playback records
* [Output panel](/crosswatch/main-dashboard/output-panel.md) — Sync, Watcher, and Debug output

<figure><img src="/files/zhmU9eXYsDVYv9VGo3kq" alt=""><figcaption><p>Main navigation with the dashboard, tools, and settings entry points.</p></figcaption></figure>

### Common paths

#### Connect providers

1. Open **Settings → Connections**
2. Connect what you need
3. Click **Save**

#### Create a pair

1. Open **Synchronization**
2. Create one pair first
3. Start with **one-way** and **one feature**

#### Run and check

1. Go to **Main**
2. Run a sync
3. Review the results
4. Fix mismatches in [Analyzer](/crosswatch/main-dashboard/tools/analyzer.md) or [Editor](/crosswatch/main-dashboard/navigation/editor.md)

### Saving changes

* Click **Save** to persist changes.
* Active runs use the next saved settings.
* Some changes need a restart.
  {% endtab %}

{% tab title="Power users" %}

### Key settings areas

Most configuration lives under **Settings**.

Use these pages for the deeper controls:

* [Settings](/crosswatch/settings.md)
* [Connections](/crosswatch/settings/connections.md)
* [Metadata / ID Mapping](/crosswatch/settings/connections/metadata.md)
* [Configure Pairs](/crosswatch/settings/configure-pairs.md)
* [Scheduling](/crosswatch/settings/scheduling.md)
* [Scrobble](/crosswatch/settings/scrobbler.md)
* [Recent Activity](/crosswatch/settings/scrobbler/recent-activity.md)
* [Maintenance](/crosswatch/settings/maintenance.md)
* [HTTPS/TLS](/crosswatch/advanced-and-api/https-and-tls.md)
* [Plex SSO](/crosswatch/settings/ui-settings/security/plex-sso.md)

### Notes

Connected providers appear in **Synchronization** only after they connect.

Most setup issues come from authentication, mapping, or pair rules.

For feature-level behavior, use [Synchronization](/crosswatch/settings/synchronization.md) and [Tools](/crosswatch/main-dashboard/tools.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/main-dashboard/navigation.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.