Alerts, reports and billing
Operational views expose recorded facts, with explicit boundaries for external services.
Alerts
Owners/admins manage rules; permitted organization members can read them. Rules can be enabled/disabled and have recorded delivery attempts.
Slack delivery is implemented for allowed Slack incoming-webhook destinations. Email alerts are not available in this release and cannot be selected for a new alert. Existing email rules do not establish working email delivery. A Slack Test action can send an external notification.
- Invalid-signature streak: checks consecutive verified events with invalid results, optionally for a source.
- Quota threshold: compares current-month usage with the configured plan’s capture limit.
- High error rate: computes invalid signatures among checked signatures in the selected window, not destination HTTP failures.
Activity reports
Billing can download a PDF activity report. Current calendar month, rolling 30 days and 24-hour sections are labeled separately. A report is a snapshot of loaded organization activity; failed data retrieval should not be interpreted as zero activity.
The report is generated for the selected organization. It does not contain a provider payment ledger or certify processing at the webhook destination.
Billing
The interface shows the configured plan and usage. Subscription invoices are a placeholder until billing is enabled. No in-app checkout, payment-method update, trial purchase or automatic overage billing is available.
Displayed plan prices and limits are informational UI configuration, not an independently verified commercial offer. Ask the deployment operator about the applicable arrangement.
Audit
Permitted readers can inspect recorded actions, including source changes, replay acceptance and content reads. Audit entries and delivery history describe different stages. A queued action is not evidence of successful notification or business effect.