akanealw/Charon
1
0
Fork 0
Code Issues Pull Requests Actions 15 Packages Projects Releases Wiki Activity

fix: clarify feature flag behavior for Slack notifications in documentation

Browse Source
This commit is contained in:
GitHub Actions
2026-03-15 12:14:48 +00:00
parent 41ecb7122f
commit 82b1c85b7c
1 changed files with 0 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/features/notifications.md
View File

@@ -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