Turn on notifications
Summary
This step completes when you connect Slack or Teams and send a test briefing. Use each destination's Test button as well, to confirm the platform can actually reach your team in Slack or Teams, not just that the integration looks connected.
Before you start
You need the Manage Communications permission to set up Integrations → Notifications (and Manage Users or Manage Tenant to open Configure), plus permission in Slack or Microsoft Teams to approve a new app connection. Whether Slack and Microsoft Teams can be connected at all depends on how CyberHQ.ai is set up for your organization, not on your plan; where it isn't set up, the section says so and that turning it on is a setting, not a plan change. Connecting Slack or Teams, sending to their channels, and the daily briefing all need the Professional plan or above, so on Starter this step can't be completed.
1. Connect Slack or Teams
- Go to Integrations → Notifications.
- Under Slack or Microsoft Teams, select Connect Slack or Connect Microsoft Teams.
- You'll be taken to Slack or Microsoft to approve access, then returned automatically.
Once connected, you'll see the team name and connection date. In Slack specifically, you can also turn on interactive buttons (Acknowledge/Resolve directly from a message) and optionally restrict who can use them with an authorized-responders list.
2. Point a notification destination at it
- Under Notification destinations, create a new destination.
- Choose Slack or Teams as the type, and pick a channel.
- Leave the event, severity, and signal-type filters empty for now: empty means "everything," which is the simplest way to confirm delivery is working before you narrow it down.
- Select Test on the destination's row. A test message should arrive in the channel you picked, and the result shows under the row.
3. Send a test briefing
- Go to the Daily CISO briefing section (Professional plan or above).
- Under Recipients (emails), add at least one email address and save. The test can't be sent until a recipient is saved.
- Select Send test briefing now.
The full briefing goes by email to the saved recipients. A short "Daily Briefing" summary also posts to any Slack or Teams destination whose filters are left empty, like the one you created in step 2. Sending the test is what completes this step, wherever it lands.
Confirm it worked
The briefing email arrives for your saved recipients, and Briefing history lists the test. For Slack or Teams, select View delivery log at the bottom of the Notifications page: your destination test should appear with an outcome of Sent, and the message itself should be visible in the channel.
If it didn't work
- Delivery log shows nothing: nothing was attempted; recheck that the destination is enabled and its filters aren't excluding the test.
- Delivery log shows Failed: the specific error shown usually names the cause directly; a disconnected integration is the most common one.
- Delivery log shows Sent but nothing arrived: the platform delivered it successfully; check the receiving channel's permissions or any message filters on the Slack/Teams side.
- For anything beyond these, see An expected notification didn't arrive.
Related
- An expected notification didn't arrive
- Complete your organization profile