Notifications and Email
Who in your organisation hears about which runs, in the app and by email — set by role, with a switch for each person.
On SynapseOrch Cloud, notifications are routed by role. Owners and admins decide which roles hear about each event, in the app and by email, and each person can turn off what reaches them. Both live under Settings → Notifications.
What the bell is and how a run raises a notification are on Notifications. This page covers what Cloud adds: roles, email, and approvals from scheduled agents.
The events
| Event | What it means | In the app, by default | By email, by default |
|---|---|---|---|
| Needs input | A run is paused until someone answers | Everyone | Owners and admins |
| Needs approval | A scheduled agent wants to run a tool that needs a person's approval | Everyone | Owners and admins |
| Run failed | A run failed or was cancelled | Everyone | Owners and admins |
| Run completed | A run finished | Everyone | Nobody |
| Low balance | Credits fell to 50%, 25% or 10% of the plan | Everyone | Owners |
| Payment failed | A plan renewal could not be charged | Owners | Owners |
| Webhook switched off | A webhook endpoint kept failing for a day and was switched off | Owners and admins | Owners and admins |
| Support replied | Support answered a request you filed | The person who filed it | Never — support's reply already arrives by email |
Payment failed is sent once per failed renewal, not for each retry. Runs keep starting for seven days while the card is retried; update it under Settings → Billing.
For the workspace
The first card is a grid: each event, against each role, in the app and by email. Owners and admins change it and save. Everyone else can read it: Only an admin or the owner can change this.
A rule applies to a role, never to one person. An event you have not changed follows the defaults above. Support replied is not in the grid, because it only ever goes to the person who filed the request.
For you
The second card is your own: Turn off anything that reaches you and you would rather not get. You can switch off any event, in the app or by email, that your role receives. A dash marks a channel your role does not get, and only an admin can change that for the workspace. Your switches change nothing for anyone else.
- The first email about an event goes at once. More of the same event in the next 15 minutes are held and sent together as one email — 3 more: Run failed — which names up to ten of them. The window is yours, per event and per workspace.
- The subject starts with the workspace's name, and the button opens the run, Plan, Billing or Schedules on your workspace's own address.
- The footer says why you got it — your role, and that this event's emails go to that role — and links to Settings → Notifications.
Unsubscribing
Every email carries an unsubscribe link, and the one-click header that mail apps show as a button. The link opens a page that asks first; opening it changes nothing. Unsubscribe turns off that event's email for you in that workspace. The event still reaches you in the app, and you can turn the email back on under Settings → Notifications.
A link from a workspace you have left does not work.
Approvals from scheduled agents
When an agent running on a schedule wants to use a tool that its tool policy says to confirm, it stops and asks in the bell: Daily digest needs approval, the call it wants to make, and why it asks — the tool can modify data in a way that cannot be undone, it reaches systems outside this workspace, or it does not declare what it does.
- Approvers, builders, admins and owners see Approve and Refuse. A viewer reads the question. The schedule's conversation in History answers it too.
- Approve runs the call and the turn carries on: Allowed — the schedule's run carries on. Refuse does not run it: Refused — not run.
- Nobody answers within 24 hours: it expires without running. If the schedule fires again first, the new run replaces the question and the old one expires.
- Afterwards the bell and the history mark it Allowed, Refused or Expired — not run, and it opens its conversation.
- Approving carries on the agent's turn, which spends credits as a chat message does. With no credits left, or a payment past due, Approve is refused with the reason.
- Owners and admins also get it by email (Needs approval), which links to Schedules.
The bell and the history
The bell shows how many are unread and the newest twenty; opening it marks them read — for you, not for anyone else. See all opens Notifications, every one grouped by day. New ones arrive live and show once as a toast.
Notifications are kept in your organisation's database, so a restart or a deploy loses none, and a dropped connection picks up where it left off.