PlexSub is under active development. Features and compatibility may evolve before version 1.0.
EspañolDiscord

NATIVE CAPABILITY

Native requests. In context.

Organise requests without removing members from their community context.

A first-party journey for recording requests, applying rules and providing understandable tracking.

DocumentationParticipate in the beta

ROLE IN THE SYSTEM

First-party, complementary and bounded.

A first-party journey for recording requests, applying rules and providing understandable tracking.

First-party
Administration. Brings criteria, permissions and operational tracking into the administration console.Members. Lets members request content and review its status from the portal.
Complements
Can be the primary journey or coexist with Seerr, Overseerr and Jellyseerr as configurable alternatives.
Does not replace
Its scope depends on the services and rules enabled by the instance.

JOURNEY

A common path and an honest outcome.

Alternatives are not presented as mandatory consecutive steps.

  1. 01

    Request

    A member selects content.

  2. 02

    Decision

    PlexSub applies permissions and rules.

  3. 03

    Delivery

    One configured provider receives the approved request.

ECOSYSTEM

Relationships within the flow.

Every relationship retains its type, explanation and navigable destination.

Direct

Capabilities that participate explicitly in this journey.

Media servers

Configurable servers retain their own identities, permissions and internal administration.

PlexJellyfinEmby
RadarrRadarr contributes as a direct relationship in this flow.SonarrSonarr contributes as a direct relationship in this flow.LidarrLidarr contributes as a direct relationship in this flow.

Alternatives

Journeys that can cover the same point in the flow.

SeerrSeerr contributes as a alternatives relationship in this flow.
ContextualRelated signals that add operational context without becoming dependencies.7 relationships

Notifications

Configurable channels deliver notices while every destination keeps its own link and availability.

SMTPWeb PushDiscordTelegramAppriseNotifiarrWebhooks

DEMO VIEW

A visual reference using fictional data.

The image shows a demo instance and does not extend the functional scope described on this page.

Native request queue with status and moderation actions
Demo instance with fictional data.

FREQUENTLY ASKED QUESTIONS

Before enabling it.

Do I need Seerr?

No. The native module can be the primary request journey.

Can I use both?

Yes, when the instance clearly defines what each journey is for.