Notifications
How hiring events reach you — in-app, email, Slack, and direct messages — and how to set up each channel.
Notifications
Notifications keep you informed about hiring activity: a candidate starts, submits, or completes an assessment; the integrity analysis is ready; an assessment is activated; or your wallet is running low.
The same events can reach you in several ways. This page explains each channel, who sets it up, and where to change what you receive.
How a notification reaches you
| Channel | Who sees it | Set up by |
|---|---|---|
| In-app — the bell in the header | Each person's own list | Automatic; toggle per event in Events |
| Each person's own inbox | Automatic; the most important events | |
| Slack — organization channels | Everyone in a shared channel | Connected once for the workspace |
| Slack / Microsoft Teams — direct messages | Only you, in your own Slack/Teams | You link your own account, after the app is connected |
In-app is the baseline and is always available. Email covers the most important events. Slack and Teams are optional chat integrations; the sections below cover their setup.
Slack and Microsoft Teams
Both are supported. Slack is available first; Microsoft Teams becomes available in your workspace once your QualifyCode contact enables it. Everything on this page applies to both — wherever you read Slack, Teams works the same way.
How it fits together
A single event can fan out to several places at once. The workspace's shared channel and your personal direct messages are independent: turning one off never affects the other.
The Notifications page
Open Notifications from the sidebar. There are two tabs:
| Tab | Who sees it | What it holds |
|---|---|---|
| Events | Everyone | Your personal channels and the event list you can tune |
| Integrations | Workspace admins | Connect Slack and Microsoft Teams for the whole workspace |
Admins see both tabs; everyone else sees Events only.
The Events tab
At the top are your personal cards — Your Slack (and Your Teams, when available) — where you link your own account for direct messages.
Below them is the event list (the matrix). Each row is an event; each column is a place it can be delivered:
| Column | What it controls | Available to |
|---|---|---|
| In-app | The bell in the header, and your personal feed | Everyone |
| Direct message | A private Slack/Teams DM to you | Everyone, once you link an account |
| Slack | A post to the workspace's shared Slack channel | Admins only |
Each column has a per-event switch and a master switch at the group and "all events" level. Turn a column off to stop that event reaching that place.
Critical events stay on
A few events — such as a low wallet balance — cannot be fully muted, because missing them can interrupt candidate assessments. Their switches are shown locked on.
Set up the workspace app
Admins connect Slack and Microsoft Teams from the Integrations tab (Notifications → Integrations). If you are not an admin and the workspace has not connected yet, you can do the one-time connect from the Your Slack card on the Events tab instead (see below).
Open the Slack card and choose how to connect:
| Route | What it does | What it can reach |
|---|---|---|
| Connect with the Slack app | Standard install. Authorize the workspace once. | Post to any channel you pick, and enable direct messages to individuals |
| Use an incoming webhook | Minimum permissions. You paste a single channel's webhook. | Post to that one channel only — no direct messages |
The Slack app is recommended when you want members to receive direct messages; the incoming-webhook route is a lighter option for a single shared channel.
Direct messages need the Slack app
Personal direct messages need the workspace Slack app installed first. The incoming-webhook route cannot send a direct message, because a webhook belongs to one channel, not to a person.
After connecting, the Slack card lists the destinations (channels or webhooks) and lets you add or remove them. Use Send test to confirm delivery, and Disconnect to remove the whole connection.
Set up your own direct messages (everyone)
Once the workspace's Slack app is connected, each person links their own account so private events reach them as direct messages:
Wait for the workspace app (or ask for it)
Personal direct messages need the workspace's Slack app. If it is not connected yet, the Your Slack card tells you so — you can connect it yourself, or use Request an admin to connect Slack, which notifies your admins that someone is waiting.
Link your account
In Your Slack, click Connect my Slack and approve the request in the Slack window that opens. When it closes, your account appears in the list.
Choose your events
In the event list, use the Direct message column to pick which events DM you. Changes save immediately.
Your direct messages are private to you. They are separate from the workspace's shared channel and never post to it.
Linking is personal
A linked Slack account receives only your direct messages. Unlink it with Remove on the Your Slack card at any time; direct messages then stop until you link again.
Who can do what
The workspace's chat app is connected once for the whole workspace. After that, daily work splits by role:
| Action | Admin | Recruiter |
|---|---|---|
| Connect the workspace Slack/Teams app (one-time) | Yes | Yes, from Your Slack, if not connected yet |
| Add or remove shared channel destinations | Yes | No |
| Choose which events post to the shared channel | Yes | No |
| Link my own Slack/Teams for direct messages | Yes | Yes |
| Choose which events DM me | Yes | Yes |
Connecting is a one-time, workspace-wide step
Whoever connects it first installs the app for the entire workspace — there is one app, not one per person. If your workspace has not connected it yet, the Your Slack card lets you connect it (or, where your workspace requires an admin to, request one). Choosing and changing the shared destinations stays with administrators.
For the full role model, see Roles and permissions.
Event types
| Event | Icon | Category | What it means | Where to go |
|---|---|---|---|---|
candidate.completed | CheckCircle | success | A candidate submitted their assessment | Open the candidate's report |
candidate.started | Play | info | A candidate opened their invitation and began | Monitor; you may want to wait for the completion event |
cets.complete | FileText | info | The CETS analysis for a candidate's attempt is ready | Open the integrity report |
assessment.activated | BellRing | success | An assessment became ACTIVE (payment captured) | Open the assessment to send invitations |
invitation.sent | BellRing | info | Invitation emails were dispatched | Monitor; track who has started in the assessment detail |
Categories
| Category | Color | When to use |
|---|---|---|
success | success green | The event completed without issue |
info | info blue | A state change that does not require action |
warning | warning amber | Something to look at, but not yet a problem |
error | error red | An action failed or needs intervention |
Marking as read
Notifications are marked as read when the dropdown opens. The unread count disappears and the events remain in the list (until the configured retention window).
To mark a single notification as read, click it. To mark every notification as read without opening the dropdown, use Mark all as read in the dropdown header.
Email equivalents
| Event | Email? |
|---|---|
candidate.completed | Yes |
cets.complete | Yes |
assessment.activated | Yes |
invitation.sent | No (the email is the notification) |
candidate.started | No |
You can configure your email notification preferences from Settings.
If something is not arriving
| Symptom | What to check |
|---|---|
| No Slack posts to a channel | An admin has connected the app and added that destination, and the Slack column is on for the event |
| "An administrator must connect Slack first" | The workspace Slack app is not connected yet — an admin can connect it, or use Request an admin |
| No direct messages | You have linked Your Slack, and the Direct message column is on for the event |
| A switch will not turn off | It is a critical event, which stays on (for example, low wallet balance) |
More help is in Troubleshooting.