Skip to main content

Basic administration guide

Dashboard​

Use the admin dashboard as your starting point: review service health, pending work, notices, and account activity before changing configuration.

Users​

Create or invite users, validate their identity, and use test accounts before applying a new flow to real customers. Keep admin access limited to trusted people.

Invitations and subscriptions​

Review invitation expiry, access duration, and linked services before sending an invitation. Track active, renewed, cancelled, expired, and pending memberships without losing prior-period history.

Requests​

Choose a clear request source—Seerr/Jellyseerr or native Requests—and test it end to end. Avoid mixed flows unless ownership and synchronisation are understood.

Downloads, library, and subtitles​

Enable only the services you use. Validate queue ownership, library visibility, subtitle status, and Customer Portal wording with a test customer.

Activity and observability​

Use service diagnostics and logs to distinguish an application failure from an external-service, network, or credentials failure.

Incidents and support​

Keep customer-facing support clear and non-technical. Never ask users to send passwords, API tokens, or sensitive data through support.

Services and settings​

Store integration credentials through Settings > Services where possible, keep secrets outside Git, and preserve APP_SETTINGS_ENCRYPTION_KEY.

Before opening to users​

  • Verify APP_BASE_URL, HTTPS, and secure cookies.
  • Test admin and Customer Portal access.
  • Check backups and restore procedures.
  • Review every enabled integration.
  • Remove fake or test data that should not be public.