Operations
These terms cover running Scryer for other people and keeping it healthy. Each links to the guide that goes deeper.
Permissions
Section titled “Permissions”Permissions decide what an account can see and do. App permissions unlock instance-wide settings such as users, system settings, and catalog settings. Library permissions are granted per library: view, manage titles, resolve imports, manage library, request, and auto-approve requests.
Navigation is permission-aware, so two users on the same server see different sidebars. The full tables are in Authentication.
Notification Channel
Section titled “Notification Channel”A notification channel is a provider instance from a notification plugin, subscribed to Scryer events such as import complete, upgrade, or health warning. Configure channels in Settings → Notifications.
The Plex, Jellyfin, and Emby channels are special: instead of messaging a person they send the media server a targeted refresh for the path that changed.
Media Server Connection
Section titled “Media Server Connection”A media server connection links Scryer to a Plex, Jellyfin, or Emby server for identity: people sign in with that account, link it to an existing Scryer user, or are auto-added with default permissions. Configure connections in Settings → Media Servers.
A connection is not a notification channel. It verifies who someone is. It does not refresh libraries. See Media Servers.
Media Request
Section titled “Media Request”A media request is a user’s ask for a title in a library they hold the request permission on. Requests wait in an approval queue unless the requester also holds autoApproveRequests for that library. See Media Requests.
Subtitle Provider
Section titled “Subtitle Provider”A subtitle provider is a provider instance from a subtitle plugin, scoped to the content types it serves. Scryer fetches subtitles during import and keeps looking for monitored titles. Configure providers in Settings → Subtitles. See Scryer vs. Bazarr.
Post-Processing Script
Section titled “Post-Processing Script”A post-processing script runs after an import lands, with the file path and title context passed as environment variables. Scripts are scoped per facet and run blocking or fire-and-forget. See Post-Processing.
Recycle Bin
Section titled “Recycle Bin”The recycle bin holds files Scryer removes or replaces so they can be restored until retention expires. It is off by default. See Recycle Bin.
A job is background work: RSS checks, scheduled searches, metadata refreshes, recycle bin cleanup, provider catalog refresh, and library scans. System → Jobs shows what is running and when each last ran. Jobs require manageSystemSettings to view.
Library Scan
Section titled “Library Scan”A library scan walks a library’s roots and reconciles files on disk with the catalog: matching new files to titles, noticing removed ones, and updating quality state. Run one after adding an existing folder as a root or after changing files outside Scryer. Scans read local state only. They do not touch indexers or download clients.