Browse documentation
DocsUse Lumina

Connections

Metadata, requests, and supporting services without guesswork.

Add metadata

Open Manage Server → Connections → Metadata. Paste a TMDB v3 key or v4 read token, choose a language, and use Test. Local NFO values and manual edits retain priority. Resolve uncertain matches under Unmatched → Fix match.

Connect your existing services

ServiceSetup / behavior
Sonarr / RadarrSet address, write-only API key, and remote-to-local path mappings. Inventory observation runs independently of member requests.
LidarrTest the connection; choose root folder, quality profile, metadata profile, and path mappings. Album acquisition requires owner approval.
ProwlarrRead-only observations. Indexer configuration stays upstream.
qBittorrent / NZBGetRead-only transfer observations. Bind the arr server and exact configured download-client name to correlate jobs.

Use Manage Server → Connections → Integrations for inventory, queue, history, and health. A failed poll keeps the last successful snapshot and marks it stale.

Make requests playable

  1. Enable the integration and test the connection.
  2. Map upstream paths to a registered, enabled external root.
  3. Complete that root’s first owner import.
  4. Set member request rules under Household → Request rules.

A request becomes playable only when a normal import registers a file visible to the member. If an acquisition outcome is uncertain, use Reconcile and inspect upstream before retrying; Lumina does not blindly resend it.

Send household email

Configure SMTP in Manage Server → Connections → Email, then choose Send test email. Invitations, request updates, and security notices use the configured public HTTPS address.

Applies to Lumina 0.4.0. Source: operator guide

Find your next step.

Type to search all documentation.