> 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/features/collection.md).

# Collection

Sync a source library or tracker collection into a target collection.

Sync items from a source library or tracker collection into a target collection.

Collections are **one-way only**. Enabling Collection locks the pair to **One-way** mode.

For Plex, Emby, Jellyfin, and Kodi, Collection means items in selected media libraries. It does not mean named media-server collections.

#### Basics

| Option     | What it does                                          |
| ---------- | ----------------------------------------------------- |
| **Enable** | Turns on Collection sync for the pair.                |
| **Add**    | Adds source items missing from the target collection. |
| **Remove** | Removes target items removed from the source.         |

#### Collection scope

| Option            | What it does                                  |
| ----------------- | --------------------------------------------- |
| **All available** | Sync every media type both providers support. |
| **Movies**        | Sync movies.                                  |
| **Shows**         | Sync shows.                                   |
| **Seasons**       | Sync seasons.                                 |
| **Episodes**      | Sync episodes.                                |

CrossWatch shows only media types supported by both providers.

Types a provider does not support are greyed out.

#### How it works

The first run creates the Collection baseline.

Later runs are delta-based. CrossWatch processes only changes since the prior state.

Where supported, CrossWatch preserves the original collection added date.

#### Supported directions

Collection sources include:

* Plex
* Emby
* Jellyfin
* Kodi
* Trakt
* MDBList
* CrossWatch
* PunchPlay
* Floppy
* Scrob

Collection targets include:

* Trakt
* MDBList
* CrossWatch
* PunchPlay
* Floppy
* Scrob

Media servers are source-only for Collection sync.

#### What Collection does not have

Collection has no **Only items in destination library** option.

That option filters what is written to a media server. For Collection, a media server is never the target, so there is nothing to filter.

It exists for History, Ratings, Progress and Watchlist.

Collection also has no Advanced settings in the pair.

#### Recommended setup

Start with **Add / Update** enabled and **Remove** disabled.

Check the first sync result. Enable **Remove** only when target removals should follow source deletions.

#### Related

* Overview of feature choices and patterns: [Features](/crosswatch/settings/configure-pairs/features.md)
* Pair-level feature toggles and safety: [Configure Pairs](/crosswatch/settings/configure-pairs.md)


---

# 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/features/collection.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.