Overview
The Notifications system keeps you informed about infrastructure events across InfraKitchen. It combines two complementary mechanisms: Subscriptions that control which entities you follow, and Notification Preferences that control how and when you are notified.
Notification Components
| Component | Purpose | Configured by |
|---|---|---|
| Subscriptions | Follow specific resources to receive their events | Any user |
| Notification Preferences | Also receive an event type through external channels such as Slack | Any user |
How Notifications Work
When an event occurs on an entity (e.g., a resource is provisioned, a workflow completes), InfraKitchen:
- Identifies the recipients: users subscribed to the entity (or its project), or, for approval notifications, the approvers and the author of the change
- Delivers the notification in-app to every recipient
- Also delivers it to each external channel (Slack, …) that the recipient’s Notification Preference enables for that event type
If you have linked accounts, notifications are delivered to your primary account.
Approval Notifications
When a resource needs approval — it was created while the approval flow is enabled, or a change, destroy or recreate is waiting to be approved — InfraKitchen notifies the users who can approve it, whether or not they are subscribed:
- Project owners of the resource’s project
- Users with admin permission on the resource or its project
The user who requested the change is never notified. Super admins are only notified when nobody else can approve the resource.
Approval notifications are delivered in-app. To also receive them in Slack, add a preference for the approval_required event type with the SLACK channel.
When the change is approved or rejected, the user who requested it is notified (unless they made the decision themselves); add an approval_result preference with the SLACK channel to receive these in Slack too.
One notification per change
Each change to a resource notifies every user at most once, and never the user who made it:
| Action | Change requester | Approvers | Other subscribers |
|---|---|---|---|
| Edit (needs approval) | — | Approval required | — |
| Edit (applied directly) | — | — | Updated |
| Approve | Your change was approved | — | Approved |
| Reject | Your change was rejected | — | Rejected |
| Destroy (needs approval) | — | Approval required | Destroy requested |
Notification Inbox
Every in-app notification is stored in your inbox:
- The bell icon in the header shows the number of unread notifications. Click it to see the latest notifications, and click one to open the related entity and mark it as read.
- Click View all notifications to open the Notifications page. There you can filter by read state, event type, severity and entity type. Click a notification to open the related entity; unread notifications are marked with a red dot. Each notification has a Mark as read / Mark as unread button, both here and in the bell dropdown.
Notifications are kept for 30 days (configurable with the NOTIFICATION_RETENTION_DAYS setting), then deleted automatically.
Delivery Channels
| Channel | Description |
|---|---|
| IN_APP | Always on. Notifications appear in the InfraKitchen UI and are stored in your inbox |
| SLACK | Opt-in per event type. Delivered to Slack via a configured Slack integration, including the entity’s name, type and a link to it |