Notifications¶
DV Forge tells you when something needs your attention on a signature you care about: it was assigned to you, it regressed, a rule flagged it, or a root-cause run finished. Notifications appear under the bell at the top of the sidebar, next to your profile picture. This page lists what notifies you, how to get (or stop getting) notifications, and how to read and clear them.
Notifications are in-app only today. Email and chat delivery aren't available yet.
What notifies you¶
| Event | Who is notified | Notification title |
|---|---|---|
| A signature is assigned to you | The new assignee, unless they assigned themselves | Assigned to you: signature title |
| A signature regresses (hit again after it was resolved) | Its assignee and everyone watching it | Regressed: signature title |
| A triage rule's Notify action | The recipients chosen in the rule: the assignee, everyone watching, or named members | Rule name: signature title, with the rule's message if it has one |
| A root-cause run finishes with a hypothesis | Whoever launched the run, the signature's assignee, and everyone watching it | Root-cause hypothesis ready: signature title |
| A root-cause run fails | Whoever launched the run, the signature's assignee, and everyone watching it | Root-cause run failed: signature title |
Rules that assign someone notify them the same way a person assigning them would.
Comments, label changes and status changes made by others don't send notifications. Follow those in the signature's activity timeline.
How to get notifications for a signature¶
You hear about a signature when you're its assignee or one of its watchers. You become a watcher when you:
- select Watch on the signature, or Watch in the queue's bulk toolbar,
- are assigned to it, or
- comment on it.
To stop, select Stop watching on the signature (or Unwatch in bulk). Watching works for every role. See Working a signature.
Read and clear notifications¶
The bell shows how many unread notifications you have. Select it to open the list of your latest 30.
- Select a notification to open its signature. That also marks it read.
- Mark read marks one notification read without opening it.
- Mark all read clears every unread notification.
The bell checks for new notifications every 60 seconds, and again when you return to the browser tab.
You only see notifications from organizations you still belong to. If you leave an organization, its notifications are hidden, and DV Forge stops sending you new ones from it.
Notifications through the API¶
Notifications belong to a signed-in person, so these endpoints need a user session; API tokens can't use them.
# Your latest unread notifications
curl -s "https://api.daruur.cloud/v1/notifications?unread_only=true&limit=50" \
-H "Authorization: Bearer $TOKEN"
# Mark some read (up to 500 ids), or all of them
curl -s -X POST "https://api.daruur.cloud/v1/notifications/read" \
-H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
-d '{"all": true}'
The list returns items (newest first) and unread, the total unread count.
Each item has a kind (signature.assigned, signature.regressed,
rule.notify, signature.agent_complete or signature.agent_failed), a
title, an optional body, the signature_id, and read_at.