Documentation Index

Fetch the complete documentation index at: https://docs.ironcoaching.app/docs/llms.txt

Use this file to discover all available pages before exploring further.

​

Health Alerts

Health Alerts watch four wearable metrics for each connected athlete and ping you when a data point falls outside their 30-day baseline. Available on Pro and Expert plans.

​

What gets monitored

The alert engine compares each new metric against the athlete’s own 30-day average and standard deviation — not a global cohort. Threshold defaults to ±1.5 standard deviations from their personal baseline.

​

How to enable alerts for a client

1. Open the client’s profile (Clients → pick a client).
2. Switch to the Health tab.
3. Make sure the athlete has shared the relevant metric type with you under Health Data Sharing. Without consent, alerts cannot fire.
4. Scroll to Alert Settings.
5. For each metric, choose:
   • Enabled — toggle on to start alerts firing.
   • Custom threshold (optional) — override the default 1.5σ rule with a fixed value (e.g. RHR > 80 bpm).
   • Email frequency — immediate (one email per alert), daily (8am rollup digest), or off (in-app only).

A coach with no settings rows still receives default behavior: alerts on, daily digest. Configure per-athlete to tune sensitivity.

​

How alerts fire

• After every successful wearable sync (real-time on webhook events from Oura/Withings/WHOOP).
• After manual health log entry.
• Cooldown: one alert per athlete-per-metric per 24 hours, so a single bad night doesn’t spam your inbox.
• A minimum of 7 data points in the last 30 days is required before any alert can fire — gives a stable baseline before triggering.

​

Where alerts surface

• In-app notification bell on every page of the dashboard.
• Health tab of the client profile, top of page (AlertBanner shows recent unread alerts).
• Email — immediate per-alert email or daily 8am rollup, depending on per-metric setting.
• Mobile push — coming via the IronCoaching mobile app.

​

Plan availability

​

Privacy

Alerts only run on metrics the athlete has explicitly shared with you. Toggling consent off in their IronLedger settings instantly stops alert evaluation for that metric — there is no buffering or retention.