Configure and receive Crashlytics alerts by email or in-console

Firebase can send a variety of defaultCrashlytics alerts (see thealerting overview page).Firebase can send all defaultCrashlytics alerts to your email.Forregressed issues andincreasing-velocity issues, Firebase can also showalerts in theFirebase console.

  • Alerts forregressed andtrending issues do not require any configurationand aresent by default when you set upCrashlytics.

  • Alerts for newnon-fatals,fatals,ANRs, andincreasing-velocity issues arenot sent by default. To receive thesealerts, you must (at minimum) select your preferred alerting channel.

All alert types offer some configuration. For example, you can turn alerts onor off for your own account, and forincreasing-velocity issues, you can setthresholds for when alerts are sent. You can view and configure these alerts intheAlerts tab in theFirebase console.

Note: Alerts for increasing-velocity issues (calledvelocity alerts) are amore complex type of alert. Find detailed information aboutconfiguring velocity alerts later on this page.


The rest of this page describes in detail how to configure various options fordefaultCrashlytics alerts.

Receive alerts by email and in-console

Only specific project members can receive alerts, and you can turn on or offalerts for your own account.

By default, every project member (who has the required permissions to receivealerts) will get an email forregressed issue alerts and an email plus anin-console alert fortrending alerts. All other alerts must be configured foryou to receive them by email or in-console.

Required permissions to receive alerts

To receiveCrashlytics alerts by email or in-console, you must have thefirebase.projects.update permission. The following roles include this requiredpermission by default:Firebase Admin or projectOwner or Editor.

Turn alerts on or off for your own account

For your own account, you can turnCrashlytics alerts on or off withoutaffecting other project members. Note that you still need the requiredpermissions to receive alerts.

  1. Sign in to theFirebase console, then select your project.

  2. Click, then selectProject Settings.

  3. Select theAlerts tab.

  4. Go to theCrashlytics alerts card, and then select the alert thatyou want to configure (for example,Velocity Alerts).

  5. Set your account preference for that alert.

Configure alert settings

To configure the settings for an alert, you must have thefirebasecrashlytics.config.update permission. The following roles includethis required permission by default:Firebase Crashlytics Admin,Firebase Quality Admin,Firebase Admin, orprojectOwner or Editor.

  1. Sign in to theFirebase console, then select your project.

  2. Click, then selectProject Settings. Select theAlerts tab.

  3. Go to theCrashlytics alerts card, and then select the alert thatyou want to configure (for example,Velocity Alerts).

  4. Configure the settings for that alert.



Configure velocity alerts

Use velocity alerts to notify your team when any individual issue is causing anurgent problem in your app. ForCrashlytics, an issue is a grouping ofsimilar crashes or application not responding (ANR) events.

Important: To get velocity alerts,make sure your app usesat minimum the following versions of theCrashlytics SDK:
Apple platforms: v10.8.0+ |Android: v18.6.0+ (BoM v32.6.0+) |Flutter: v3.4.5+ |Unity: 11.7.0+

What triggers a velocity alert?

Velocity alerts are triggered when an issue in your app crosses certainthresholds that youconfigure in theFirebase console.

You define the threshold for velocity alerts in terms of apercentage of users and the minimum number of users that wereimpacted by the crash or ANR. You can set the percentage threshold valuebetween 0% and 100% of sessions. The minimum users threshold can be set to anynumber greater than or equal to 10. By default, the velocity alert threshold isset at 1% of sessions and 25 users.

Specifically, an alert is triggered if, during a 30-minute time period,all the following are true:

  • An issue in an app exceeds the defined percentage threshold and exceeds theminimum users set for that app.
  • The app has at least 10 users in that time period.
  • There was no alert previously raised for the issue in the app on thatversion.

Configure velocity alert thresholds

To configure velocity alert thresholds, you must have thefirebasecrashlytics.config.update permission. The following roles includethis required permission by default:Firebase Crashlytics Admin,Firebase Quality Admin,Firebase Admin, orprojectOwner or Editor.

Configure velocity alert thresholds for each of your registered apps. Each appcan have a different alert threshold.

  1. Sign in to theFirebase console, then select your project.

  2. Click, then selectProject Settings.

  3. Select theAlerts tab.

  4. Go to theCrashlytics alerts card, and then select theVelocity Alerts tab.

  5. Configure the alert thresholds for the app.

Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2026-02-18 UTC.