Skip to main content

Manage Alerts and Notifications

Create a storage alert​

With tenant-administrator access, open Admin → Retention & Alerts (/admin?tab=retention-alerts). In Create storage alert rule, enter your tenant slug and a positive Threshold (GB), then select Create rule.

For example, enter 10 if a 10 GiB threshold suits your tenant. The form labels this GB but converts it as 10 × 1024³ bytes. Save the returned rule ID, check measured usage in Admin → Storage, and read the evaluated alert feed in Monitoring. A created rule is not proof that an alert has fired or a message has reached a recipient. Missing measurement is not zero usage.

Inspect and retry delivery​

Use an authenticated profile authorized for the tenant and a known delivery UUID:

custdctl notification webhooks list --profile client --company-slug example
custdctl notification deliveries get --profile client --company-slug example \
  --uuid <delivery-uuid>

Replace client, example and the UUID with your own values. Expected result: state, attempt count, timestamps and safe error classes. Recipients and message bodies are not returned. Confirm receipt in your receiving service or mailbox; a sent status alone does not prove a person received or read the message.

After fixing the receiver, explicitly replay a failed delivery:

custdctl notification deliveries replay --profile client --company-slug example \
  --uuid <delivery-uuid> --reason 'Receiver recovered; retry failed delivery'

Read the same delivery again. Replay is audited and reuses the original request. Replay accepts failed or unknown deliveries while their original message data is retained. For webhook deliveries the original subscription must still be enabled; this condition does not apply to email. Unknown means delivery may already have happened: check the receiver before replaying, because the recipient effect could be duplicated. Pending work follows bounded server retries.

Webhook setup and limits​

The CLI provides notification webhooks create, enable, disable, rotate-secret, and delete. Creation requires --profile, --company-slug, --name and --endpoint; inspect --help before a mutation. Replace an example endpoint such as https://hooks.example.com/custd with your actual receiver. Only public HTTPS port 443 is accepted; private destinations and redirects are refused. Store a one-time signing secret in your receiver's approved secret store immediately, without copying it into logs or tickets.

The browser webhook panel currently lives under system-only Admin → Operations. It is not available in tenant-admin navigation. This is a browser self-service gap; the tenant-scoped CLI/API remains the automation path. Do not request system authority to complete a tenant task.