These are alerts on Insights metrics. They're separate from KPI alerts in Resources, which watch one person's scheduling numbers, and from the alert levels on prepaid hours in Agreements, which tell you when a block's hours are running out.
An alert watches one metric and tells you, and anyone you choose, when it crosses a line. You don't have to keep a dashboard open to notice that money owed past 60 days just went over $20,000.
Who can set one#
You need Create alerts on metrics. Admins and managers have it by default; an administrator can give it to other roles under System → Roles. Insights must be switched on.
You can alert on any metric you can see yourself, and the alert always reads the number as you see it: the same clients, projects, boards and people your own dashboards show you.
Creating an alert#
Open Insights → Alerts and choose New alert:
- Name — what the notice will say, e.g. "AR over 60 days".
- Metric — any metric from the metrics catalog, with its usual settings (the period, whose work, and so on).
- Filters — only for metrics that follow them: narrow to particular clients, projects, people or teams, just like a dashboard's filter bar.
- Condition: - Is above, is at or above, is below, is at or below, or is outside a range (a low and a high value). - Rises by more than or falls by more than a percentage on the previous period. Only metrics with a period offer these. - For N periods in a row: for metrics with a period, the earlier periods must have crossed too. "Utilization below 70% for 3 weeks in a row" ignores a single slow week.
- Which rows — choose Check now to see the number right now and whether the alert would fire. For a metric with rows (by board, by age, by client…), you can watch only some rows, e.g. "money owed 61–90 days and 90+ days late". Otherwise it watches the total.
- Tell — yourself (on by default), plus any people and roles. See who gets told.
- Repeat — only when it first crosses, or again every day or every week while it stays over. You can also be told when it's back to normal.
Check now tells no one; it only reads the number.
Adding a task or opening a ticket#
Under Also do, an alert can also:
- Add a task to a project: in a project you can add tasks to, named from the alert, assigned to you, someone else or no one, due in a set number of days if you like.
- Open a ticket: an internal ticket on a board you can open tickets on, with the board's default status, the priority you pick (or the board's default) and an optional assignee. It has no client or contact, so nothing about it emails anyone outside your organization.
Both happen only when the alert goes over the line, never when it's back to normal, and once per crossing: an alert that reminds people every day still makes one task. The name or subject can use {alert}, {metric}, {threshold} and {date}.
The task or ticket never includes the number. Anyone who can open that project or board can read it, and they may not be allowed to see the figure. It says which alert crossed, what it watches and its line. People the alert tells can follow its link to see the number as they see it; anyone else can open the metric on a dashboard.
If you can no longer add tasks to that project or open tickets on that board (or someone it's assigned to can no longer open it), the alert pauses and you and the admins are told why, the same as when you lose access to its metric.
Posting to Slack or Teams#
Under Also do, an alert can also post to a channel: a short Slack or Teams message with the alert's name, the line it crossed, the number and a link to the alert.
- You need Email reports outside the organization. A channel is an audience outside AspirePro's permissions, like an outside email address. It's only offered when an admin has connected a channel under System → Integrations → Slack and Teams; channels marked "Anyone who schedules reports may post here" are offered to everyone, and admins can pick any.
- It shows your number. Everyone in the channel sees the same message, so it carries the number as you see it, and says so at the bottom. It isn't offered for profitability, pay or cost metrics, or for a saved report: those figures never go to a channel.
- It posts once per crossing, only when the alert goes over the line, not when it's back to normal. A retry, or a check that runs twice, never posts twice.
- If it can't post, the alert keeps running. When the channel has been switched off or removed, or you've lost Email reports outside the organization or the right to use that channel, nothing is posted, the run notes say why, and you're told once. The notices to people still go out, and the alert does not pause.
How often it checks#
- Metrics for right now (open tickets, money owed, unbilled work…) are checked every hour.
- Metrics over a period (this month's revenue, last week's utilization…) are checked once a day, after 7:00 in your organization's time zone.
An alert tells people when the number crosses the line, not every time it's checked while it stays over (unless you chose to repeat). If a metric has no reading (for example nothing to measure yet), nothing fires: a missing reading never counts as zero.
Who gets told#
Notices arrive in AspirePro's notifications, under Insights. They're sent straight away by default; each person can change that under Account → Notifications.
An alert can tell up to 25 people who aren't admins, by name or by role. Roles are read each time the alert sends, so a new member of a role is included.
The number is only ever told to people who'd see the same number themselves. People's access differs: someone who sees only some boards, projects or pipelines may see a smaller number for the same metric. So:
- When you save, you can pick anyone who can see the metric. Someone who'd see a different number than you is listed when you Check now, and named again when you save: they'll be told the alert triggered, but not the number. Someone who can't see the metric at all is refused, and you're told how many.
- Each time it sends, everyone is checked again. Anyone who'd see a different number (named that way, or whose access narrowed since) gets a notice without the number: "an alert you're on was triggered". They get it only when their own number has crossed too, so it tells them nothing they couldn't see already. Opening it shows the alert with the number as they see it.
- People who can no longer see the metric at all, and anyone left inactive, aren't told. The alert's list of times it crossed says how many.
Admins are checked the same way: some things, like other people's private activities, stay private even from admins, so an admin can see a different number too. On an alert's page, everyone except its owner sees the number as they see it.
The alert page#
Insights → Alerts lists your alerts (admins see everyone's), with each one's state: Over the line, Normal or Paused, the last value and when it was last checked. Open an alert to see the times it crossed the line (and came back, if you asked to be told): when, whether the notice went out, and notes such as how many people weren't told. A check that changes nothing isn't listed; the last check's time and value are at the top.
A person an alert tells can open it from their notice, even without Create alerts on metrics. They see the alert and their own number, but can't change it.
Pausing, ownership and changes#
- Pause stops the checks and the notices; Resume (or saving it again) starts them, after checking everything again.
- An alert pauses itself when its owner can no longer see what it reads: they lose the metric or a project or person it's filtered to, or they're made inactive. The owner and the admins are told why. It never keeps checking with access its owner no longer has.
- Each alert has an owner: whoever created it. Admins can change or delete any alert; when an admin edits someone else's alert, Tell its owner is the owner's notice, not theirs. If someone else changes what it watches (the metric, its settings, filters or condition), they become its owner, because the alert reads the number as its owner sees it. Renaming it or changing who's told keeps the owner.
Asking Prox#
Prox, and AI assistants connected to AspirePro, can set alerts for you: "tell me when open tickets on the Support board go over 40". It's the same alert, with the same checks, and it shows up on the Alerts page. Prox can't add or remove a channel post (posting outside your organization is a choice you make on the Alerts page), but changing an alert keeps the one it has, as long as you could post to it yourself.