Remove classic instance notifications docs (#4179)

The classic instance notification system has been superseded by Event
Notifications. Remove the configuration page, the classic Slack webhook
page, their shared partial, and all cross-references. Update the intro
and RBAC docs to point to Event Notifications instead.

Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: AmberAlston

docs/intro-replicated.mdx

@@ -202,8 +202,8 @@ When installed alongside an application, the Replicated SDK automatically sends
 This instance data includes health and status indicators, adoption metrics, and performance metrics.
 For more information, see [About instance and event data](/vendor/instance-insights-event-data).
 
-ISVs can also set up email and Slack notifications to get alerted of important instance issues or performance trends.
-For more information, see [Configuring instance notifications](/vendor/instance-notifications-config).
+ISVs can also set up notifications to get alerted of important instance issues or performance trends.
+For more information, see [About Event Notifications](/vendor/event-notifications).
 
 ### Support
 

docs/partials/instance-insights/_notifications-about.mdx

@@ -96,21 +96,3 @@ Event Notifications has the following limitations:
 - It is possible to create a notification for some resource types, such as customers and support bundles, but not to access the notification linked asset due to your allowed user permissions. This is most likely to impact teams with [enterprise and custom RBAC policies](team-management-rbac-configuring). For example, someone with the [Sales RBAC role](team-management-rbac-configuring) can create a notification for a customer uploading a support bundle, but does not have permission to view the linked specific customer bundle due to their RBAC role permissions.
 - The Release Assets Downloaded event might fire per chart or image if the customer pulls each separately as part of your installation instructions. Because release assets might be shared across many of your release versions, the Vendor Portal records the event at the chart/image level and does not associate the event with a specific release version. If you find this alert too noisy, reach out to us to further discuss your specific use case.
 
-## Comparison to instance notifications (Classic)
-
-Event Notifications is the next generation of instance notification functionality in the Vendor Portal. Compared to [Instance Notifications (Classic)](instance-notifications-config), Event Notifications offers more event types, fine-grained filtering, flexible delivery routing, notification history tracking, and better access control.
-
-You can use Event Notifications concurrently with Instance Notifications (Classic) while you evaluate and transition.
-
-The following table compares the functionality offered by Instance Notifications (Classic) and Event Notifications:
-
-| Feature | Instance Notifications (Classic) | Event Notifications |
-|---------|------------------------------|---------------------------|
-| **Event Types** | Three event types: App Status, System Events, Custom Metrics | More than 20 event types across six categories |
-| **Scope** | Per-instance subscriptions | Team-wide with flexible filtering |
-| **Delivery** | Slack (1 team webhook) + Email (1 user) | Per notification email or webhook |
-| **Filtering** | Instance-level only | Multi-field filters (app, customer, channel, etc.) |
-| **Permissions** | User-scoped | Team-scoped RBAC |
-| **Webhook Security** | Basic | HMAC-SHA256 signing |
-| **Delivery Testing** | Manual | Built-in payload preview and test buttons for both email and webhook delivery |
-| **Notification History** | Minimal | Full delivery attempt tracking with event details |

docs/vendor/event-notifications.mdx

@@ -136,7 +136,7 @@ Grants the holder permission to create a new license in the specified applicatio
 
 ### KOTS/app/[:appid]/license/[:customerid]/read
 
-Grants the holder permission to view the license specified by ID. If you deny this permission, the licenses do not appear in search, CSV export, or the Vendor Portal. The holder also cannot subscribe to this license's instance notifications.
+Grants the holder permission to view the license specified by ID. If you deny this permission, the licenses do not appear in search, CSV export, or the Vendor Portal.
 
 ### KOTS/app/[:appid]/license/[:customerid]/update
 
@@ -556,14 +556,6 @@ Grants the holder permission to create team members.
 
 Grants the holder permission to delete other team members.
 
-### Team/notifications/slack-webhook/read
-
-Grants the holder permission to view the team's Slack webhook for classic instance notifications. For more information, see [Configure Instance Notifications (Classic)](instance-notifications-config).
-
-### Team/notifications/slack-webhook/update
-
-Grants the holder permission to edit the team's Slack webhook for classic instance notifications. For more information, see [Configure Instance Notifications (Classic)](instance-notifications-config).
-
 ### Team/notifications/\*\*
 
 Grants the holder full access to all notification features, including managing other users' event notification subscriptions. For more information, see [About Event Notifications](event-notifications).

docs/vendor/instance-notifications-config.mdx

@@ -110,7 +110,7 @@ const sidebars = {
                 "vendor/team-management-scim-provisioning",
               ],
             },
-            "vendor/team-management-slack-config",
+
             "vendor/replicated-api-tokens",
           ],
         },
@@ -187,7 +187,7 @@ const sidebars = {
                 "vendor/event-notifications-manage",
               ],
             },
-            "vendor/instance-notifications-config",
+
             "vendor/instance-data-export",
           ],
         },