Notifications & Slack routing
Connect Slack and choose, per event type, where notifications go: Slack channel, in-app bell, email.
- Every event type has its own routing — no firehose channel
- Create Slack channels and send test messages without leaving the page
- Learner-facing events (reviews, admissions, feedback) reach the in-app bell automatically
Notifications & Slack
Admin → Notifications wires platform events to the places your team watches.
Connect Slack
Create a Slack app with scopes chat:write, channels:read, groups:read and (optionally, to create channels from here) channels:manage. Install it, then paste the bot token (xoxb-…). Miatz verifies it, connects, and loads your channel list so routing uses dropdowns instead of typos. From the same card you can create a channel, send a test message, disconnect, or flip the global Slack enabled switch.
Route every event
Events are grouped by category — Access, Learning, Quality, Support, Admissions & Mentoring, General. For each event type choose:
- Slack channel — where the message posts (remember to /invite the bot into it).
- In-app — whether the learner's bell shows it (applies to learner-facing events like bug reviewed, mentor feedback, admission decisions).
- Email — whether the admin address is emailed too.
Save per row; changes apply immediately.
Good defaults
Point noisy quality events (bug reports, reviews) at a triage channel, admissions at the program channel, and support tickets somewhere someone actually watches. The Bug Board can additionally post a consolidated daily digest to Slack each morning.
The journey, step by step
| Step | What you do | What you get |
|---|---|---|
| Connect Slack | Paste your Slack app's bot token (xoxb-…) and verify | The workspace connects and your channel list loads |
| Prepare channels | Create a channel or send a test message from the page | You confirm delivery before routing real events |
| Route each event | Per event type, pick a channel and toggle Slack / in-app / email | Bug reviews, admissions, support tickets and more land where your team works |
| Invite the bot | /invite the bot into each channel you picked | Messages actually deliver — a picked channel without the bot stays silent |
Frequently asked
What does my Slack app need?
Scopes chat:write, channels:read, groups:read and (to create channels from miatz) channels:manage. Install it to your workspace, then paste the bot token — it's verified before saving.
Who sees what?
Slack messages go to your team's channels. In-app notifications go to the learner's bell for learner-facing events (bug reviewed, mentor feedback, admission). Email additionally notifies the admin address when enabled.
Why isn't a routed event arriving in Slack?
Most often the bot isn't in the channel — /invite it. Also check the global 'Slack enabled' toggle and the last-action status shown on the connection card.