Notifications
When you get pinged and how to tune your notification preferences.
TestKase sends notifications for a focused set of accessibility events so your inbox doesn't fill up.
When you get notified
| Event | Who gets notified |
|---|---|
Your scan finishes (completed) | Scan creator |
Your scan fails (failed) | Scan creator |
| You're added to an accessibility team | The new member |
| You're removed from an accessibility team | The removed member |
Nothing is sent when a scan is shared with a team, and nothing is sent to team members when someone else's scan finishes.
Every run counts, including scheduled ones. The completed/failed email fires once per run, not once per scan — so a scan on a daily schedule emails its creator every day, and there is no per-scan mute. If the volume is unwelcome, change the schedule; see Managing scans.
A scheduled run that cannot start because the organization no longer has an Automate plan is recorded as a failed run and sends the failure email, with the plan requirement as the error message.
Channels
Accessibility events are delivered by email only — they do not appear in the in-app notification bell, and there is no per-scan muting or unsubscribe toggle for them yet.
Everything goes to the address on your TestKase account. The scan emails go to the scan's creator — not to whoever is on call, and not to the team the scan is shared with.