Notifications

Midstream tells you when something you care about happens — a scene was captured, a deploy failed, somebody commented. This page covers what it can tell you, where the switches are, and what happens when your choice and your workspace's default disagree.

There are two places to look:

• Account → Notifications — your own choices, set separately for each workspace you belong to.
• Workspace settings → Notifications — the defaults everyone in the workspace starts from.

Channels

Two more channels are on the way: Slack, as a direct message through the Slack integration Coming soon, and a webhook channel that delivers your own notifications to a workspace endpoint rather than to you Coming soon. That second one is not the same feature as outbound webhooks — see the end of this page.

Events

Every event can be switched on or off per channel. These are the built-in defaults you start from:

"Scene captured" is the one deliberately quiet by email. A test suite that marks forty scenes captures forty on every push, and nobody wants that in their inbox. Switch it on if your suite is small enough for it to be useful.

Notifications go to every member of the workspace for whom that event and channel resolve to on. They are not narrowed to the people involved in what happened, so a workspace-wide default that is on really does reach everyone.

How a setting resolves

Three layers, checked in order. The first one that has an answer wins:

1. Your choice, for this event and channel, in this workspace.
2. Your workspace's default for that same cell.
3. The built-in default in the table above.

Two consequences worth understanding before you change anything.

Changing a workspace default moves everyone who has not chosen for themselves. That is the point of it — an owner switching "Deploy failed" email on gets it to the whole team without asking each person. But it does mean the blast radius is larger than the one page you are looking at. People who have made their own choice for that cell are untouched.

Choosing the value you would have inherited anyway is the same as not choosing. If the workspace default for a cell is off and you switch it off, Midstream clears your override rather than storing "off". You go back to inheriting, so a later workspace change reaches you. To pin a value against future workspace changes, it has to differ from the current default. Workspace defaults behave the same way against the built-in defaults.

Reset to workspace defaults on your account page drops every override you have in that workspace at once, and you inherit everything again.

What you cannot turn off

Two kinds of message ignore the grid entirely:

• A workspace invitation. The invitee is not a member yet, has no preferences to consult, and the email is the only thing that gets them in.
• Anything required to get into your own account. Access to your account cannot depend on a switch you might have flipped off six months ago.

These are transactional, not announcements: they are sent because you or someone else took an action that needs a reply, not to keep you informed. They go through exactly the same delivery path as everything else — there is no separate back door that skips your preferences — they are just marked as mandatory.

Everything in the events table is optional. If it is not in that table, it is one of the two above.

Two different webhooks

The word appears twice in Midstream and means different things.

If you want capture.created in your own systems with a signed payload you can verify, that is Webhooks, and it works today.