From 82b1c85b7c3cf60b67733ce5792aaaaada52050c Mon Sep 17 00:00:00 2001 From: GitHub Actions Date: Sun, 15 Mar 2026 12:14:48 +0000 Subject: [PATCH] fix: clarify feature flag behavior for Slack notifications in documentation --- docs/features/notifications.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/docs/features/notifications.md b/docs/features/notifications.md index 2cb89f05..c8d7dc3f 100644 --- a/docs/features/notifications.md +++ b/docs/features/notifications.md @@ -37,8 +37,6 @@ Email notifications send HTML-branded alerts directly to one or more email addre Email notifications use built-in HTML templates with Charon branding — no JSON template editing is required. -> **Feature Flag:** Email notifications must be enabled via `feature.notifications.service.email.enabled` in **Settings** → **Feature Flags** before the Email provider option appears. - ### Why JSON Templates? JSON templates give you complete control over notification formatting, allowing you to: @@ -193,8 +191,6 @@ Slack notifications send messages to a channel using an Incoming Webhook URL. > **Security:** Your Webhook URL is stored securely and is never exposed in API responses. The settings page only shows a `has_token: true` indicator, so your URL stays private even if someone gains read-only access to the API. -> **Feature Flag:** Slack notifications must be enabled via `feature.notifications.service.slack.enabled` in **Settings** → **Feature Flags** before the Slack provider option appears. - #### Basic Message ```json