The dashboard

Alerts & email

An Alert is an email to your workspace's Members when an Issue is filed — the "email me on new issues" you already expect from an error tracker. It arrives after analysis, so it carries the Issue's real title and a summary rather than a stack frame.

When an Alert is sent

One Alert per new Issue. A repeat occurrence that folds onto an existing Issue never re-alerts, which is what keeps a crash loop from becoming ten thousand emails. Each Alert carries a reason:

  • new — this Issue has just been filed.
  • regression — an Issue you had resolved has come back.

Delivery is queued durably and swept after analysis finishes, with a timed fallback so a slow or failed analysis still gets the email out — just with less in it.

Per-project: the alert mode

Each Project sets how much of its activity emails anyone, in its settings. It is the Owner's lever for what a Project sends.

ModeWhat it sends
Regressions (default)Brand-new Issues, plus a resolved Issue that comes back. The setting most projects want.
New onlyBrand-new Issues. A resolved Issue recurring is filed and counted, but sends nothing.
OffThis Project never emails anyone. Everything still lands in the queue.

The delivery sweep reads the mode fresh, so turning a noisy Project down takes effect for Alerts already in flight. There is deliberately no "every occurrence" mode — occurrences fold onto one Issue and never re-alert.

Per-person: where your Alerts go

By default your Alerts go to the email you sign in with. In Settings → Notifications you can send them somewhere else — a shared inbox, an alias, a phone-notifying address — by entering it and following the confirmation link Fixback sends there. An address that hasn't been confirmed never receives anything.

You get one alert address across every workspace you belong to. Your sign-in email is never edited here: that is the identity your sign-in provider proved.

The same section holds your personal opt-out. A Project's mode decides what it sends; your opt-out decides what you receive.

Silencing one Issue

Mute is the per-Issue lever. A muted Issue stays Open and triageable but emits no Alert and drops out of the default queue into the Muted lens. It is shared across the workspace, so muting spares everyone, not just you.

The reporter's email

One more email exists, and it isn't an Alert. When linked work merges and auto-closes an Issue, the person who reported it gets "your report is fixed" at the address they themselves supplied — naming the Project, the Issue, and the page they filed it from. It is informational only: no sign-in links, no dashboard access, nothing they didn't submit. If they gave no address, nothing is sent. See GitHub & the return path.