Notification channels are the delivery targets for TigerTrust alerts — expiry warnings, revocations, workflow failures, anomaly detections, and TPM attestation failures. You configure channels once and reference them in alert rules, escalation policies, and workflow steps.
Notification Channels

​
Channel types

TypePurpose
EmailSMTP or transactional email to a recipient list
SlackSlack Incoming Webhook
TeamsMicrosoft Teams Incoming Webhook
PagerDutyPagerDuty Events API v2
WebhookGeneric HTTP POST with HMAC signature
SMSOutbound SMS via Twilio
OpsGenie is supported through the generic webhook type using OpsGenie’s inbound integration URL.

​
Set it up

Create an Incoming Webhook in your Slack workspace. Go to Settings > Notifications > Add channel, select Slack, and paste the webhook URL. Enter an optional channel override and display name.TigerTrust sends a rich block message with title, severity color, and a link to the alert.

​
Test a channel

Every channel has a Send test button in Settings > Notifications. Clicking it sends a synthetic alert through the full delivery path. A successful test confirms the channel is ready for production use.

​
Escalation rules

Route alerts to specific channels based on severity and resource type. Go to Settings > Notifications > Escalation Rules and click New rule. Set the matching conditions (severity, resource type), the primary channels to notify, an escalation delay, and the secondary channels to notify if no acknowledgement arrives within the delay. Example: route critical alerts on CA resources to the PagerDuty on-call, and if no acknowledgement arrives within 15 minutes, also page the CTO channel.

​
Delivery order

For each alert, TigerTrust resolves the notification destination in this order:
  1. Channels explicitly referenced in the alert rule
  2. Escalation rules that match the alert’s severity and resource type
  3. Workspace default channel (configured in Settings > Notifications > Defaults)
Generic webhook targets receive an HMAC-SHA256 signature in the X-TigerTrust-Signature header. Always verify the signature on your end before trusting the payload — an unverified webhook endpoint is a security risk.

Alerts

Configure alert rules and severity thresholds.

Webhooks

Full webhook signing and retry behaviour.

Notifications

Templates, escalation policies, and channel management.

Workflows

Trigger automations from alerts, not just notifications.