Enforgate
Start free
Browse documentation

How do I get notified when an agent needs approval?

A require_approval verdict is only useful if a human actually sees it. Notification configs decide where Enforgate sends that alert, for email, Slack, Microsoft Teams, and Telegram, all from one reusable, org-scoped setup.

One config, many keys

On Settings → Notifications, create a config: give it a name, then turn on whichever channels you want and fill in their details. Each API key on /dashboard/keys can then be assigned at most one config from a dropdown. Configure Slack once and assign the same config to every key that should post there, instead of re-entering the webhook URL per key.

A key with no config assigned falls back to the org's legacy defaults (or plain console logging in local development) so nothing silently stops notifying while you're migrating existing keys over.

The four channels

  • Email. Three delivery modes: console(logs the approval link, useful for local development), Enforgate's hosted sender (no setup), or your own custom SMTP server.
  • Slack. An incoming webhook URL; Enforgate posts a Block Kit message with the call details and Approve/Deny buttons.
  • Microsoft Teams. An incoming webhook URL; posts an adaptive MessageCard.
  • Telegram. A bot token plus the chat ID to post into, with an inline approve/deny keyboard.

Turn on more than one channel and a single approval request goes out on all of them in parallel. Whichever button or link gets used first resolves the request; the others just stop mattering.

Use Send test on a config to fire a sample notification through every enabled channel before you assign it to a real key.

Secrets are encrypted, never round-tripped

SMTP passwords, Slack/Teams webhook URLs, and the Telegram bot token are all encrypted at rest (AES-256-GCM). The dashboard never sends a stored secret back to your browser. Edit the config and leave a secret field blank to keep the existing value; type a new value to rotate it.

Custom SMTP, and the Slack/Teams/Telegram channels, are a Pro and Scale feature. On the Free plan, every config is email-only and sends through Enforgate's hosted sender or console logging.

How this fits with approvals

Notification configs only control where the alert goes. Who needs to act on it is a separate layer, see routing approvals to the right personfor approver groups and on-call schedules, which add recipients on top of whatever a key's notification config already sends to.