DiscordDirect integration
Jellyseerr. In its proper role.
Jellyseerr connects to PlexSub as a direct integration, adding requests capabilities without taking over the provider's own responsibilities.
HOW IT FITS
One connection with a specific role.
PlexSub relates services by the capability they contribute to an operator-configured flow, not simply by brand.
- What it contributes
- Jellyseerr contributes requests context within its configured requests role.
- Who configures it
- The person administering the PlexSub instance.
- What members see
- Only the status and options enabled by the operator for each journey.
JOURNEY
From provider to useful context.
Available information depends on the configuration and actual capabilities of each connected service.
- 01
Configure
The operator configures Jellyseerr and the capabilities required by the instance.
- 02
Relate
PlexSub relates the available requests signals to the relevant member or operational context.
- 03
Present
Only enabled status and actions appear in the corresponding administration or member journey.
ECOSYSTEM
Relationships within the flow.
Includes direct relationships, alternatives and contextual options. Each instance decides which ones to enable.
Direct
Capabilities that participate explicitly in this journey.
Media servers
Configurable servers retain their own identities, permissions and internal administration.
Alternatives
Journeys that can cover the same point in the flow.
SCOPE AND BOUNDARIES
Connect what you need without replacing everything.
Jellyseerr retains its own configuration, permissions, availability and provider-specific responsibilities.
Use the PlexSub documentation to prepare a connection suited to your environment.