How do I set up notifications and recipient groups?

Requires Pro

Quick answer

In the Operations area, create a notification on the Notifications tab (Title, Message, Level) and optionally assign it to a Group. Maintain recipient groups on the Groups tab (name + comma-separated e-mail addresses). Unread notifications are counted by the bell icon at the top of the header bar.

Prerequisites

Operations is part of the Operations module and available from the Pro tier.

Create a recipient group (optional). Open Operations → Groups and click “Add Group”. Give it a name, enter the addresses under Recipients (e-mails, comma) (e.g. it@example.com, ops@example.com) and save.

Screenshot pending betrieb-benachrichtigungen-01 Groups tab in the Operations area with the dialog for creating a recipient group

A recipient group with comma-separated e-mail addresses.
Create a notification. Switch to the Notifications tab and click “Add Notification”. Fill in the dialog:
- Title (required).
- Message (optional) — free text.
- Level (required) — Information, Warning, Error or Success.
- Group (optional) — the recipient group you created earlier.
Screenshot pending betrieb-benachrichtigungen-02 'Add Notification' dialog with Title, Message, Level and group selection

A notification with a level and an optional recipient group.
Read and acknowledge. New, unread notifications increase the counter on the bell icon in the header bar. Opening a notification marks it as read and the counter decreases.

Create a group — POST /api/v1/notification-groups:

curl -X POST https://demo.notory.io/api/v1/notification-groups \
  -H "Authorization: Bearer inv_dein_token" \
  -H "Content-Type: application/json" \
  -d '{ "name": "IT-Betrieb", "recipients": "it@example.com, ops@example.com" }'

Create a notification — POST /api/v1/notifications (group_id optional):

curl -X POST https://demo.notory.io/api/v1/notifications \
  -H "Authorization: Bearer inv_dein_token" \
  -H "Content-Type: application/json" \
  -d '{
    "title": "Zertifikat läuft in 14 Tagen ab",
    "message": "www.example.com — bitte erneuern",
    "level": "warning",
    "group_id": "8b1c…"
  }'

Unread counter and marking as read:

curl -H "Authorization: Bearer inv_dein_token" \
  https://demo.notory.io/api/v1/notifications-unread-count
# → { "unread": 3 }

curl -X POST https://demo.notory.io/api/v1/notifications/7f3a.../read \
  -H "Authorization: Bearer inv_dein_token"

Possible errors: 401 (token missing/invalid), 403 (the Operations module is not in your tier or no write access), 404 (notification not found), 422 (validation).

What happens behind the scenes?

is_read status: Every notification starts as unread. Opening it (or calling .../read) sets is_read = true; the unread counter only counts unread entries for the tenant.
Groups are recipient lists: A group bundles comma-separated e-mail addresses. If a group is deleted, its associated notifications are kept; their group_id is set to null.
Tenant isolation & audit: Notifications and groups belong to your tenant; creating, changing and deleting them is logged.
Link to monitoring: If an alert rule breaches its threshold, Notory automatically creates a notification — this is how technical alerts flow in here.