WDYT@bpmct@DanielleMaywood think about disabling this notification by default?

I'm in two minds about this:

• If an operator is unhappy about the volume they could always disable it when/if it becomes an issue.
• We should aim to have nice defaults, so disabling it by default avoids this unhappy path.

I'm a big fan ofPrinciple of Least Surprise. I think for existing customers who upgrade to a more recent version and now start getting hundreds of emails they didn't expect violates that principle.

Hey folks - apologies for the confusion here. Let's disable this notification by default both for users and admins. In fact, we should probably not make it available for users to configure. The second point is less important to me, but I just can't think of a good use case for it.

Some of these notifications are really interesting from a webhook POV (fails, creates/updates to an external system) but emails themselves with no filtering would create a lot of spam.

Let's disable this notification by default both for users and admins.

Sounds good 👍 thanks@bpmct - and no need to apologise!

In fact, we should probably not make it available for users to configure.

Fortunately, regular (unprivileged) users will only be able to modify their own workspaces, and we're now inhibiting these notifications if the initiator is owner of the workspace; so we won't have to build in this out.