Skip to main content
Deliveries send a digest of your governed metrics to email or Slack on a schedule, so the people who never log into Platinur (an owner, an ops lead, a CEO) still hear from it.

​
What a delivery sends

Each delivery digest includes, for every selected metric: its label, its current value, and its month-over-month change (computed from the same trend data shown on the Models page). If a metric has no time dimension, the digest shows the value only. The digest also includes a link back to the Dashboards page for anyone who wants to open Evidence — v1 has no image snapshots or public/unauthenticated links, so the numbers in the message itself are the content.

​
Creating a delivery

Open Deliveries from the Dashboards page head (visible to users who can manage settings). A delivery has:
  • Name — shown in the delivery list and as the email/Slack message subject.
  • Environment — staging or prod (defaults to prod).
  • Metrics — choose specific governed metrics, or leave the selection empty to send all governed metrics (capped at 10 per digest).
  • Cadence — daily, weekly (pick a weekday), or monthly (pick a day 1-28), each at a time in your workspace’s display timezone (Settings -> Preferences).
  • Channel — email (up to 10 recipients) or Slack. Slack reuses the webhook already configured in Configuration -> Notifications; it’s disabled in the form until a webhook is saved there.
Use Send now on any delivery to fire it immediately without waiting for its schedule — useful for confirming a new delivery looks right.

​
How scheduling works

A delivery’s cadence is recomputed on every check rather than relying on a persisted “next run” timestamp, so editing a delivery’s schedule takes effect immediately. If the portal was down at a delivery’s scheduled time, it still sends on recovery as long as that’s within 6 hours of the scheduled time; past that window, the occurrence is skipped (recorded in Monitoring as skipped) rather than sending a stale digest, and the delivery waits for its next scheduled occurrence.

​
Where sends land

Every delivery attempt — success, failure, or skip — is recorded in Monitoring as a delivery run, with the delivery name, channel, and status. Email sends go through Platinur’s own transactional email (no customer SMTP setup required); Slack sends go through the Slack webhook configured in Configuration -> Notifications.

​
Limits

Deliveries are capped at 20 per account, 10 metrics per delivery, and 10 recipients per email delivery.