Differences

This shows you the differences between two versions of the page.

--- ux:overseerr [2025/12/16 00:09] – created - external edit 127.0.0.1
+++ ux:overseerr [2025/12/20 18:56] (current) – privacyl0st
@@ Line 1: / Line 1: @@
-= Overseerr =
+====== Overseerr – General Configuration Guide ======
-Covers Overseerr setup, request management, and user permissions.
+**Purpose:**
+Overseerr is a user-facing media request system that complements your automation ecosystem. Running on its own **Request Server VM**, it allows users to submit content requests, track request statuses, and communicate directly with your media server environment without needing admin access. This ensures a **self-service, low-touch system** that keeps your library growing efficiently and your automation stack flowing smoothly.
+---
+===== Key Concepts =====
+  * **Plex Integration** – Overseerr connects to Plex to check your existing library, validate requests, and update media availability once content is processed. This prevents duplicate requests and ensures accurate request fulfillment.
+  * **Email Notifications** – Overseerr can send emails to users when requests are approved, denied, or completed, keeping them informed without admin intervention.
+  * **End-User Self-Service** – By providing a web interface for content requests, Overseerr reduces the number of ad-hoc requests sent directly to admins and improves overall system usability.
+---
+===== General Configuration Steps =====
+=== 1. Initial Setup ===
+  * Install Overseerr on the dedicated Request Server VM.
+  * Ensure network access to your Plex Media Server VM for library queries.
+  * Assign a static port or hostname (default: //**<vm-ip>:5055**//) so users can reliably access the interface.
+  * Enable authentication; you can integrate with Plex accounts for seamless user management.
+=== 2. Plex Integration ===
+  * Connect Overseerr to your Plex server using a **Plex Token**.
+  * Verify that Overseerr can read your libraries and identify which content is already available.
+  * Configure library access permissions per user or group as needed.
+  * Once integrated, Overseerr will automatically prevent duplicate requests for content already in your library.
+=== 3. Email Notifications ===
+  * Configure the SMTP server details (host, port, encryption, credentials).
+  * Set default “From” address for outgoing emails.
+  * Enable notifications for request creation, approval, denial, and fulfillment.
+  * Optionally, allow users to manage their own notification preferences to reduce email clutter.
+  * Test notifications to confirm email deliverability.
+=== 4. User-Facing Features ===
+  * **Search and Request** – Users can search your library and supported media databases (TMDb, TVDb, etc.) to request movies or TV shows.
+  * **Request Status Tracking** – Users can see the current status of their requests: pending, approved, denied, or completed.
+  * **Notifications & Alerts** – Email or in-app notifications keep users informed without requiring admin intervention.
+  * **Audit & Logs** – Admins can review all requests, approve/deny them, and track fulfillment to ensure smooth operation.
+---
+===== How Overseerr Complements the Automation Stack =====
+| Function | Role in the Ecosystem |
+| Plex | Provides library visibility to prevent duplicate requests. |
+| Sonarr / Radarr | Overseerr triggers or queues requests that feed into automated acquisition. |
+| Automation VM | Overseerr itself does not process media but coordinates requests with your automation tools. |
+| Users | Provides a clean, controlled, self-service request interface, reducing admin workload. |
+In short, Overseerr acts as the **front door for content requests**, while Prowlarr, Jackett, and Unmanic handle backend processing and delivery. The system ensures **efficient, self-managed operation**, improving library growth, user satisfaction, and workflow reliability.
+---
+===== Best Practices =====
+  * Use Plex authentication to manage user access and reduce account proliferation.
+  * Configure email notifications for transparency, but avoid spamming by allowing users to set preferences.
+  * Regularly monitor requests to ensure the automation stack is fulfilling them correctly.
+  * Keep Overseerr updated to maintain compatibility with Plex and media databases.
+---
+This guide introduces Overseerr in the context of your automated media environment. Detailed per-user configuration, advanced permission management, and troubleshooting should be referenced in Overseerr’s official documentation as needed.