Alerts is a reporting feature that enables automated report delivery based on highly configurable scheduling, custom conditions, and dynamic routing of select results to involved team members. A library of Alert templates is available to help you get started.

Those on the Foundations plan cannot create custom alerts but do have access to use Alert templates. Custom Alerts can be configured on the Plus, Enterprise, and Legacy Plus plans:

Alerts allows customized and timely delivery of data that matters to the recipients who matter. Difference detection and dynamic routing automate delivery of this data. A single alert alleviates the need to create many customized report delivery schedules.

We've identified a number of use cases where alerts can be applied immediately. They range from data quality and operational excellence to milestone notifications. You can view a full list of alert templates and some custom alert examples at Alerts Library.

In this example, we create a report that looks at candidates in the recruiter screen stage for 10+ days and set up an alert to automatically notify individual recruiters of only the candidates they are managing. In a matter of minutes, you can set up a single alert with dynamic routing to notify team members of records that are important to them.

An alert can be created for any saved Custom List report. To add a new alert, navigate to Reports > Saved Reports and click on the Custom List report in question, then click the Alerts button.

Once an alert has been added to a Custom List report, you can configure the following:

Under the Send section, you can decide what records you want delivered. This allows for customized focus on details relevant to your particular use case.

Options include:

After selecting what records to deliver, you can select when the alert should be delivered.

After you set your report type and delivery schedule, you can specify the alert's recipients. Ashby Alerts allows standard email or a dynamic routing option to deliver records only to the involved users. You can opt to send individual emails to each specified user as part of the alert, or send a single email including all users who are set as recipients.

You can select who the alert appears to come from: either the generating user (the default) or Ashby, selected from the drop-down.

You can customize the title of the alert and email body. The alert results are inserted inline to the email after any custom message content you add. Once you enter an alert title, the Activate or Lock Report & Activate button turns purple, indicating that the alert can now be activated.

Below is an example of an alert delivery email. In this instance, there are links to the candidate profile, job page, and the underlying Custom List report. There is also a link to view the report in Ashby.

If you prefer that Ashby links (for example, a link to the candidate profile) are not included, toggle off the Include Links to Ashby option within the sender settings. This setting applies only to Ashby links and doesn't affect non-Ashby links (for example, a candidate's social URL). The link to view the report in Ashby is still present within the email.

When adding an alert, the default delivery method is email. If the Slack integration is enabled, you can select Slack.

With the Slack integration enabled, your alert has a Delivery field that lets you select email or Slack. When you select the Slack option, you have two delivery options:

Syncing private channels may take up to 30 minutes after the Ashby app is initially added.

To prevent private channel names from being revealed, type in the exact private channel name when creating your alert.

The results delivered via Slack messages follow a formatting determined by the Custom List report: the first column (often the Candidate) is the top-level element, and the subsequent columns are listed as sub-bullet points. An example of our new hire notification, which incorporates linking to process documents, is shown below.

The saved reports directory has a folder titled Reports with Alerts in which any report with an alert is listed.

The bell icon indicates how many active alerts the report has.

At the report level, the Alerts button shows the number of alerts added to the report. If you hover over the alert count on the Alerts button, it shows the number of active and inactive alerts.

You can click the Alerts button within the report to make changes to exists alerts or add new ones.

Delete an alert by clicking the Alerts button, then selecting the trash icon on the right side of the alert you wish to delete.

Yes; we recommend selecting the 31st day of the month. The alert is sent on the last day of the month, even on months with fewer than 31 days.

For users without access to Ashby, or who are logged out, the candidate profile link from an Ashby alert redirects to your host ATS candidate profile (for example, directly to Greenhouse or Lever). For any Ashby user who is logged in, the candidate profile link in an alert opens the Ashby profile, from which they can view the profile in the host ATS by selecting the View in [ATS] button.

When you select a user field such as recruiter or hiring manager in to users involved as, only records associated with those users are delivered. For example, if you have a custom list report scheduled to send the entire list every Monday, opting to send records to the associated recruiter results in each recruiter seeing the entire list of candidates they are associated with, but no other records.

For recurring alerts (for example, those not set to immediate), Ashby always sends emails to all fixed recipients, regardless of whether the alert and underlying report are empty.

For recurring alerts, to users involved as recipients do not receive an alert when the underlying Custom List report is empty. No one is "involved as" when the record set is empty.

Yes! Both email alerts and alerts in Slack support attaching the results as a CSV file. When setting up your alert or editing it, select CSV from the Attach dropdown within the Advanced section.

If the attachments exceed the platform's limits (10 MB for email, 1 GB for Slack), they are not attached, but the normal message is still sent.

Alerts can only be configured for Custom List reports. If you have a dashboard with reports that you'd like to send out to users on a regular basis, check out Scheduled Dashboards.

Currently this isn't possible. You can include the candidate profile URL in your custom list report details, though, so the candidate profile is easily accessible from the report. Users need access to the job, department, team, or location the candidate is linked to in order to view the profile.

Alerts sent to Slack support limited markdown formatting. You can format alerts sent to Slack with hyperlinks, bold, italic, and headings.

Report alerts configured to send on added or removed rows trigger on any added or removed row, regardless of the reason. Some common causes of unexpected alerts are:

When the user who enabled a report alert is deactivated in Ashby, the alert stops sending. Because report data is generated using the enabling user's account permissions, Ashby pauses delivery when that account is no longer active. This keeps sensitive data secure.

To keep your alerts running, any active user with sufficient permissions can reassign an alert before the departing user's account is deactivated:

We recommend completing this before the departing user's last day to avoid any interruption in alert delivery. If the departing user had locked any reports, any Organization Admin can unlock them. For more information, see Confidential Reporting & Content Access Control .