How to Set Up Run Notifications in Manta

Runs take a few minutes to half an hour. Notifications mean you can start one and get back to work, and hear about it when it matters.

What you get notified about

Manta notifies you when a run completes and when a run finds issues — in the dashboard's notification feed and by email to the address on your account. The "issues detected" notification is the high-signal one: it only fires when there's something to look at.

[Screenshot: the in-app notification feed showing a completed run with a findings count]

Step 1 — Check your notification settings

Open the notifications section in your account or project settings and confirm what's enabled. If it offers a choice of which events notify you, keep issues detected on; turn run completed on too if you tend to start a run and step away.

[Screenshot: the notification settings screen]

Step 2 — Confirm email is arriving

Start a quick test run and confirm the email arrives — check your spam folder on the first one and allowlist the sender, so you're not relying on a channel that's silently misconfigured.

[Screenshot: an example notification email showing a completed run with a findings count]

Step 3 — Set a team convention

If several people share a project, decide who's on the hook for acting on a notification — otherwise everyone assumes someone else has it. Pair this with the triage ownership from organizing your team.

Tips and common mistakes

• On a high-frequency project, lean on "issues detected" — if every completed run pings you, you'll start ignoring them and miss the one that mattered.
• Check your spam folder on the first email and allowlist the sender.
• A notification is a prompt to review the run — not a substitute for it.

What to try next

• How to Review a Run — what to do when a notification says issues were found.
• Continuous testing — keeping the feedback loop tight.

Start free.