-
Notifications
You must be signed in to change notification settings - Fork 1
Account Linking
Adam Glover edited this page Aug 18, 2026
·
1 revision
Linking is the core idea of VaultRequestrr: every request is submitted to Seerr as the requester's own Seerr user, so their per-user quotas and permissions apply.
- A user runs
/movie <title>or/tv <title>. - The bot searches Seerr and shows the results to pick from (TV adds a season picker).
- On the user's first request, a popup asks for their Plex username/email.
- It must match an existing Seerr user — if their account hasn't been imported from Plex yet, they should log into Seerr once first.
- The link is saved (SQLite) and written back into Seerr's notification settings, so it's also visible in the Seerr UI.
- The request is submitted with that user's
userId, so Seerr applies their quota/permissions.
From then on, every request, issue, and invite from that Discord user is attributed to their Seerr account automatically.
- Users can check their link with
/linkstatusand remove it with/unlink(they'll be asked again on the next request). - Admins can unlink or remap any user on the Admin Dashboard Links page, and set per-user Plex Invites caps there.
Set REQUIRE_LINKING=false to let users request without linking. Unattributed requests then fall back to DEFAULT_SEERR_USER_ID — a single shared Seerr user, which means shared quota. See Configuration.
"No Seerr user found" on link — the Plex username/email must match an existing Seerr user. Have the user sign into Seerr once with Plex so their account is imported, then retry.
More in Troubleshooting and FAQ.
VaultRequestrr · Report a bug · MIT licensed