Notifications

The Notifications tab on the Alerting page provides a centralized view of events and alerts across your Onehouse project. Notifications are delivered through multiple channels and organized by severity to help you monitor your data infrastructure.

Notification Channels

• In-app Notifications: Enabled by default. Cannot be turned off.
• Email Notifications: Who receives them is controlled per rule — see Notification Rules — and can be overridden project-wide, see Email Recipients.
• Slack Notifications: Follow the instructions in the docs to set up the Slack integration, then enable the Slack channel on the rules you want delivered there.

Choosing who is notified

Notification Rules decide who is told about what. A rule names a resource type, the events you care about, the recipients — Project Admins, the person who created the resource, or specific addresses — and the channels to use.

Every project starts with a set of default rules routed to Project Admins, so notifications work without any setup. Edit them, or add your own, under Alerting → Rules.

Email Recipients

Who receives a notification email depends on whether a Notifications Email is configured for the project:

Notifications Email	Who is emailed
Not set	Project admins (project-level notifications) and account admins (account-level notifications, such as API key expiry)
Set	Only the configured address

Setting the address is therefore how you stop notification emails reaching individual admins — point it at a shared distribution list or on-call alias and your team receives everything at one place. Clearing the address restores admin routing.

warning

The Notifications Email overrides notification rules for email. When it is set, every rule's email goes to that one address instead of the rule's own recipients — including any resource creator or specific addresses the rule names. Leave it empty if you want per-rule recipients to apply, and put shared addresses in the rule's Specific addresses instead. See Notification Rules.

Slack and the in-app feed are unaffected by this setting.

To configure it, go to Project Settings → General → Communication Preferences → Notifications Email. It defaults to the project creator's email and can be changed to any valid email address (for example, a team alias like team-alias@company.com).

Only one address is supported — use a distribution list to reach several people.

Severity Categories

Notifications are organized into four severity tabs:

Errors

Critical issues that require immediate attention.

• Flow failed after retries
• Metadata extractor errors
• API key expired

Warnings

Conditions that may lead to issues if not addressed.

• Flow delayed (and subsequent recovery notifications)
• Max OCU limit reached
• API key expiring soon
• Missing records in table

Information

Informational updates about resource lifecycle events.

• Resources created or deleted (Flows, Sources, Databases, Data Lakes, Catalogs, Tables, Users)
• Flows paused or resumed
• Savepoints created
• API key approaching expiration
• First table processed

Recommendations

Suggestions for optimizing your data infrastructure.

• Data skew detected in partitions
• Log file count increased per partition
• Status of table processing updates

Notification Actions

• Dismiss: Archive notifications you have reviewed. Dismissed notifications can be reactivated.
• Activate: Restore previously dismissed notifications.
• Bulk actions: Select multiple notifications to dismiss or activate in batch.

Filtering

Filter notifications by:

• Type — narrow to specific notification categories.
• Lakes — filter by data lake.
• Databases — filter by database.
• Tables — filter by table.
• Sources — filter by data source.
• Creation Date — filter by time range.

Notification Settings

For community edition projects, click the settings icon on the Notifications page to configure thresholds for:

• Data Skew Per Partition — enable or disable alerts and set a custom threshold.
• Number of Log Files Per Partition — enable or disable alerts and set a custom threshold.

Troubleshooting

Some admins are not receiving Flow-failure alerts

If a specific admin is missing alerts:

1. Check the Notifications Email. If one is set for the project, emails go to that address instead of the admins — the most common reason an admin stops receiving them. See Email Recipients. Clear the address to restore admin routing.
2. Check the rule. A rule covering that resource type and event must exist, be enabled, include Email as a channel, and name recipients that include the admin. See Notification Rules.
3. Verify the role. The user must hold the Project Admin role, not just Project Member. See Permissions.
4. Check Slack integration health if Slack is the affected channel — re-authorize the Slack integration if messages have stopped arriving.

If alerts are still missing after these checks, contact support with the project ID, the affected admin's email, and the time window of the missed notification.