Library Whitelisting

Limit which Plex/Jellyfin/Emby libraries CrossWatch reads, writes, or scrobbles.

Whitelisting limits which libraries CrossWatch reads and writes. It also controls which libraries generate scrobbles.

Use it to:

• speed up runs

• reduce API calls

• avoid syncing noise libraries (music, photos, live TV)

• block scrobbling from specific libraries

Two whitelist layers

1. Server-level (provider settings) Applies to every pair using that provider.

2. Pair-level (pair settings) Applies only to one pair.

If you do not configure whitelisting, CrossWatch uses all visible libraries.

Server-level filtering is used by the orchestrator. Pair-level filtering is applied by adapters.

Some UI dashboards use orchestrator state. If you rely heavily on pair-level filtering, dashboards can look too big.

Server-level whitelisting (recommended)

Available for Plex, Jellyfin, and Emby under Settings → Authentication.

You can whitelist per feature:

• History (H)

• Ratings (R)

• Scrobble (S)

Scrobble whitelist

Scrobble whitelisting controls which libraries generate real-time scrobbles:

• Watchers

• Webhooks

If scrobble libraries are empty, CrossWatch scrobbles everything.

Set server-level whitelists

1

Open provider whitelisting

Go to Settings → Authentication.

Open Plex, Jellyfin, or Emby.

Open Whitelisting.

2

Load libraries

Click Load Libraries.

3

Select H / R / S

Select libraries under:

• H (History)

• R (Ratings)

• S (Scrobble)

4

Save

Click Save.

Emby and Jellyfin expose "Views".

CrossWatch resolves items to the correct view first.

Pair-level whitelisting (per pair)

Pair-level whitelisting lives in the pair editor. It is used mainly for History and Ratings.

Pair-level selection:

• overrides the pair's scope

• does not affect other pairs

Scrobble whitelisting is server-level only. Scrobbling is event-driven, not pair-driven.

Set pair-level whitelists

1

Open a pair

Go to Pairs.

Edit a pair.

2

Load libraries

Open the provider settings (Plex/Jellyfin/Emby).

Click Load Libraries if needed.

3

Select libraries

Select libraries for History and/or Ratings.

4

Save

Save the pair.

How the two layers interact

Think of it like:

• Server-level = maximum allowed scope

• Pair-level = per-pair subset

Troubleshooting

Insights dashboard shows too much data

• Dashboards are based on orchestrator state.

• Prefer server-level whitelisting for global scoping.

• Keep pair-level whitelisting for exceptions.

Pair-level whitelisting doesn’t work

• Confirm the pair provider section has libraries selected for the feature.

• Re-run the pair once to refresh state.

Scrobble ignores my library selection

• Scrobble filtering is server-level only.

• Verify S libraries are selected in provider whitelisting.

Reset and allow everything

• Clear selected libraries at server-level (H/R/S).

• Clear selected libraries in the pair.

• Save and re-run.