# What do you need?

CrossWatch (CW) supports two workflows. Pick one path first.

If you’re unsure, start with **syncing**.

### Path 1: Syncing (periodic)

Use this to align watchlists, history, ratings, and progress. Start one-way. Add two-way later.

Progress (resume position) is media-server-only (Plex/Emby/Jellyfin).

Start here: [Syncing](/getting-started/first-time-setup/what-do-you-need/syncing.md)

You will set up:

* Authentication providers
* Metadata (recommended)
* Pairs

### Path 2: Scrobbling (real-time)

Use this to push plays while you watch. Prefer **Watcher**.

Start here: [Webhook or Watcher](/getting-started/first-time-setup/what-do-you-need/webhook-or-watcher.md)

You will set up:

* Authentication providers
* Metadata (recommended)
* Scrobbler (Watcher or Webhook)

{% hint style="warning" %}
Legacy webhooks are deprecated. Use **Watcher** unless you have a specific reason not to.
{% endhint %}

{% hint style="info" %}
Many setups use both. Syncing is best for backfills and alignment. Scrobbling is best for new plays as they happen.
{% endhint %}

### Related topics

#### Quick setup

* [First-time setup](/getting-started/first-time-setup.md) — recommended order in the UI
* [Settings](/crosswatch/navigation/settings.md) — where everything lives

#### Connect providers

* [Providers](/crosswatch/providers.md) — what CW supports
* [Authentication](/crosswatch/providers/authentication.md) — connect services
* [Metadata](/crosswatch/providers/metadata.md) — why TMDb matters

#### Build safe pairs

* [Configure Pairs](/crosswatch/configure-pairs.md) — dry run, guards, and feature toggles
* [Scheduling](/crosswatch/scheduling.md) — run pairs on a cadence
* [Whitelisting](/crosswatch/library-whitelisting.md) — limit which libraries are touched
* [Pair-level Whitelisting](/crosswatch/configure-pairs/provider-settings/pair-level-whitelisting.md) — limit libraries for one pair

#### Enable scrobbling

* [Webhook or Watcher](/getting-started/first-time-setup/what-do-you-need/webhook-or-watcher.md) — pick a mode
* [Watcher](/crosswatch/scrobble/watcher.md) — recommended setup

#### Fix issues fast

* [Analyzer](/crosswatch/tools/analyzer.md) — find missing peers and mismatches
* [Editor](/crosswatch/tools/editor.md) — overrides, blocks, and cleanup
* [FAQ](/crosswatch/faq.md) — common questions

#### Safety reads

* [Best practices](/getting-started/best-practices.md) — safer defaults
* [Tracker to Media Server](/related-information/tracker-to-media-server.md) — why it’s risky
* [Media Server to Media Server](/related-information/media-server-to-media-server.md) — why it’s fragile

#### Operations

* [Docker setup](/getting-started/docker-setup.md) — installation and persistent config
* [Install scripts](/related-information/community/install-scripts.md) — community-maintained platform wrappers
* [HTTPS/TLS](/crosswatch/navigation/ui-settings/user-interface/https-tls.md) — secure the UI
* [Maintenance](/crosswatch/maintenance.md) — logging and cleanup

### Next steps

* For syncing: [Syncing](/getting-started/first-time-setup/what-do-you-need/syncing.md)
* For scrobbling: [Webhook or Watcher](/getting-started/first-time-setup/what-do-you-need/webhook-or-watcher.md)
* If you’re brand new: [First-time setup](/getting-started/first-time-setup.md)

### Summary

Use **syncing** for periodic alignment (watchlists/history/ratings/progress).

Use **scrobbling** for real-time playback progress and new plays.

Most users end up using both. Start with one path.


---

# 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/getting-started/first-time-setup/what-do-you-need.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.