docs: update documentation to reflect recent changes/additions (#1730) [skip ci]

* docs: update documentation to reflect recent changes/additions

* docs: add list of third-party integrations

* docs: add v3 warning

* docs: fix Docker for Windows link text

* docs: fix Telegram 'Send Silently' setting description

* docs: note that application URL is required for password reset/generation

* docs: add additional details on webhook template variables

docs/using-overseerr/notifications/README.md

@@ -5,7 +5,9 @@
 Overseerr currently supports the following notification agents:
 
 - [Email](./email.md)
+- [Web Push](./webpush.md)
 - [Discord](./discord.md)
+- [LunaSea](./lunasea.md)
 - [Pushbullet](./pushbullet.md)
 - [Pushover](./pushover.md)
 - [Slack](./slack.md)
@@ -14,11 +16,9 @@ Overseerr currently supports the following notification agents:
 
 ## Setting Up Notifications
 
-Configuring your notifications is quite simple. First, you will need to visit the **Settings** page and click **Notifications** in the menu. This will present you with all of the currently available notification agents. Click on each one individually to configure them.
+Simply configure your desired notification agents in **Settings → Notifications**.
 
-You must configure which type of notifications you want to send _per agent_. If no types are selected, you will not receive notifications!
-
-Note that some notifications are intended for the user who submitted the relevant request, while others are for administrators. For details, please see the documentation for the specific agent you would like to use.
+Users can customize their personal notification preferences in their own user notification settings.
 
 ## Requesting New Notification Agents
 

docs/using-overseerr/notifications/discord.md

@@ -1,26 +1,16 @@
 # Discord
 
+The Discord notification agent enables you to post notifications to a channel in a server you manage.
+
 {% hint style="info" %}
-The following notification types will mention _all_ users with the **Manage Requests** permission, as these notification types are intended for application administrators rather than end users:
-
-- Media Requested
-- Media Automatically Approved
-- Media Failed
-
-On the other hand, the notification types below will only mention the user who submitted the request:
-
-- Media Approved (does not include automatic approvals)
-- Media Declined
-- Media Available
-
-In order for users to be mentioned in Discord notifications, they must have their [Discord user ID](https://support.discord.com/hc/en-us/articles/206346498-Where-can-I-find-my-User-Server-Message-ID-) configured and **Enable Mentions** checked in their Discord notification user settings.
+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.
 {% endhint %}
 
 ## Configuration
 
-{% hint style="info" %}
-To configure Discord notifications, you first need to [create a webhook](https://support.discord.com/hc/en-us/articles/228383668-Intro-to-Webhooks).
-{% endhint %}
+### Webhook URL
+
+You can find the webhook URL in the Discord application, at **Server Settings → Integrations → Webhooks**.
 
 ### Bot Username (optional)
 
@@ -29,7 +19,3 @@ If you would like to override the name you configured for your bot in Discord, y
 ### Bot Avatar URL (optional)
 
 Similar to the bot username, you can override the avatar for your bot.
-
-### Webhook URL
-
-You can find the webhook URL in the Discord application, at **Server Settings → Integrations → Webhooks**.

docs/using-overseerr/notifications/email.md

@@ -1,22 +1,14 @@
 # Email
 
+## Configuration
+
 {% hint style="info" %}
-The following email notification types are sent to _all_ users with the **Manage Requests** permission, as these notification types are intended for application administrators rather than end users:
-
-- Media Requested
-- Media Automatically Approved
-- Media Failed
-
-On the other hand, the email notification types below are only sent to the user who submitted the request:
-
-- Media Approved (does not include automatic approvals)
-- Media Declined
-- Media Available
-
-In order for users to receive email notifications, they must have **Enable Notifications** checked in their email notification user settings.
+If the [Application URL](../settings/README.md#application-url) setting is configured in **Settings → General**, Overseerr will explicitly set the origin server hostname when connecting to the SMTP host.
 {% endhint %}
 
-## Configuration
+### Sender Name (optional)
+
+Configure a friendly name for the email sender (e.g., "Overseerr").
 
 ### Sender Address
 
@@ -24,10 +16,6 @@ Set this to the email address you would like to appear in the "from" field of th
 
 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.
 
-### Sender Name (optional)
-
-Configure a friendly name for the email sender.
-
 ### SMTP Host
 
 Set this to the hostname or IP address of your SMTP host/server.

docs/using-overseerr/notifications/lunasea.md

@@ -0,0 +1,17 @@
+# LunaSea
+
+## Configuration
+
+### Webhook URL
+
+Copy either a device- or user-based webhook URL from the LunaSea app into this field.
+
+### Profile Name (optional)
+
+If not using the `default` profile in the LunaSea app, specify the name of the profile here.
+
+Note that the entered profile name **_must_** match the name in LunaSea exactly (including any capitalization, punctuation, and/or whitespace).
+
+{% hint style="info" %}
+Please refer to the [LunaSea documentation](https://docs.lunasea.app/lunasea/notifications/overseerr) for more details on configuring these notifications.
+{% endhint %}

docs/using-overseerr/notifications/slack.md

@@ -4,4 +4,8 @@
 
 ### Webhook URL
 
-Simply [create a webhook](https://catflixserver.slack.com/apps/new/A0F7XDUAZ-incoming-webhooks) and enter the URL in this field.
+Simply [create a webhook](https://my.slack.com/services/new/incoming-webhook/) and enter the URL in this field.
+
+{% hint style="info" %}
+Please refer to the [Slack API documentation](https://api.slack.com/messaging/webhooks) for more details on configuring these notifications..
+{% endhint %}

docs/using-overseerr/notifications/telegram.md

@@ -1,14 +1,7 @@
 # Telegram
 
 {% hint style="info" %}
-All notification types will be sent to the chat ID configured in your Overseerr application settings.
-
-If a user has configured a chat ID and has **Enable Notifications** checked in their Telegram notification user settings as well, they will be sent the following notification types for requests which they submit:
-
-- Media Approved (does not include automatic approvals)
-- Media Declined
-- Media Available
-
+Users can optionally configure their own notifications in their user settings.
 {% endhint %}
 
 ## Configuration
@@ -16,12 +9,12 @@ If a user has configured a chat ID and has **Enable Notifications** checked in t
 {% hint style="info" %}
 In order to configure Telegram notifications, you first need to [create a bot](https://telegram.me/BotFather).
 
-Bots **cannot** initiate conversations with users, users must have your bot added to a conversation in order to receive notifications.
+Bots **cannot** initiate conversations with users, so users must have your bot added to a conversation in order to receive notifications.
 {% endhint %}
 
 ### Bot Username (optional)
 
-If this value is configured, users will be able to start a chat with your bot and configure their own personal notifications.
+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.
 
@@ -35,4 +28,4 @@ To obtain your chat ID, simply create a new group chat, add [@get_id_bot](https:
 
 ### Send Silently (optional)
 
-Instagram allows you to enable silent notifications. Those will present a pop-up to the user, but will not make any sound. That's a per user configuration.
+Optionally, notifications can be sent silently. Silent notifications send messages without notification sounds.

docs/using-overseerr/notifications/webhooks.md

@@ -1,6 +1,6 @@
 # Webhook
 
-The webhook notification agent allows you to send a custom JSON payload to any endpoint.
+The webhook notification agent enables you to send a custom JSON payload to any endpoint for specific notification events.
 
 ## Configuration
 
@@ -18,7 +18,7 @@ This value will be sent as an `Authorization` HTTP header.
 
 ### JSON Payload
 
-Customize the JSON payload to suit your needs. Overseerr provides several [template variables](./webhooks.md#template-variables) for use in the payload, which will be replaced with the relevant data when the notifications are triggered.
+Customize the JSON payload to suit your needs. Overseerr 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
 
@@ -67,12 +67,12 @@ The following variables must be used as a key in the JSON payload (e.g., `"{{ext
 
 These `{{media}}` special variables are only included in media-related notifications, such as requests.
 
-- `{{media_type}}` Media type. Either `movie` or `tv`.
+- `{{media_type}}` Media type (`movie` or `tv`).
 - `{{media_tmdbid}}` Media's TMDb ID.
 - `{{media_imdbid}}` Media's IMDb ID.
 - `{{media_tvdbid}}` Media's TVDB ID.
-- `{{media_status}}` Media's availability status (e.g., `AVAILABLE` or `PENDING`).
-- `{{media_status4k}}` Media's 4K availability status (e.g., `AVAILABLE` or `PENDING`).
+- `{{media_status}}` Media's availability status (`UNKNOWN`, `PENDING`, `PROCESSING`, `PARTIALLY_AVAILABLE`, or `AVAILABLE`).
+- `{{media_status4k}}` Media's 4K availability status (`UNKNOWN`, `PENDING`, `PROCESSING`, `PARTIALLY_AVAILABLE`, or `AVAILABLE`)
 
 #### Request
 
@@ -82,5 +82,5 @@ The `{{request}}` special variables are only included in request-related notific
 - `{{requestedBy_username}}` Requesting user's username.
 - `{{requestedBy_email}}` Requesting user's email address.
 - `{{requestedBy_avatar}}` Requesting user's avatar URL.
-- `{{requestedBy_settings_discordId}}` Requesting user's Discord ID (if one is set).
-- `{{requestedBy_settings_telegramChatId}}` Requesting user's Telegram Chat ID (if one is set).
+- `{{requestedBy_settings_discordId}}` Requesting user's Discord ID (if set).
+- `{{requestedBy_settings_telegramChatId}}` Requesting user's Telegram Chat ID (if set).

docs/using-overseerr/notifications/webpush.md

@@ -0,0 +1,17 @@
+# Web Push
+
+The web push notification agent enables you and your users to receive Overseerr notifications in a supported browser.
+
+This notification agent does not require any configuration, but is not enabled in Overseerr by default.
+
+{% hint style="warning" %}
+**The web push agent only works via HTTPS.** Refer to our [reverse proxy examples](../../extending-overseerr/reverse-proxy.md) for help on proxying Overseerr traffic via HTTPS.
+{% endhint %}
+
+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.
+
+{% hint style="info" %}
+Web push notifications offer a native notification experience without the need to install an app. iOS devices do not have support for these notifications at this time, however.
+{% endhint %}