Skip to main content

Users, roles, and memberships

Basic concepts​

PlexSub separates administration, customer access, subscriptions, integrations, and the support portal. A user can exist in PlexSub while also being linked to services such as Plex, Jellyfin, Seerr, or payment providers.

  1. Registration or invitation.
  2. Identity and email confirmation.
  3. Access or subscription assignment.
  4. Provisioning in media services.
  5. Normal Customer Portal use.
  6. Renewal, pause, cancellation, or removal.
  7. Access revocation when appropriate.

Invitations​

PlexSub can use native invitation flows and Wizarr. Native invitations are beta, optional, and recommended; Wizarr is beta and depends on Plex.

Relevant variables: WIZARR_URL, WIZARR_API_KEY, WIZARR_EXTERNAL_URL, WIZARR_DEFAULT_SERVER_IDS, WIZARR_DEFAULT_LIBRARY_IDS, WIZARR_INVITATION_EXPIRES_IN_DAYS, WIZARR_ACCESS_DURATION, WIZARR_ALLOW_DOWNLOADS, WIZARR_ALLOW_LIVE_TV, WIZARR_ALLOW_MOBILE_UPLOADS, and WIZARR_UNLIMITED_ACCESS.

Roles and permissions​

The public documentation does not contain a complete role-permission matrix. Use these rules:

  • Give administration permissions only to trusted people.
  • Use customer accounts for portal access.
  • Never share admin accounts.
  • Review permissions before enabling payment providers, invitations, or automated actions.

Memberships and renewals​

The subscriptions module reflects access, renewals, and operational status. A previous month must retain its history when a user renews later; each period keeps its own status.

Administrators should be able to review active, renewed, cancelled, expired, and—where applicable—pending payment or review states.

Removal or cancellation​

Before removing a user:

  1. Review the subscription or access agreement.
  2. Check recent payments.
  3. Check linked services.
  4. Revoke access only when appropriate.
  5. Retain the operational history you need.
  6. Do not delete external accounts when you only need to remove access.

Good practices​

  • Use test users to validate invitations and removals.
  • Document which provider is authoritative in every flow.
  • Review logs, subscription status, and diagnostics instead of relying on memory.
  • Do not put screenshots containing email addresses, tokens, or private data in public documentation.