Media Servers

Scryer talks to media servers in two separate ways. Configure both, or just the one you need.

	Connection	Notification
Purpose	Let people sign in to Scryer with their Plex, Jellyfin, or Emby account, and link accounts	Tell the media server to rescan after Scryer imports, upgrades, renames, or deletes a file
Where	Settings → Media Servers	Settings → Notifications, using the plex, jellyfin, or emby plugin
Direction	Media server verifies identities for Scryer	Scryer pushes refreshes to the media server
Permission	manageSystemSettings	manageSystemSettings

The two do not depend on each other. A connection does not refresh libraries, and a notification does not let anyone sign in.

Connections

A connection stores a provider (Plex, Jellyfin, or Emby), a display name, a base URL Scryer uses to reach the server, and an optional external URL used for “watch in media server” links in the UI.

Authentication differs by provider:

• Plex authenticates with Plex PIN sign-in, then you pick the server. Scryer stores the server’s machine id so only users of that server are accepted.
• Jellyfin and Emby connect with an API key. Paste one under Setup via API key, or enter an admin username and password and let Scryer create the key for you. Those credentials are used once, in memory, to sign in to the server and mint a Scryer API key. Only the key is stored. The account must be an administrator, and if the server does not return a usable key, paste one manually. Emby can also accept Emby Connect sign-in.

Each connection has three switches:

• Login enabled lets media server users sign in to Scryer. Form login must be enabled first, see Authentication.
• Linking enabled lets an existing Scryer user attach their media server account from their profile.
• Auto-add new verified users creates a Scryer user the first time an unknown media server account signs in, with the connection’s default app permissions and default library grants.

Without auto-add, an admin creates an external account invite that pairs a chosen Scryer user with a media server account. The external account then moves from pending claim to active once that person signs in.

Path mappings on a connection translate media server paths to Scryer paths, saved as server path => Scryer path. Set them when the media server sees the same files at a different mount point.

Security settings can require MFA for Jellyfin or Emby logins. Plex sign-in already carries Plex’s own verification.

Library Refresh Notifications

The plex, jellyfin, and emby notification plugins send targeted refreshes: they tell the server which path changed rather than triggering a full library scan. They fire on import complete, upgrade, rename, and file deleted.

Each instance needs:

• Base URL and API key (Plex token for Plex).
• Path mappings in SOURCE => DESTINATION form, one per line, when Scryer and the media server mount the library at different paths. The longest matching prefix wins.

Install the plugin from Settings → Plugins first, then add the instance under Settings → Notifications and pick the events. Send a test notification before relying on it.

Choosing What To Configure

• Household with Plex or Jellyfin accounts already: set up a connection with login and auto-add, and a notification so new imports appear immediately.
• Single admin: skip the connection and add only the notification.
• Requests from media server users: a connection plus the request library permission in the connection’s default grants. See Media Requests.

Related

• Authentication covers form login, MFA requirements, and permissions that media server users receive.
• Plugins explains installing the notification plugins.
• Seerr comparison shows how this replaces a separate request portal.