Alerts and Notification Preferences
How financial alerts differ from platform operational alarms.
Limitation
CoreFinOps may provide tenant-facing financial notifications and bounded email digests as part of the approved commercial hardening work. They are distinct from internal CloudWatch/SNS operational alarms used to monitor CoreFinOps infrastructure.
Notification categories
Supported or planned triggers include selected cost governance findings, operational dual-run/decommission conditions, and important account/billing status changes. Whether a category is available depends on the deployed release and the workspace's plan.
Preferences and delivery
An authorized user should be able to control supported notification preferences and unsubscribe from optional email communications. A queued email is not proof of delivery; provider acceptance, bounces, complaints and suppression should remain observable to the sending system.
Cost and privacy controls
Per-tenant quotas, deduplication, bounded retries and a low-cost email outbox prevent repeated alerts from becoming an uncontrolled operating cost. Never include raw AWS credentials, secrets, payment tokens or unnecessary financial exports in an email.
What this page does not promise
Do not describe SES production sending as active until domain validation, sandbox exit and delivery testing are proven in the deployed environment. When email is not configured, rely on visible in-product status and configured support routes.