> 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/configure-pairs.md).

# Configure Pairs

How to configure a sync pair, feature toggles, and safety controls.

Pairs define what syncs, in which direction, and with what safety rules.

* Left = **Source**
* Right = **Target**

Enable only what you need. In one-way pairs, the Source defines desired state.

Two-way pairs use feature-specific conflict rules. The Source is the final fallback.

{% hint style="info" %}
First run: **one-way** and **one feature**
{% endhint %}

{% hint style="success" %}
Most safe first pairs are media server → tracker.
{% endhint %}

{% hint style="info" %}
Defaults are good for most users.

Most setups only require:

* Pick Source and Target
* Pick the right **instances**
* Enable **Watchlist**, **Ratings**, **History**, and/or **Progress**
  {% endhint %}

### Header (the basics)

* **Enabled**: master switch for the pair.
* **Source / Target**: provider pickers.
* **Source instance / Target instance**: pick which instance to use.
  * Defaults to `default`.
  * See [Instances](https://wiki.crosswatch.app/crosswatch/settings/connections/instances.md).
* **Mode**:
  * **One-way**: target follows source.
  * **Two-way**: both sides contribute.

{% hint style="warning" %}
Choose **Two-way** only when you already trust matching on both sides.

For most setups, **One-way** is safer.
{% endhint %}

<figure><img src="https://565675962-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3rh5THg1PdhVsBt3GALo%2Fuploads%2FG5fEYdkKiPkEypByIOuE%2Fimage.png?alt=media&amp;token=9cdace0b-a4c3-47cc-b392-6342b70fd129" alt=""><figcaption></figcaption></figure>

### Feature tabs

Feature tabs show up only when **both** providers support that feature.

Start here for feature-specific options: [Features](https://wiki.crosswatch.app/crosswatch/settings/configure-pairs/features.md).

Pairs that contain **AniList** can show extra options on **Watchlist** and **Ratings**.

That includes **Use Anime ID Mapping** and, when AniList can receive writes, **Anime-only sync**.

See [AniList pair options](https://wiki.crosswatch.app/crosswatch/settings/configure-pairs/anilist-pair-options.md).

* [Watchlist](https://wiki.crosswatch.app/crosswatch/settings/configure-pairs/features/watchlist.md)
* [Ratings](https://wiki.crosswatch.app/crosswatch/settings/configure-pairs/features/ratings.md)
* [History](https://wiki.crosswatch.app/crosswatch/settings/configure-pairs/features/history.md)
* [Progress](https://wiki.crosswatch.app/crosswatch/settings/configure-pairs/features/progress.md)

### Syncing multiple media server users

For a pair between supported media servers, open **Providers** and enable **Identities**. Select identities on both connection instances first, then check and save the links in the pair. This card is not available for tracker destinations. See [Multiple media server users](https://wiki.crosswatch.app/crosswatch/settings/connections/media-servers/multiple-media-server-users.md).

### Details by topic

* Safety switches and guardrails: [Global settings](https://wiki.crosswatch.app/crosswatch/settings/configure-pairs/global-settings.md)
* Review and apply a configured pair safely: [Interactive Sync](https://wiki.crosswatch.app/crosswatch/main-dashboard/interactive-sync.md)
* Pair-scoped provider behavior: [Provider settings](https://wiki.crosswatch.app/crosswatch/settings/configure-pairs/provider-settings.md)
* Pair-only library scoping: [Pair-level Whitelisting](https://wiki.crosswatch.app/crosswatch/settings/configure-pairs/provider-settings/pair-level-whitelisting.md)
* AniList-specific pair controls: [AniList pair options](https://wiki.crosswatch.app/crosswatch/settings/configure-pairs/anilist-pair-options.md)
* Watchlist controls and Jellyfin/Emby mode: [Watchlist](https://wiki.crosswatch.app/crosswatch/settings/configure-pairs/features/watchlist.md)
* Ratings scope and backfill window: [Ratings](https://wiki.crosswatch.app/crosswatch/settings/configure-pairs/features/ratings.md)
* History behavior and safety limitations: [History](https://wiki.crosswatch.app/crosswatch/settings/configure-pairs/features/history.md)
* Resume position syncing (compatible provider pairs): [Progress](https://wiki.crosswatch.app/crosswatch/settings/configure-pairs/features/progress.md)
* Runtime additions, removals, and conflicts: [Synchronization policies](https://wiki.crosswatch.app/getting-started/support-matrix/pair-synchronization/synchronization-policies.md)

### When a section is disabled

Dependent controls lock.

This prevents accidental changes.

### Related topics

* [Pair synchronization](https://wiki.crosswatch.app/getting-started/support-matrix/pair-synchronization.md)
* [Best practices](https://wiki.crosswatch.app/getting-started/best-practices.md)

### Pair actions on smaller screens

If a pair card has limited space, open **More pair actions** for actions such as **Latest logs**, **Reset pair**, **Edit**, and **Delete**. Available actions still depend on your permissions and the pair state.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://wiki.crosswatch.app/crosswatch/settings/configure-pairs.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
