Infrastructure
Communication
How Infraova delivers alerts, proposals, and notifications to the right person at the right time — email, Slack, and approval notifications.
Why communication is part of the infrastructure layer
Infraova detects problems and generates proposals autonomously. But proposals require a human decision before anything changes. Communication is the bridge between Infraova's detection and your approval — it makes sure the right person knows a decision is needed, with enough context to make that decision without logging in and searching.
Alert email
When Infraova detects a new issue, it sends an alert email to the configured recipients. The alert includes the domain affected, the issue type, the severity level, and a direct link to the issue in Infraova. Critical issues trigger immediate alerts. Warning-level issues are batched into a digest to avoid noise. Alert recipients are configured per organization in the notification settings.
Slack notifications
If your team works in Slack, Infraova can post notifications to a designated channel. Slack notifications follow the same severity logic as email alerts — critical issues post immediately, warnings are batched. The Slack message includes the domain, the issue, the severity, and a link to the proposal if one exists. Connect Slack from Settings → Notifications.
Note
Slack and email notifications are independent. You can enable both, either, or neither. Most teams use Slack for real-time awareness and email as a fallback.
Approval notifications
When Infraova generates a proposal that requires approval, a notification is sent to operators with approval authority. The approval notification includes the proposed change, the affected domain and client, the expected outcome, and a direct link to the approval screen. Approval notifications are always sent immediately — they are never batched, because a proposal waiting for approval may be time-sensitive.
Operational alerts
Infraova also sends operational alerts for events that are not issues in the traditional sense — a connection that has gone unhealthy, a verification that failed after a remediation, a provider API that is returning errors. These alerts are sent to organization owners and administrators. They are distinct from domain issue alerts because they affect your ability to monitor and operate, not just the health of a specific domain.
Notification preferences
Notification preferences are configured at the organization level. You can set which severity levels trigger immediate alerts vs digest batching, which channels receive which types of notifications, and which team members are included as recipients. Individual team members can also configure their own notification preferences within the bounds set by the organization.