Skip to main content
Notifications keep you and your team informed the moment something meaningful happens in your Jomioz workspace — whether a resource changes state, a critical event fires, or a system threshold is breached. Jomioz delivers notifications through three channels: email, webhooks, and in-app alerts. You can mix and match channels and subscribe only to the event types that matter to your workflow.

​
Notification Types

Jomioz supports three distinct notification channels. Each channel suits a different use case, and you can enable multiple channels for the same event type.

Email

Receive formatted email summaries for events that require human attention — ideal for on-call alerts and daily digests.

Webhook

Push structured JSON payloads to any HTTPS endpoint in real time. Use webhooks to trigger automated workflows in your own systems.

In-App Alerts

See a live notification badge and feed directly inside the Jomioz Dashboard without leaving your browser.

​
Email Notifications

Email notifications deliver a formatted summary of the triggering event to one or more addresses you specify. Configure them from the Dashboard.
1

Open Notification Settings

Navigate to Dashboard → Settings → Notifications.
2

Enable Email Notifications

Toggle Email Notifications to the On position.
3

Add Recipient Addresses

Enter one or more email addresses in the Recipients field, separated by commas. These addresses receive notifications independently of the workspace notification email set in Workspace → General.
4

Choose Event Triggers

Select which events send an email. You can choose individual event types or use Select All for comprehensive coverage.
5

Save

Click Save Changes. Jomioz sends a confirmation message to each recipient address to verify delivery.
Use a team distribution list (for example alerts@your-company.com) instead of individual addresses so the right people are always notified, even when team membership changes.

​
Webhook Notifications

Webhooks deliver a real-time POST request containing a JSON payload to an HTTPS endpoint of your choice every time a subscribed event occurs. They are the best choice for triggering automated actions in external systems — for example, updating a status page, opening a support ticket, or kicking off a pipeline run. To set up a webhook, follow the First Integration guide or go directly to Dashboard → Webhooks → Add Webhook. You can also register a webhook programmatically with the API:
Every webhook delivery includes a signature header (X-Jomioz-Signature) so you can verify the payload originated from Jomioz. See the Webhooks reference for signature verification instructions and full payload schemas.
Your endpoint must respond with an HTTP 2xx status code within 10 seconds. If it does not, Jomioz marks the delivery as failed and retries up to five times using exponential backoff.

​
In-App Alerts

In-app alerts surface notifications directly in the Jomioz Dashboard without requiring any additional setup. A badge on the Notifications bell icon shows unread alert counts, and clicking it opens the alert feed. Each alert entry displays:
  • The event type that triggered the alert
  • The affected resource name and ID
  • A timestamp
  • A link to the relevant resource detail page
Alerts remain in the feed for 30 days before being automatically archived. You can manually mark individual alerts as read, or use Mark All as Read to clear the feed at once. To adjust which event types surface as in-app alerts, go to Dashboard → Settings → Notifications → In-App Alerts and toggle each event type individually.

​
Event Triggers

The table below lists every event type that can trigger a notification, the channel(s) that support it, and a description of when it fires.
Additional system-level event types — such as quota.warning and api_key.rotated — are available on the Enterprise plan. Contact your account manager for details.

​
Managing Subscriptions

You control notification subscriptions at two levels: workspace-wide defaults and per-user preferences.

​
Workspace Defaults

Workspace-wide defaults determine which event types generate notifications for all members. An admin can configure these from Dashboard → Settings → Notifications → Workspace Defaults.

​
Per-User Preferences

Each team member can override the workspace defaults for their own account. Navigate to Dashboard → Profile → Notifications to:
  • Subscribe to an event type by toggling it on.
  • Unsubscribe from an event type by toggling it off.
  • Pause all notifications temporarily using the Do Not Disturb toggle — useful during maintenance windows or scheduled downtime.
Workspace defaults set the baseline. If an admin enables resource.created email notifications at the workspace level, all users receive those emails unless they individually opt out. If an admin disables an event type at the workspace level, individual users cannot re-enable it for themselves — workspace defaults act as a ceiling, not a floor.

​
Removing a Webhook via API

To remove a webhook subscription programmatically, send a DELETE request with the webhook ID:
A 204 No Content response confirms the webhook has been deleted and will no longer receive deliveries.