feat: Overseerr to Jellyseerr migration (#2019)

* feat: add Overseerr migration

* refactor: rename to Seerr

* refactor: more rename to Seerr

* feat: update the value of the MediaStatus.DELETED enum

* fix: add more details in migration logs

* fix: replace .update by .save for TypeORM hooks

* fix: add fake migration to skip the duplicated UpdateWebPush migration

* fix: rewrite the AddUserAvatarCacheFields migration for Overseerr merge

* fix: replace jellyseerr migrations with a dedicated one for overseerr

* fix: update overseerr migration

* fix: update overseerr migration

* fix: remove irrelevant changes

* fix: typos

* docs: update jsdoc comment

* docs: update seerr description

* docs: fix the contributing.md link

* fix: remove unwanterd change on postgres dev datasource

* docs: add latest tag to docker image

* fix: migrate old deleted status for 4k media

* fix: update Seerr version check

docs/using-seerr/_category_.json

@@ -0,0 +1,9 @@
+{
+  "label": "Using Seerr",
+  "position": 2,
+  "link": {
+    "type": "generated-index",
+    "title": "Using Seerr",
+    "description": "Learn how to use Seerr"
+  }
+}

docs/using-seerr/backups.md

@@ -0,0 +1,93 @@
+---
+title: Backups
+description: Understand which data you should back up.
+sidebar_position: 4
+---
+
+# Which data does Seerr save and where?
+
+## Settings  
+
+All configurations from the **Settings** panel in the Seerr web UI are saved, including integrations with Radarr, Sonarr, Jellyfin, Plex, and notification settings.  
+These settings are stored in the `settings.json` file located in the Seerr data folder.
+
+## User Data  
+
+Apart from the settings, all other data—including user accounts, media requests, blacklist etc. are stored in the database (either SQLite or PostgreSQL).
+
+# Backup
+
+### SQLite
+
+If your backup system uses filesystem snapshots (such as Kubernetes with Volsync), you can directly back up the Seerr data folder.  
+Otherwise, you need to stop the Seerr application and back up the `config` folder.
+
+For advanced users, it's possible to back up the database without stopping the application by using the [SQLite CLI](https://www.sqlite.org/download.html). Run the following command to create a backup:  
+
+```bash
+sqlite3 db/db.sqlite3 ".backup '/tmp/seerr_db.sqlite3.bak'"
+```  
+
+Then, copy the `/tmp/seerr_dump.sqlite3.bak` file to your desired backup location.
+
+### PostgreSQL
+
+You can back up the `config` folder and dump the PostgreSQL database without stopping the Seerr application.
+
+Install [postgresql-client](https://www.postgresql.org/download/) and run the following command to create a backup (just replace the placeholders):
+
+:::info
+Depending on how your PostgreSQL instance is configured, you may need to add these options to the command below.
+
+  -h, --host=HOSTNAME      database server host or socket directory
+
+  -p, --port=PORT          database server port number
+:::
+
+```bash
+pg_dump -U <database_user> -d <database_name> -f /tmp/seerr_db.sql
+```
+
+# Restore
+
+### SQLite
+
+After restoring your `db/db.sqlite3` file and, optionally, the `settings.json` file, the `config` folder structure should look like this:
+
+```
+.
+├── cache            <-- Optional
+├── db
+│   └── db.sqlite3
+├── logs             <-- Optional
+└── settings.json    <-- Optional (required if you want to avoid reconfiguring Seerr)
+```
+
+Once the files are restored, start the Seerr application.
+
+### PostgreSQL
+
+Install the [PostgreSQL client](https://www.postgresql.org/download/) and restore the PostgreSQL database using the following command (replace the placeholders accordingly):
+
+:::info
+Depending on how your PostgreSQL instance is configured, you may need to add these options to the command below.
+
+  -h, --host=HOSTNAME      database server host or socket directory
+
+  -p, --port=PORT          database server port number
+:::
+
+```bash
+pg_restore -U <database_user> -d <database_name> /tmp/seerr_db.sql
+```
+
+Optionally, restore the `settings.json` file. The `config` folder structure should look like this:
+
+```
+.
+├── cache            <-- Optional
+├── logs             <-- Optional
+└── settings.json    <-- Optional (required if you want to avoid reconfiguring Seerr)
+```
+
+Once the database and files are restored, start the Seerr application.

docs/using-seerr/notifications/discord.md

@@ -0,0 +1,31 @@
+---
+title: Discord
+description: Configure Discord notifications.
+sidebar_position: 3
+---
+
+# Discord
+
+The Discord notification agent enables you to post notifications to a channel in a server you manage.
+
+:::info
+Users can optionally opt-in to being mentioned in Discord notifications by configuring their [Discord user ID](https://support.discord.com/hc/en-us/articles/206346498-Where-can-I-find-my-User-Server-Message-ID-) in their user settings.
+:::
+
+## Configuration
+
+### Webhook URL
+
+You can find the webhook URL in the Discord application, at **Server Settings → Integrations → Webhooks**.
+
+### Notification Role ID (optional)
+
+If a role ID is specified, it will be included in the webhook message. See [Discord role ID](https://support.discord.com/hc/en-us/articles/206346498-Where-can-I-find-my-User-Server-Message-ID).
+
+### Bot Username (optional)
+
+If you would like to override the name you configured for your bot in Discord, you may set this value to whatever you like!
+
+### Bot Avatar URL (optional)
+
+Similar to the bot username, you can override the avatar for your bot.

docs/using-seerr/notifications/email.md

@@ -0,0 +1,50 @@
+---
+title: Email
+description: Configure email notifications for your users.
+sidebar_position: 1
+---
+
+# Email
+
+## Configuration
+
+:::info
+If the [Application URL](/using-seerr/settings/general#application-title) setting is configured in **Settings → General**, Seerr will explicitly set the origin server hostname when connecting to the SMTP host.
+:::
+
+### Sender Name (optional)
+
+Configure a friendly name for the email sender (e.g., "Seerr").
+
+### Sender Address
+
+Set this to the email address you would like to appear in the "from" field of the email message.
+
+Depending on your email provider, this may need to be an address you own. For example, Gmail requires this to be your actual email address.
+
+### SMTP Host
+
+Set this to the hostname or IP address of your SMTP server.
+
+### SMTP Port
+
+Set this to a supported port number for your SMTP host. `465` and `587` are commonly used.
+
+### Encryption Method
+
+In most cases, [Use Implicit TLS](https://tools.ietf.org/html/rfc8314) should be selected for port 465, and [Use STARTTLS](https://en.wikipedia.org/wiki/Opportunistic_TLS) if available for port 587. Please refer to your email provider's documentations for details on how to configure this setting.
+
+The default value for this setting is **Use STARTTLS if available**.
+
+### SMTP Username & Password
+
+:::info
+If your account has two-factor authentication enabled, you may need to create an application password instead of using your account password.
+:::
+Configure these values as appropriate to authenticate with your SMTP host.
+
+### PGP Private Key & Password (optional)
+
+Configure these values to enable encrypting and signing of email messages using [OpenPGP](https://www.openpgp.org/). Note that individual users must also have their **PGP public keys** configured in their user settings in order for PGP encryption to be used in messages addressed to them.
+
+When configuring the PGP keys, be sure to keep the entire contents of the key intact. For example, private keys always begin with `-----BEGIN PGP PRIVATE KEY BLOCK-----` and end with `-----END PGP PRIVATE KEY BLOCK-----`.

docs/using-seerr/notifications/gotify.md

@@ -0,0 +1,21 @@
+---
+title: Gotify
+description: Configure Gotify notifications.
+sidebar_position: 5
+---
+
+# Gotify
+
+## Configuration
+
+### Server URL
+
+Set this to the URL of your Gotify server.
+
+### Application Token
+
+Add an application to your Gotify server, and set this field to the generated application token.
+
+:::info
+Please refer to the [Gotify API documentation](https://gotify.net/docs) for more details on configuring these notifications.
+:::

docs/using-seerr/notifications/index.mdx

@@ -0,0 +1,25 @@
+---
+title: Notifications
+description: Configure notifications for your users.
+sidebar_position: 3
+---
+
+# Notifications
+
+## Supported Notification Agents
+
+Seerr currently supports the following notification agents:
+
+import DocCardList from '@theme/DocCardList';
+
+<DocCardList />
+
+## Setting Up Notifications
+
+Simply configure your desired notification agents in **Settings -> Notifications** in the Seerr web UI.
+
+Users can customize their notification preferences in their own user notification settings.
+
+## Requesting New Notification Agents
+
+If we do not currently support your preferred notification agent, feel free to [submit a feature request on GitHub](https://github.com/fallenbagel/jellyseerr/issues). However, please be sure to search first and confirm that there is not already an existing request for the agent!

docs/using-seerr/notifications/ntfy.md

@@ -0,0 +1,29 @@
+---
+title: ntfy.sh
+description: Configure ntfy.sh notifications.
+sidebar_position: 6
+---
+
+# ntfy.sh
+
+## Configuration
+
+### Server Root URL
+
+Set this to the URL of your ntfy.sh server.
+
+### Topic
+
+Set this to the topic you want to send notifications to.
+
+### Username + Password authentication (optional)
+
+Set this to the username and password for your ntfy.sh server.
+
+### Token authentication (optional)
+
+Set this to the token for your ntfy.sh server.
+
+:::info
+Please refer to the [ntfy.sh API documentation](https://docs.ntfy.sh/) for more details on configuring these notifications.
+:::

docs/using-seerr/notifications/pushbullet.md

@@ -0,0 +1,23 @@
+---
+title: Pushbullet
+description: Configure Pushbullet notifications.
+sidebar_position: 7
+---
+
+# Pushbullet
+
+:::info
+Users can optionally configure personal notifications in their user settings.
+
+User notifications are separate from system notifications, and the available notification types are dependent on user permissions.
+:::
+
+## Configuration
+
+### Access Token
+
+[Create an access token](https://www.pushbullet.com/#settings) and set it here to grant Seerr access to the Pushbullet API.
+
+### Channel Tag (optional)
+
+Optionally, [create a channel](https://www.pushbullet.com/my-channel) to allow other users to follow the notification feed using the specified channel tag.

docs/using-seerr/notifications/pushover.md

@@ -0,0 +1,27 @@
+---
+title: Pushover
+description: Configure Pushover notifications.
+sidebar_position: 8
+---
+
+# Pushover
+
+:::info
+Users can optionally configure personal notifications in their user settings.
+
+User notifications are separate from system notifications, and the available notification types are dependent on user permissions.
+:::
+
+## Configuration
+
+### Application/API Token
+
+[Register an application](https://pushover.net/apps/build) and enter the API token in this field. (You can use one of the [official icons in our GitHub repository](https://github.com/fallenbagel/jellyseerr/tree/develop/public) when configuring the application.)
+
+For more details on registering applications or the API token, please see the [Pushover API documentation](https://pushover.net/api#registration).
+
+### User Key
+
+Set this to the user key for your Pushover account. Alternatively, you can set this to a group key to deliver notifications to multiple users.
+
+For more details, please see the [Pushover API documentation](https://pushover.net/api#identifiers).

docs/using-seerr/notifications/slack.md

@@ -0,0 +1,17 @@
+---
+title: Slack
+description: Configure Slack notifications.
+sidebar_position: 9
+---
+
+# Slack
+
+## Configuration
+
+### Webhook URL
+
+Simply [create a webhook](https://my.slack.com/services/new/incoming-webhook/) and enter the URL in this field.
+
+:::info
+Please refer to the [Slack API documentation](https://api.slack.com/messaging/webhooks) for more details on configuring these notifications.
+:::

docs/using-seerr/notifications/telegram.md

@@ -0,0 +1,39 @@
+---
+title: Telegram
+description: Configure Telegram notifications.
+sidebar_position: 10
+---
+
+# Telegram
+
+:::info
+Users can optionally configure personal notifications in their user settings.
+
+User notifications are separate from system notifications, and the available notification types are dependent on user permissions.
+:::
+
+## Configuration
+
+:::info
+In order to configure Telegram notifications, you first need to [create a bot](https://telegram.me/BotFather).
+
+Bots **cannot** initiate conversations with users, so users must have your bot added to a conversation in order to receive notifications.
+:::
+
+### Bot Username (optional)
+
+If this value is configured, users will be able to click a link to start a chat with your bot and configure their own personal notifications.
+
+The bot username should end with `_bot`, and the `@` prefix should be omitted.
+
+### Bot Authentication Token
+
+At the end of the bot creation process, [@BotFather](https://telegram.me/botfather) will provide an authentication token.
+
+### Chat ID
+
+To obtain your chat ID, simply create a new group chat, add [@get_id_bot](https://telegram.me/get_id_bot), and issue the `/my_id` command.
+
+### Send Silently (optional)
+
+Optionally, notifications can be sent silently. Silent notifications send messages without notification sounds.

docs/using-seerr/notifications/webhook.md

@@ -0,0 +1,138 @@
+---
+title: Webhook
+description: Configure webhook notifications.
+sidebar_position: 4
+---
+
+# Webhook
+
+The webhook notification agent enables you to send a custom JSON payload to any endpoint for specific notification events.
+
+## Configuration
+
+### Webhook URL
+
+The URL you would like to post notifications to. Your JSON will be sent as the body of the request.
+
+### Authorization Header (optional)
+
+:::info
+This is typically not needed. Please refer to your webhook provider's documentation for details.
+:::
+
+This value will be sent as an `Authorization` HTTP header.
+
+### JSON Payload
+
+Customize the JSON payload to suit your needs. Seerr provides several [template variables](#template-variables) for use in the payload, which will be replaced with the relevant data when the notifications are triggered.
+
+## Template Variables
+
+### General
+
+| Variable                | Value                                                                                                                               |
+| ----------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
+| `{{notification_type}}` | The type of notification (e.g. `MEDIA_PENDING` or `ISSUE_COMMENT`)                                                                  |
+| `{{event}}`             | A friendly description of the notification event                                                                                    |
+| `{{subject}}`           | The notification subject (typically the media title)                                                                                |
+| `{{message}}`           | The notification message body (the media overview/synopsis for request notifications; the issue description for issue notificatons) |
+| `{{image}}`             | The notification image (typically the media poster)                                                                                 |
+
+### Notify User
+
+These variables are for the target recipient of the notification.
+
+| Variable                                 | Value                                                         |
+| ---------------------------------------- | ------------------------------------------------------------- |
+| `{{notifyuser_username}}`                | The target notification recipient's username                  |
+| `{{notifyuser_email}}`                   | The target notification recipient's email address             |
+| `{{notifyuser_avatar}}`                  | The target notification recipient's avatar URL                |
+| `{{notifyuser_settings_discordId}}`      | The target notification recipient's Discord ID (if set)       |
+| `{{notifyuser_settings_telegramChatId}}` | The target notification recipient's Telegram Chat ID (if set) |
+
+:::info
+The `notifyuser` variables are not defined for the following request notification types, as they are intended for application administrators rather than end users:
+
+- Request Pending Approval
+- Request Automatically Approved
+- Request Processing Failed
+
+On the other hand, the `notifyuser` variables _will_ be replaced with the requesting user's information for the below notification types:
+
+- Request Approved
+- Request Declined
+- Request Available
+
+If you would like to use the requesting user's information in your webhook, please instead include the relevant variables from the [Request](#request) section below.
+:::
+
+### Special
+
+The following variables must be used as a key in the JSON payload (e.g., `"{{extra}}": []`).
+
+| Variable      | Value                                                                                                                          |
+| ------------- | ------------------------------------------------------------------------------------------------------------------------------ |
+| `{{media}}`   | The relevant media object                                                                                                      |
+| `{{request}}` | The relevant request object                                                                                                    |
+| `{{issue}}`   | The relevant issue object                                                                                                      |
+| `{{comment}}` | The relevant issue comment object                                                                                              |
+| `{{extra}}`   | The "extra" array of additional data for certain notifications (e.g., season/episode numbers for series-related notifications) |
+
+#### Media
+
+The `{{media}}` will be `null` if there is no relevant media object for the notification.
+
+These following special variables are only included in media-related notifications, such as requests.
+
+| Variable             | Value                                                                                                          |
+| -------------------- | -------------------------------------------------------------------------------------------------------------- |
+| `{{media_type}}`     | The media type (`movie` or `tv`)                                                                               |
+| `{{media_tmdbid}}`   | The media's TMDB ID                                                                                            |
+| `{{media_tvdbid}}`   | The media's TheTVDB ID                                                                                         |
+| `{{media_status}}`   | The media's availability status (`UNKNOWN`, `PENDING`, `PROCESSING`, `PARTIALLY_AVAILABLE`, or `AVAILABLE`)    |
+| `{{media_status4k}}` | The media's 4K availability status (`UNKNOWN`, `PENDING`, `PROCESSING`, `PARTIALLY_AVAILABLE`, or `AVAILABLE`) |
+
+#### Request
+
+The `{{request}}` will be `null` if there is no relevant media object for the notification.
+
+The following special variables are only included in request-related notifications.
+
+| Variable                                  | Value                                           |
+| ----------------------------------------- | ----------------------------------------------- |
+| `{{request_id}}`                          | The request ID                                  |
+| `{{requestedBy_username}}`                | The requesting user's username                  |
+| `{{requestedBy_email}}`                   | The requesting user's email address             |
+| `{{requestedBy_avatar}}`                  | The requesting user's avatar URL                |
+| `{{requestedBy_settings_discordId}}`      | The requesting user's Discord ID (if set)       |
+| `{{requestedBy_settings_telegramChatId}}` | The requesting user's Telegram Chat ID (if set) |
+
+#### Issue
+
+The `{{issue}}` will be `null` if there is no relevant media object for the notification.
+
+The following special variables are only included in issue-related notifications.
+
+| Variable                                 | Value                                           |
+| ---------------------------------------- | ----------------------------------------------- |
+| `{{issue_id}}`                           | The issue ID                                    |
+| `{{reportedBy_username}}`                | The requesting user's username                  |
+| `{{reportedBy_email}}`                   | The requesting user's email address             |
+| `{{reportedBy_avatar}}`                  | The requesting user's avatar URL                |
+| `{{reportedBy_settings_discordId}}`      | The requesting user's Discord ID (if set)       |
+| `{{reportedBy_settings_telegramChatId}}` | The requesting user's Telegram Chat ID (if set) |
+
+#### Comment
+
+The `{{comment}}` will be `null` if there is no relevant media object for the notification.
+
+The following special variables are only included in issue comment-related notifications.
+
+| Variable                                  | Value                                           |
+| ----------------------------------------- | ----------------------------------------------- |
+| `{{comment_message}}`                     | The comment message                             |
+| `{{commentedBy_username}}`                | The commenting user's username                  |
+| `{{commentedBy_email}}`                   | The commenting user's email address             |
+| `{{commentedBy_avatar}}`                  | The commenting user's avatar URL                |
+| `{{commentedBy_settings_discordId}}`      | The commenting user's Discord ID (if set)       |
+| `{{commentedBy_settings_telegramChatId}}` | The commenting user's Telegram Chat ID (if set) |

docs/using-seerr/notifications/webpush.md

@@ -0,0 +1,23 @@
+---
+title: Web Push
+description: Configure web push notifications for your users.
+sidebar_position: 2
+---
+
+# Web Push
+
+The web push notification agent enables you and your users to receive Seerr notifications in a supported browser.
+
+This notification agent does not require any configuration, but is not enabled in Seerr
+
+:::warning
+Web push notifications require a secure connection to your Seerr instance. Refer to the [Reverse Proxy](/extending-seerr/reverse-proxy) documentation for more information.
+:::
+
+To set up web push notifications, simply enable the agent in **Settings → Notifications → Web Push**. You and your users will then be prompted to allow notifications in your web browser.
+
+Users can opt out of these notifications, or customize the notification types they would like to subscribe to, in their user settings.
+
+:::info
+Web push notifications offer a native notification experience without the need to install an app.
+:::

docs/using-seerr/plex/_category_.json

@@ -0,0 +1,9 @@
+{
+  "label": "Plex Integration",
+  "position": 3,
+  "link": {
+    "type": "generated-index",
+    "title": "Plex Integration",
+    "description": "Learn about Seerr's Plex integration features"
+  }
+}

docs/using-seerr/plex/index.md

@@ -0,0 +1,36 @@
+---
+title: Overview
+description: Learn about Seerr's Plex integration features
+sidebar_position: 1
+---
+
+# Plex Features Overview
+
+Seerr provides integration features that connect with your Plex media server to automate media management tasks.
+
+## Available Features
+
+- [Watchlist Auto Request](./plex/watchlist-auto-request) - Automatically request media from your Plex Watchlist
+- More features coming soon!
+
+## Prerequisites
+
+:::info Authentication Required
+To use any Plex integration features, you must have logged into Seerr at least once with your Plex account.
+:::
+
+**Requirements:**
+- Plex account with access to the configured Plex server
+- Seerr configured with Plex as the media server
+- User authentication via Plex login
+- Appropriate user permissions for specific features
+
+## Getting Started
+
+1. Authenticate at least once using your Plex credentials
+2. Verify you have the necessary permissions for desired features
+3. Follow individual feature guides for setup instructions
+
+:::note Server Configuration
+Plex server configuration is handled by your administrator. If you cannot log in with your Plex account, contact your administrator to verify the server setup.
+:::

docs/using-seerr/plex/watchlist-auto-request.md

@@ -0,0 +1,95 @@
+---
+title: Watchlist Auto Request
+description: Learn how to use the Plex Watchlist Auto Request feature
+sidebar_position: 1
+---
+
+# Watchlist Auto Request
+
+The Plex Watchlist Auto Request feature allows Seerr to automatically create requests for media items you add to your Plex Watchlist. Simply add content to your Plex Watchlist, and Seerr will automatically request it for you.
+
+:::info
+This feature is only available for Plex users. Local users cannot use the Watchlist Auto Request feature.
+:::
+
+## Prerequisites
+
+- You must have logged into Seerr at least once with your Plex account
+- Your administrator must have granted you the necessary permissions
+- Your Plex account must have access to the Plex server configured in Seerr
+
+## Permission System
+
+The Watchlist Auto Request feature uses a two-tier permission system:
+
+### Administrator Permissions (Required)
+Your administrator must grant you these permissions in your user profile:
+- **Auto-Request** (master permission)
+- **Auto-Request Movies** (for movie auto-requests)
+- **Auto-Request Series** (for TV series auto-requests)
+
+### User Activation (Required)
+You must enable the feature in your own profile settings:
+- **Auto-Request Movies** toggle
+- **Auto-Request Series** toggle
+
+:::warning Two-Step Process
+Both administrator permissions AND user activation are required. Having permissions doesn't automatically enable the feature - you must also activate it in your profile.
+:::
+
+## How to Enable
+
+### Step 1: Check Your Permissions
+Contact your administrator to verify you have been granted:
+- `Auto-Request` permission
+- `Auto-Request Movies` and/or `Auto-Request Series` permissions
+
+### Step 2: Activate the Feature
+1. Go to your user profile settings
+2. Navigate to the "General" section
+3. Find the "Auto-Request" options
+4. Enable the toggles for:
+   - **Auto-Request Movies** - to automatically request movies from your watchlist
+   - **Auto-Request Series** - to automatically request TV series from your watchlist
+
+### Step 3: Start Using
+- Add movies and TV shows to your Plex Watchlist
+- Seerr will automatically create requests for new items
+- You'll receive notifications when items are auto-requested
+
+## How It Works
+
+Once properly configured, Seerr will:
+
+1. Periodically checks your Plex Watchlist for new items
+2. Verify if the content already exists in your media libraries
+3. Automatically submits requests for new items that aren't already available
+4. Only requests content types you have permissions for
+5. Notifiy you when auto-requests are created
+
+:::info Content Limitations
+Auto-request only works for standard quality content. 4K content must be requested manually if you have 4K permissions.
+:::
+
+## For Administrators
+
+### Granting Permissions
+1. Navigate to **Users** > **[Select User]** > **Permissions**
+2. Enable the required permissions:
+   - **Auto-Request** (master toggle)
+   - **Auto-Request Movies** (for movie auto-requests)
+   - **Auto-Request Series** (for TV series auto-requests)
+3. Optionally enable **Auto-Approve** permissions for automatic approval
+
+### Default Permissions
+- Go to **Settings** > **Users** > **Default Permissions**
+- Configure auto-request permissions for new users
+- This sets the default permissions but users still need to activate the feature individually
+
+## Limitations
+
+- Local users cannot use this feature
+- 4K content requires manual requests
+- Users must have logged into Seerr with their Plex account
+- Respects user request limits and quotas
+- Won't request content already in your libraries

docs/using-seerr/settings/_category_.json

@@ -0,0 +1,9 @@
+{
+  "label": "Settings",
+  "position": 1,
+  "link": {
+    "type": "generated-index",
+    "title": "Settings",
+    "description": "Configure Seerr to your liking"
+  }
+}

docs/using-seerr/settings/dns-caching.md

@@ -0,0 +1,16 @@
+---
+title: DNS Caching
+description: Configure DNS caching settings.
+sidebar_position: 7
+---
+
+# DNS Caching
+
+Seerr uses DNS caching to improve performance and reduce the number of DNS lookups required for external API calls. This can help speed up response times and reduce load on DNS servers, when something like a Pi-hole is used as a DNS resolver.
+
+## Configuration
+
+You can enable the DNS caching settings in the Network tab of the Seerr settings. The default values follow the standard DNS caching behavior.
+
+- **Force Minimum TTL**: Set a minimum time-to-live (TTL) in seconds for DNS cache entries. This ensures that frequently accessed DNS records are cached for a longer period, reducing the need for repeated lookups. Default is 0.
+- **Force Maximum TTL**: Set a maximum time-to-live (TTL) in seconds for DNS cache entries. This prevents infrequently accessed DNS records from being cached indefinitely, allowing for more up-to-date information to be retrieved. Default is -1 (unlimited).

docs/using-seerr/settings/general.md

@@ -0,0 +1,91 @@
+---
+title: General
+description: Configure global and default settings for Seerr.
+sidebar_position: 1
+---
+
+# General
+
+## API Key
+
+This is your Seerr API key, which can be used to integrate Seerr with third-party applications. Do **not** share this key publicly, as it can be used to gain administrator access!
+
+If you need to generate a new API key for any reason, simply click the button to the right of the text box.
+
+If you want to set the API key, rather than letting it be randomly generated, you can use the API_KEY environment variable. Whatever that variable is set to will be your API key.
+
+## Application Title
+
+If you aren't a huge fan of the name "Seerr" and would like to display something different to your users, you can customize the application title!
+
+## Application URL
+
+Set this to the externally-accessible URL of your Seerr instance.
+
+You must configure this setting in order to enable password reset and generation emails.
+
+## Enable Proxy Support
+
+If you have Seerr behind a reverse proxy, enable this setting to allow Seerr to correctly register client IP addresses. For details, please see the [Express Documentation](https://expressjs.com/en/guide/behind-proxies.html).
+
+This setting is **disabled** by default.
+
+## Enable CSRF Protection
+
+:::warning
+**This is an advanced setting.** Please only enable this setting if you are familiar with CSRF protection and how it works.
+:::
+
+CSRF stands for [cross-site request forgery](https://en.wikipedia.org/wiki/Cross-site_request_forgery). When this setting is enabled, all external API access that alters Seerr application data is blocked.
+
+If you do not use Seerr integrations with third-party applications to add/modify/delete requests or users, you can consider enabling this setting to protect against malicious attacks.
+
+One caveat, however, is that HTTPS is required, meaning that once this setting is enabled, you will no longer be able to access your Seerr instance over _HTTP_ (including using an IP address and port number).
+
+If you enable this setting and find yourself unable to access Seerr, you can disable the setting by modifying `settings.json` in `/app/config`.
+
+This setting is **disabled** by default.
+
+## Enable Image Caching
+
+When enabled, Jellseerr will proxy and cache images from pre-configured sources (such as TMDB). This can use a significant amount of disk space.
+
+Images are saved in the `config/cache/images` and stale images are cleared out every 24 hours.
+
+You should enable this if you are having issues with loading images directly from TMDB in your browser.
+
+## Display Language
+
+Set the default display language for Seerr. Users can override this setting in their user settings.
+
+## Discover Region, Discover Language & Streaming Region
+
+These settings filter content shown on the "Discover" home page based on regional availability and original language, respectively. The Streaming Region filters the available streaming providers on the media page. Users can override these global settings by configuring these same options in their user settings.
+
+## Blacklist Content with Tags and Limit Content Blacklisted per Tag
+
+These settings blacklist any TV shows or movies that have one of the entered tags. The "Process Blacklisted Tags" job adds entries to the blacklist based on the configured blacklisted tags. If a blacklisted tag is removed, any media blacklisted under that tag will be removed from the blacklist when the "Process Blacklisted Tags" job runs.
+
+The limit setting determines how many pages per tag the job will process, with each page containing 20 entries. The job cycles through all 16 available discovery sort options, querying the defined number of pages to blacklist media that is most likely to appear at the top of each sort. Higher limits will create a more accurate blacklist, but will require more storage.
+
+Blacklisted tags are disabled until at least one tag is entered. These settings cannot be overridden in user settings.
+
+## Hide Available Media
+
+When enabled, media which is already available will not appear on the "Discover" home page, or in the "Recommended" or "Similar" categories or other links on media detail pages.
+
+Available media will still appear in search results, however, so it is possible to locate and view hidden items by searching for them by title.
+
+This setting is **disabled** by default.
+
+## Hide Blacklisted Items
+
+When enabled, media that has been blacklisted will not appear on the "Discover" home page, for all administrators. This can be useful to hide content that you don't want to see, such as content with specific tags or content that has been manually blacklisted when you have the "Manage Blacklist" permission.
+
+This setting is **disabled** by default.
+
+## Allow Partial Series Requests
+
+When enabled, users will be able to submit requests for specific seasons of TV series. If disabled, users will only be able to submit requests for all unavailable seasons.
+
+This setting is **enabled** by default.

docs/using-seerr/settings/jobs&cache.md

@@ -0,0 +1,13 @@
+---
+title: Jobs & Cache
+description: Configure jobs and cache settings.
+sidebar_position: 6
+---
+
+# Jobs & Cache
+
+Seerr performs certain maintenance tasks as regularly-scheduled jobs, but they can also be manually triggered on this page.
+
+Seerr also caches requests to external API endpoints to optimize performance and avoid making unnecessary API calls. If necessary, the cache for any particular endpoint can be cleared by clicking the "Flush Cache" button.
+
+You can also view the current image cache size as well as the total number of cached images.

docs/using-seerr/settings/mediaserver.mdx

@@ -0,0 +1,241 @@
+---
+title: Mediaserver Settings
+description: Configure your Jellyfin, Emby, or Plex server settings.
+sidebar_position: 3
+---
+
+# Media Server
+
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
+<Tabs groupId="media-server-type" queryString>
+    <TabItem value="jellyfin" label="Jellyfin">
+:::info
+To set up Jellyfin, make sure you log in using an account with administrative privileges.
+
+The email address can be any email address and is only used for notifications, password resets, and local sign-in.
+It is **not** tied to your Jellyfin account.
+:::
+
+### Jellyfin Libraries
+
+In this section, simply select the libraries you would like Seerr to scan. Seerr will periodically check the selected libraries for available content to update the media status that is displayed to users.
+
+If you do not see your Jellyfin library listed, verify your Jellyfin settings are correct and click the Sync Libraries button.
+
+### Manual Library Scan
+
+Seerr will perform a full scan of your Jellyfin libraries once every 24 hours (recently added items are fetched more frequently). If this is your first time configuring Jellyfin, a one-time full manual library scan is recommended!
+
+### Jellyfin Settings
+
+This section is where you configure the connection to your Jellyfin server.
+
+    <Tabs groupId="versions" queryString>
+        <TabItem value="latest" label="Latest">
+
+#### Internal URL
+
+The internal URL is the URL that Seerr will use to communicate with your Jellyfin server. This URL should be accessible from the machine running Seerr.
+
+In most cases, this will be the hostname or IP address of the machine running Jellyfin, followed by the port number Jellyfin is running on (usually 8096).
+
+:::note
+When running Seerr in a docker container with a bridged network (default), the container's network will be separate from the host network. Therefore, you cannot use `localhost` or `127.0.0.1` as the internal URL as it will resolve to the container itself.
+:::
+:::tip
+If you are running Jellyfin in a docker container, you can put both Seerr and Jellyfin on the same docker network by using a custom [docker network](https://docs.docker.com/reference/cli/docker/network/). This will allow you to use the container name as the internal URL.
+:::
+
+#### External URL
+
+The external URL is the URL that your users will use to access Jellyfin. This URL is used to generate links in `Play on Jellyfin` buttons, Jellyfin avatars and other places where users need to access Jellyfin directly.
+
+In most cases, the external URL will be different from the internal URL. This is especially true if you are connecting to Jellyfin using docker container names or local IP addresses.
+
+#### Forgot Password URL
+
+The forgot password URL is the URL that users will be directed to when they click the "Forgot Password" button on the login page. This URL should be accessible from the machine running Seerr.
+
+By default, this field is empty and the "Forgot Password" button on the login page will redirect to the Jellyfin internal URL with the path `/web/index.html#!/forgotpassword`.
+
+You can customize this URL to point to a custom password reset page if you have one.
+
+        </TabItem>
+        <TabItem value="develop" label="develop">
+
+#### Hostname or IP Address
+
+If you have Seerr installed on the same network as Jellyfin, you can set this to the local IP address of your Jellyfin server. Otherwise, this should be set to a valid hostname (e.g., jellyfin.myawesomeserver.com).
+
+In most cases, this will be the hostname or IP address of the machine running Jellyfin.
+
+:::note
+When running Seerr in a docker container with a bridged network (default), the container's network will be separate from the host network. Therefore, you cannot use `localhost` or `127.0.0.1` as the internal URL as it will resolve to the container itself.
+:::
+:::tip
+If you are running Jellyfin in a docker container, you can put both Seerr and Jellyfin on the same docker network by using a custom [docker network](https://docs.docker.com/reference/cli/docker/network/). This will allow you to use the container name as the internal URL.
+:::
+
+#### Port
+
+This value should be set to the port that your Jellyfin server listens on. The default port that Jellyfin uses is 8096, but you may need to set this to 443 or some other value if your Jellyfin server is hosted on a VPS or a different machine and is behind a reverse proxy.
+
+#### Use SSL
+
+Enable this setting to connect to Jellyfin via HTTPS rather than HTTP. Note that self-signed certificates are **not** officially supported.
+
+#### External URL
+
+The external URL is the URL that your users will use to access Jellyfin. This URL is used to generate links in `Play on Jellyfin` buttons, Jellyfin avatars and other places where users need to access Jellyfin directly.
+
+In most cases, the external URL will be different from the internal URL. This is especially true if you are connecting to Jellyfin using docker container names or local IP addresses.
+
+#### Forgot Password URL
+
+The forgot password URL is the URL that users will be directed to when they click the "Forgot Password" button on the login page. This URL should be accessible from the machine running Seerr.
+
+By default, this field is empty and the "Forgot Password" button on the login page will redirect to the Jellyfin internal URL with the path `/web/index.html#!/forgotpassword`.
+
+You can customize this URL to point to a custom password reset page if you have one.
+
+            </TabItem>
+        </Tabs>
+    </TabItem>
+
+   <TabItem value="emby" label="Emby">
+:::info
+To set up Emby, make sure you log in using an account with administrative privileges.
+
+The email address can be any email address and is only used for notifications, password resets, and local sign-in.
+It is **not** tied to your Emby account.
+:::
+
+### Emby Libraries
+
+In this section, simply select the libraries you would like Seerr to scan. Seerr will periodically check the selected libraries for available content to update the media status that is displayed to users.
+
+If you do not see your Emby library listed, verify your Emby settings are correct and click the Sync Libraries button.
+
+### Manual Library Scan
+
+Seerr will perform a full scan of your Emby libraries once every 24 hours (recently added items are fetched more frequently). If this is your first time configuring Emby, a one-time full manual library scan is recommended!
+
+### Emby Settings
+
+This section is where you configure the connection to your Emby server.
+
+        <Tabs groupId="versions" queryString>
+            <TabItem value="latest" label="Latest">
+
+#### Internal URL
+
+The internal URL is the URL that Seerr will use to communicate with your Emby server. This URL should be accessible from the machine running Seerr.
+
+In most cases, this will be the hostname or IP address of the machine running Emby, followed by the port number Emby is running on (usually 8096).
+
+:::note
+When running Seerr in a docker container with a bridged network (default), the container's network will be separate from the host network. Therefore, you cannot use `localhost` or `127.0.0.1` as the internal URL as it will resolve to the container itself.
+:::
+:::tip
+If you are running Emby in a docker container, you can put both Seerr and Emby on the same docker network by using a custom [docker network](https://docs.docker.com/reference/cli/docker/network/). This will allow you to use the container name as the internal URL.
+:::
+
+#### External URL
+
+The external URL is the URL that your users will use to access Emby. This URL is used to generate links in `Play on Emby` buttons, Emby avatars and other places where users need to access Emby directly.
+
+In most cases, the external URL will be different from the internal URL. This is especially true if you are connecting to Emby using docker container names or local IP addresses.
+
+#### Forgot Password URL
+
+The forgot password URL is the URL that users will be directed to when they click the "Forgot Password" button on the login page. This URL should be accessible from the machine running Seerr.
+
+By default, this field is empty and the "Forgot Password" button on the login page will redirect to the Emby internal URL with the path `/web/index.html#!/forgotpassword.html`.
+
+You can customize this URL to point to a custom password reset page if you have one.
+
+            </TabItem>
+            <TabItem value="develop" label="develop">
+
+#### Hostname or IP Address
+
+If you have Seerr installed on the same network as Emby, you can set this to the local IP address of your Emby server. Otherwise, this should be set to a valid hostname (e.g., jellyfin.myawesomeserver.com).
+
+In most cases, this will be the hostname or IP address of the machine running Emby.
+
+:::note
+When running Seerr in a docker container with a bridged network (default), the container's network will be separate from the host network. Therefore, you cannot use `localhost` or `127.0.0.1` as the internal URL as it will resolve to the container itself.
+:::
+:::tip
+If you are running Emby in a docker container, you can put both Seerr and Emby on the same docker network by using a custom [docker network](https://docs.docker.com/reference/cli/docker/network/). This will allow you to use the container name as the internal URL.
+:::
+
+#### Port
+
+This value should be set to the port that your Emby server listens on. The default port that Emby uses is 8096, but you may need to set this to 443 or some other value if your Emby server is hosted on a VPS or a different machine and is behind a reverse proxy.
+
+#### Use SSL
+
+Enable this setting to connect to Emby via HTTPS rather than HTTP. Note that self-signed certificates are **not** officially supported.
+
+#### External URL
+
+The external URL is the URL that your users will use to access Emby. This URL is used to generate links in `Play on Emby` buttons, Emby avatars and other places where users need to access Emby directly.
+
+In most cases, the external URL will be different from the internal URL. This is especially true if you are connecting to Emby using docker container names or local IP addresses.
+
+#### Forgot Password URL
+
+The forgot password URL is the URL that users will be directed to when they click the "Forgot Password" button on the login page. This URL should be accessible from the machine running Seerr.
+
+By default, this field is empty and the "Forgot Password" button on the login page will redirect to the Emby internal URL with the path `/web/index.html#!/startup/forgotpassword.html`.
+
+You can customize this URL to point to a custom password reset page if you have one.
+
+            </TabItem>
+        </Tabs>
+    </TabItem>
+
+    <TabItem value="plex" label="Plex">
+
+### Plex Settings
+
+:::info
+To set up Plex, you can either enter your details manually or select a server retrieved from [plex.tv](https://plex.tv/). Press the button to the right of the "Server" dropdown to retrieve available servers.
+
+Depending on your setup/configuration, you may need to enter your Plex server details manually in order to establish a connection from Seerr.
+:::
+
+#### Hostname or IP Address
+
+If you have Seerr installed on the same network as Plex, you can set this to the local IP address of your Plex server. Otherwise, this should be set to a valid hostname (e.g., `plex.myawesomeserver.com`).
+
+#### Port
+
+This value should be set to the port that your Plex server listens on. The default port that Plex uses is `32400`, but you may need to set this to `443` or some other value if your Plex server is hosted on a VPS or cloud provider.
+
+#### Use SSL
+
+Enable this setting to connect to Plex via HTTPS rather than HTTP. Note that self-signed certificates are _not_ supported.
+
+#### Web App URL (optional)
+
+The **Play on Plex** buttons on media pages link to items on your Plex server. By default, these links use the [Plex Web App](https://support.plex.tv/articles/200288666-opening-plex-web-app/) hosted from plex.tv, but you can provide the URL to the web app on your Plex server and we'll use that instead!
+
+Note that you will need to enter the full path to the web app (e.g., `https://plex.myawesomeserver.com/web`).
+
+### Plex Libraries
+
+In this section, simply select the libraries you would like Seerr to scan. Seerr will periodically check the selected libraries for available content to update the media status that is displayed to users.
+
+If you do not see your Plex libraries listed, verify your Plex settings are correct and click the **Sync Libraries** button.
+
+### Manual Library Scan
+
+Seerr will perform a full scan of your Plex libraries once every 24 hours (recently added items are fetched more frequently). If this is your first time configuring Plex, a one-time full manual library scan is recommended!
+
+</TabItem>
+
+</Tabs>

docs/using-seerr/settings/notifications.mdx

@@ -0,0 +1,9 @@
+---
+title: Notifications
+description: Configure notifications for your users.
+sidebar_position: 5
+---
+
+# Notifications
+
+Please see the [Notifications](/using-seerr/notifications) page for more information.

docs/using-seerr/settings/services.md

@@ -0,0 +1,75 @@
+---
+title: Services
+description: Configure your default services.
+sidebar_position: 4
+---
+
+# Services
+
+:::info
+**If you keep separate copies of non-4K and 4K content in your media libraries, you will need to set up multiple Radarr/Sonarr instances and link each of them to Seerr.**
+
+Seerr checks these linked servers to determine whether or not media has already been requested or is available, so two servers of each type are required _if you keep separate non-4K and 4K copies of media._
+
+**If you only maintain one copy of media, you can instead simply set up one server and set the "Quality Profile" setting on a per-request basis.**
+:::
+
+### Radarr/Sonarr Settings
+
+:::warning
+**Only v3 & V4 Radarr/Sonarr servers are supported!** If your Radarr/Sonarr server is still running v2, you will need to upgrade in order to add it to Seerr.
+::::
+
+#### Default Server
+
+At least one server needs to be marked as "Default" in order for requests to be sent successfully to Radarr/Sonarr.
+
+If you have separate 4K Radarr/Sonarr servers, you need to designate default 4K servers _in addition to_ default non-4K servers.
+
+#### 4K Server
+
+Only select this option if you have separate non-4K and 4K servers. If you only have a single Radarr/Sonarr server, do _not_ check this box!
+
+#### Server Name
+
+Enter a friendly name for the Radarr/Sonarr server.
+
+#### Hostname or IP Address
+
+If you have Seerr installed on the same network as Radarr/Sonarr, you can set this to the local IP address of your Radarr/Sonarr server. Otherwise, this should be set to a valid hostname (e.g., `radarr.myawesomeserver.com`).
+
+#### Port
+
+This value should be set to the port that your Radarr/Sonarr server listens on. By default, Radarr uses port `7878` and Sonarr uses port `8989`, but you may need to set this to `443` or some other value if your Radarr/Sonarr server is hosted on a VPS or cloud provider.
+
+#### Use SSL
+
+Enable this setting to connect to Radarr/Sonarr via HTTPS rather than HTTP. Note that self-signed certificates are _not_ supported.
+
+#### API Key
+
+Enter your Radarr/Sonarr API key here. Do _not_ share these key publicly, as they can be used to gain administrator access to your Radarr/Sonarr servers!
+
+You can locate the required API keys in Radarr/Sonarr in **Settings → General → Security**.
+
+#### URL Base
+
+If you have configured a URL base for your Radarr/Sonarr server, you _must_ enter it here in order for Jellyeerr to connect to those services!
+
+You can verify whether or not you have a URL base configured in your Radarr/Sonarr server at **Settings → General → Host**. (Note that a restart of your Radarr/Sonarr server is required if you modify this setting!)
+
+#### Profiles, Root Folder, Minimum Availability
+
+Select the default settings you would like to use for all new requests. Note that all of these options are required, and that requests will fail if any of these are not configured!
+
+#### External URL (optional)
+
+If the hostname or IP address you configured above is not accessible outside your network, you can set a different URL here. This "external" URL is used to add clickable links to your Radarr/Sonarr servers on media detail pages.
+
+#### Enable Scan (optional)
+
+Enable this setting if you would like to scan your Radarr/Sonarr server for existing media/request status. It is recommended that you enable this setting, so that users cannot submit requests for media which has already been requested or is already available.
+
+#### Enable Automatic Search (optional)
+
+Enable this setting to have Radarr/Sonarr to automatically search for media upon approval of a request.

docs/using-seerr/settings/users.md

@@ -0,0 +1,45 @@
+---
+title: User Settings
+description: Configure global and default user settings.
+sidebar_position: 2
+---
+
+# Users
+
+## Enable Local Sign-In
+
+When enabled, users who have configured passwords will be allowed to sign in using their email address.
+
+When disabled, your mediaserver OAuth becomes the only sign-in option, and any "local users" you have created will not be able to sign in to Seerr.
+
+This setting is **enabled** by default.
+
+## Enable Jellyfin/Emby/Plex Sign-In
+
+When enabled, users will be able to sign in to Seerr using their Jellyfin/Emby/Plex credentials, provided they have linked their media server accounts.
+
+When disabled, users will only be able to sign in using their email address. Users without a password set will not be able to sign in to Seerr.
+
+This setting is **enabled** by default.
+
+## Enable New Jellyfin/Emby/Plex Sign-In
+
+When enabled, users with access to your media server will be able to sign in to Seerr even if they have not yet been imported. Users will be automatically assigned the permissions configured in the [Default Permissions](#default-permissions) setting upon first sign-in.
+
+This setting is **enabled** by default.
+
+## Global Movie Request Limit & Global Series Request Limit
+
+Select the request limits you would like granted to users.
+
+Unless an override is configured, users are granted these global request limits.
+
+Note that users with the **Manage Users** permission are exempt from request limits, since that permission also grants the ability to submit requests on behalf of other users.
+
+## Default Permissions
+
+Select the permissions you would like assigned to new users to have by default upon account creation.
+
+If [Enable New Jellyfin/Emby/Plex Sign-In](#enable-new-jellyfinembyplex-sign-in) is enabled, any user with access to your media server will be able to sign in to Seerr, and they will be granted the permissions you select here upon first sign-in.
+
+This setting only affects new users, and has no impact on existing users. In order to modify permissions for existing users, you will need to edit the users.

docs/using-seerr/users/_category_.json

@@ -0,0 +1,9 @@
+{
+  "label": "Users",
+  "position": 2,
+  "link": {
+    "type": "generated-index",
+    "title": "Users",
+    "description": "Configure your Seerr users"
+  }
+}

docs/using-seerr/users/adding-users.mdx

@@ -0,0 +1,64 @@
+---
+title: Adding Users
+description: Add users to your Seerr instance.
+sidebar_position: 2
+---
+
+# Adding Users
+
+There are currently two methods to add users to Seerr: importing Mediaserver users and creating "local users." All new users are created with the [default permissions](/using-seerr/settings/users#default-permissions) defined in **Settings → Users**.
+
+### Importing Mediaserver Users
+
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
+<Tabs groupId="media-server-type" queryString>
+  <TabItem value="jellyfin" label="Jellyfin">
+    Clicking the **Import Jellyfin Users** button on the **User List** page will fetch the list of users with access to the Jellyfin server and add them to Seerr automatically.
+
+    Importing Jellyfin users is not required, however. Any user with access to the Jellyfin server can log in to Seerr even if they have not been imported, and will be assigned the configured [default permissions](/using-seerr/settings/users#default-permissions) upon their first login.
+
+:::tip
+To disable new Jellyfin sign-ins, navigate to **Settings &rarr; Users** and uncheck the [**Enable New Jellyfin Sign-In**](/using-seerr/settings/users#enable-new-jellyfinembyplex-sign-in) box.
+:::
+
+  </TabItem>
+  <TabItem value="emby" label="Emby">
+    Clicking the **Import Emby Users** button on the **User List** page will fetch the list of users with access to the Emby server and add them to Seerr automatically.
+
+    Importing Emby users is not required, however. Any user with access to the Emby server can log in to Seerr even if they have not been imported, and will be assigned the configured [default permissions](/using-seerr/settings/users#default-permissions) upon their first login.
+
+:::tip
+To disable new Emby sign-ins, navigate to **Settings &rarr; Users** and uncheck the [**Enable New Emby Sign-In**](/using-seerr/settings/users#enable-new-jellyfinembyplex-sign-in) box.
+:::
+
+  </TabItem>
+
+  <TabItem value="plex" label="Plex">
+    Clicking the **Import Plex Users** button on the **User List** page will fetch the list of users with access to the Plex server from [plex.tv](https://www.plex.tv/), and add them to Seerr automatically.
+
+    Importing Plex users is not required, however. Any user with access to the Plex server can log in to Seerr even if they have not been imported, and will be assigned the configured [default permissions](/using-seerr/settings/users#default-permissions) upon their first login.
+
+:::tip
+To disable new Plex sign-ins, navigate to **Settings &rarr; Users** and uncheck the [**Enable New Plex Sign-In**](/using-seerr/settings/users#enable-new-jellyfinembyplex-sign-in) box.
+:::
+
+  </TabItem>
+</Tabs>
+
+### Creating Local Users
+
+If you would like to grant Seerr access to a user who doesn't have their own Plex account and/or access to the Plex server, you can manually add them by clicking the **Create Local User** button.
+
+#### Email Address
+
+Enter a valid email address at which the user can receive messages pertaining to their account and other notifications. The email address currently cannot be modified after the account is created.
+
+#### Automatically Generate Password
+
+If an [application URL](/using-seerr/settings/general#application-url) is set and [email notifications](/using-seerr/notifications/email) have been configured and enabled, Seerr can automatically generate a password for the new user.
+
+#### Password
+
+If you would prefer to manually configure a password, enter a password here that is a minimum of 8 characters.

docs/using-seerr/users/deleting-users.md

@@ -0,0 +1,9 @@
+---
+title: Deleting Users
+description: Delete users from Seerr.
+sidebar_position: 4
+---
+
+# Deleting Users
+
+When users are deleted, all of their data and request history is also cleared from the database.

docs/using-seerr/users/editing-users.md

@@ -0,0 +1,62 @@
+---
+title: Editing Users
+description: Edit user settings and permissions.
+sidebar_position: 3
+---
+
+# Editing Users
+
+From the **User List**, you can click the **Edit** button to modify a particular user's settings.
+
+You can also click the check boxes and click the **Bulk Edit** button to set user permissions for multiple users at once.
+
+## General
+
+### Display Name
+
+You can optionally set a "friendly name" for any user. This name will be used in lieu of their media server (Jellyfin/Emby/Plex) username (for users imported from the media server) or their email address (for manually-created local users).
+
+### Email
+
+:::note
+This field is read-only for users imported from Plex.
+:::
+You can optionally set a proper email address for any user. This email address will be used for notifications, local sign-in and password resets.
+
+By default, users imported from Jellyfin/Emby will use their media server username as their email address.
+
+:::warning
+You cannot leave this field blank.
+:::
+
+### Display Language
+
+Users can override the [global display language](/using-seerr/settings/general#display-language) to use Seerr in their preferred language.
+
+### Discover Region & Discover Language
+
+Users can override the [global filter settings](/using-seerr/settings/general#discover-region-discover-language--streaming-region) to suit their own preferences.
+
+### Movie Request Limit & Series Request Limit
+
+You can override the default settings and assign different request limits for specific users by checking the **Enable Override** box and selecting the desired request limit and time period.
+
+Unless an override is configured, users are granted the global request limits.
+
+Note that users with the **Manage Users** permission are exempt from request limits, since that permission also grants the ability to submit requests on behalf of other users.
+
+Users are also unable to modify their own request limits.
+
+## Password
+
+All "local users" are assigned passwords upon creation, but users imported from Plex can also optionally configure passwords to enable sign-in using their email address.
+
+Passwords must be a minimum of 8 characters long.
+
+## Notifications
+
+Users can configure their personal notification settings here. Please see [Notifications](/using-seerr/notifications/) for details on configuring and enabling notifications.
+
+## Permissions
+
+Users cannot modify their own permissions. Users with the **Manage Users** permission can manage permissions of other users, except those of users with the **Admin** permission.

docs/using-seerr/users/owner.md

@@ -0,0 +1,17 @@
+---
+title: Owner Account
+description: Your owner account is the primary account for managing Seerr.
+sidebar_position: 1
+---
+
+# Owner Account
+
+The user account created during Seerr setup is the "Owner" account, which cannot be deleted or modified by other users. This account's credentials are used to authenticate with your media server and configure Seerr settings.
+
+:::note
+In case of Jellyfin/Emby, the owner account is also used for API access to your media server. This account should have a valid authentication token for your media server.
+:::
+
+:::tip
+If your authentication token is ever invalidated or changed, you can refresh it by re-authenticating with your media server.
+:::