Manage Alerts and Notifications
Create a storage alert
With tenant-administrator access, open Admin → Retention & Alerts
(/admin?tab=retention-alerts). In Storage alerts, enter your tenant slug, a
Threshold (% of storage limit) from 1 to 100 and a Delivery channel
(Email with an Alert email address, or Webhook subscriptions), then
select Create rule.
For example, enter 80 to be alerted when your attributed storage crosses 80% of
its limit. A rule fires once when usage crosses the threshold and re-arms after
usage drops back below it. 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. An endpoint whose name resolves to a
private, loopback, link-local, shared (carrier-grade NAT), documentation or
reserved address is refused when you create it and again at every delivery, and
so is a redirect. 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.
Send alerts to Slack
A Slack destination posts each alert as a short Slack message: a title, the key
numbers and a link back. Create an incoming webhook in Slack first and copy its
https://hooks.slack.com/services/... URL. Treat that URL as a secret: Custd
stores it sealed, shows only its last few characters afterwards, and refuses any
other host.
For error, site finding and site outage alerts, add a Slack subscription for the tenant, then choose Slack as the event's channel:
export SLACK_WEBHOOK_URL='https://hooks.slack.com/services/...'
custdctl notification slack add --profile client --company-slug example \
--name alerts --url-env SLACK_WEBHOOK_URL
custdctl notification destinations set --profile client --event error_issue_alert \
--channel slack
The URL is read from the named environment variable, never from an argument.
List, disable or delete a Slack subscription with notification webhooks; it
has no signing secret to rotate. In the browser, the same panel adds one with the
Slack incoming webhook kind.
For a hosted app's item alerts, the item owner posts the URL to
POST /api/v1/app/item/alerts/slack as {"webhookUrl": "..."} and removes it
like a webhook, with DELETE /api/v1/app/item/alerts/webhooks/{webhookUuid}.
Slack deliveries use the same bounded retries and delivery history as webhooks.