# Pair-level Whitelisting

Pair-level whitelisting limits libraries for **one pair**.

Use it when you need exceptions:

* one pair should ignore “Kids” or “Anime”
* one pair should backfill only a small library

For the full picture (server-level + pair-level), use:\
[Library Whitelisting](/crosswatch/library-whitelisting.md).

### What pair-level whitelisting affects

Pair-level whitelisting is applied inside the pair settings.

Typical features:

* **History**
* **Ratings**

It does not change other pairs.

{% hint style="info" %}
Scrobble filtering is **server-level only**.\
Scrobbling is event-driven (Watcher/Webhooks), not pair-driven.
{% endhint %}

### Configure pair-level whitelisting

1. Go to **Pairs**.
2. Edit a pair (example: Plex → SIMKL).
3. Open **Provider settings** (Plex/Jellyfin/Emby).
4. Click **Load Libraries** if needed.
5. Select libraries for **History** and/or **Ratings**.
6. Save the pair.

### How it interacts with server-level whitelisting

Think of it like:

* Server-level = maximum allowed scope
* Pair-level = per-pair subset

### Troubleshooting

**Insights dashboard shows too much**

Dashboards are based on orchestrator state.\
Prefer server-level whitelisting for global scoping.

**Pair-level selection doesn’t apply**

* Confirm the pair provider section has libraries selected for that feature.
* Re-run the pair once to refresh state.

**Reset and allow everything**

* Clear libraries in the pair for the feature.
* Save and re-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/configure-pairs/provider-settings/pair-level-whitelisting.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.