Alerts

1Add an email rule

On Alerts, enter an address, pick a project or All projects, and tick new issues, regressions, or both. Each rule shows when it last fired and whether delivery worked. Only owners and admins can change this; members can see it.

2New issues and regressions

A new-issue alert goes out the first time a fingerprint is seen. A regression alert goes out when a resolved issue gets a new event, with a note saying whether it came back in the same release or a later one. Snoozed issues skip both.

3Who else is emailed

Code owners whose rule matches the stack trace or URL get a copy. Odoo people in charge get new-issue and regression emails for their company. Nobody is emailed twice for one alert.

4Security thresholds

On the Scale plan the Alerts page also has Security thresholds: how many failed logins, blocked logins or password resets in how many minutes raise a security issue, per project or for the whole workspace. See Security monitoring.

Good to know

• Seats: members, pending invites, email rule addresses and Odoo people in charge share one seat count, deduplicated by email. When a rule would go past the plan's seats you see: '<Plan> includes N seats, and M people would be getting alerts. Remove one, or move up a plan on Usage.' Free has 1 seat, Solo 3, Team and Scale unlimited.
• Email action links (Resolve, Ignore) are signed, expire after 48 hours, work once, and only act when you press the button on the confirmation page, so mail scanners cannot resolve issues by prefetching.
• Security alerts go to your email rules, Slack, Teams and webhooks, or to the owners when there are none; never to Odoo people in charge or code owners.