Notifications
Wisteria sends notifications for approvals, recertification, certificates, and a few other events. Configure delivery at Settings → Notifications.
Three channels
| Channel | Configuration | Required? |
|---|---|---|
| On by default | Required for password reset, certificates — can’t be disabled | |
| Slack | Paste an Incoming Webhook URL | Optional |
| Browser push | Opt-in per learner | Optional |
Email goes out via Resend (Wisteria’s transactional email provider). Sender is noreply@getwisteria.com. If your organisation has an aggressive spam filter, ask IT to whitelist that sender.
You can’t disable transactional email (password reset, certificates) — those are required for the product to function. You can toggle off optional emails (approval-stage reminders, etc.) from this page.
Slack
Wisteria integrates with Slack via Incoming Webhooks — the simplest pattern, no OAuth needed.
To configure:
- In your Slack workspace, create an Incoming Webhook pointing at the channel you want notifications in (
#wisteria-alertsis conventional). Copy the URL. - In Wisteria, paste the URL into the Slack webhook URL field. Save.
- Click Send test to verify a message arrives in your channel.
Wisteria sends to Slack for: course submission, course approval/rejection, escalation reminders.
Browser push
Each learner opts in individually when prompted by their browser. Push notifications use the standard Web Push API with a service worker.
Use cases:
- “You have a new course assigned”
- “A course is overdue”
- “You earned a certificate” (optional)
For super admins: there’s a server-side push endpoint, but Wisteria currently uses it sparingly — push is more useful for learner re-engagement than admin alerts.
Reminders
Wisteria has a built-in reminder cron that fires every four hours:
| Stage | Window | Tone |
|---|---|---|
| First nudge | 4–8h after pending | Gentle |
| Repeat nudge | 24–28h after pending | Reminder |
| Escalation | 48–52h after pending | Escalation flag |
This runs for approvals, recertification windows, and course assignments approaching their deadline. Reminders stop automatically when the action is taken.
You can’t currently configure the cadence — it’s a fixed schedule. Per-workspace cadence overrides are on the roadmap.
What gets notified
| Event | Slack | Push | |
|---|---|---|---|
| Course submitted for approval | Yes (approvers) | Yes | No |
| Step approved | Yes (trainer) | No | No |
| Step rejected | Yes (trainer) | No | No |
| Course fully approved | Yes (trainer + super_admin) | Yes | No |
| Course published | Yes (assigned learners) | No | Yes |
| Course due soon | No | No | Yes |
| Certificate issued | Yes (learner) | No | No |
| Recertification due | Yes (learner) | No | Yes |
| IT handoff completed | Yes (original requester) | No | No |