Skip to main content

Customer Portal

The Customer Portal is the area your end users see. It should show only useful information that matches the active services.

What a user can see​

Depending on configuration, users can see:

  • Account status.
  • Subscription or access.
  • Downloads.
  • Requests.
  • Notices.
  • Support.
  • Activity or usage.
  • Playback history when an analytics provider is available.
  • Discover preferences when native Requests are enabled.
  • Help articles when the Knowledge Base is enabled.

Home​

The home page summarises the user's primary status. It should make clear whether access is working or whether action is needed.

Subscription​

Shows access or billing status where applicable.

When a billing provider is paused, PlexSub should avoid misleading information. The displayed status must depend on the active configuration and available data.

Downloads​

Downloads depend on qBittorrent, Transmission, Deluge, or another download provider. When the service is disabled, its section should not appear functional.

Requests​

Requests can depend on Seerr, Overseerr, Jellyseerr, or native Requests.

With native Requests, users can browse the Discover catalogue according to the installation configuration. When available, they can save metadata-language, original-language, and region preferences.

Administrators can enable or disable public surfaces such as community activity or recently added content. These views must expose only safe, customer-facing data.

Notices​

Use notices to communicate important information. Avoid long or technical wording.

Support​

Support lets users ask for help and review incidents.

When the Knowledge Base is active, support can include searchable articles and guides. It must not be used to send passwords, tokens, or other sensitive data.

Account and security​

Users should be able to review basic account data and sign out.

Mobile and desktop​

The portal must be usable from mobile and desktop:

  • No clipped text.
  • No overlapping buttons.
  • No irrelevant sections when a service is disabled.
  • Clear states when an integration is not configured.

Good practices​

  • Review the portal with a test user.
  • Confirm that every section adds value.
  • Hide anything that depends on paused services.
  • Use clear wording for non-technical users.
  • Do not expose internal moderation data, tokens, private emails, or provider payloads.

Maintainerr deletion extensions​

When Maintainerr manages upcoming deletions, the portal can show notices and extension requests if the installation enables them.