Skip to content

Alert channels

Alert channels send events out of Identiguard to where the team already works. There are three: Slack, Microsoft Teams and email.

Requirement Detail
Plan Max or Super
Switched on for the workspace A platform operator switches alert channels on for each workspace. Until then Alerts does not appear in the sidebar.
Role Only admins can change the settings. Members and viewers can open the page. They see the banner Read-only: only workspace admins can change alert settings. and every control is disabled.

Open Alerts under Workspace in the sidebar.

  • Events at or above the channel’s minimum severity, from the tenants in the channel’s scope.
  • Synthetic journey results, as described in the table below.
Journey result Severity Slack Teams Email
Confirmed outage: two real failures in a row from one region ERROR Yes Yes Yes
Recovery ERROR Yes Yes No
Slowdown WARN Yes Yes No

The channel’s minimum severity also applies to journey results. A Teams channel left at the default ERROR never receives slowdowns. Set it to WARN if you want them.

Incidents are not sent to channels today. Work them on the Incidents page.

Channel How it connects Default minimum severity Severity options
Slack An incoming webhook URL from Slack WARN DEBUG, INFO, WARN, ERROR, CRITICAL
Microsoft Teams The HTTP URL from a Power Automate flow ERROR DEBUG, INFO, WARN, ERROR, CRITICAL
Email A list of recipients ERROR WARN, ERROR, CRITICAL

Each channel has its own card, and beside it its own Tenant forwarding scope card.

The two cards have the same controls.

Control What it does
Status chip Live or Off Shows the saved state. It does not change until you save.
Enable Slack forwarding or Enable Microsoft Teams forwarding A tick box. When ticked and saved, events are sent for the selected tenants.
Minimum severity Only events at this level or above are forwarded. DEBUG forwards everything.
Slack webhook URL or Microsoft Teams webhook URL Where you paste the URL. Once a URL is saved, the card shows it masked, with Replace.
Destination and Set by The host of the saved webhook, a fingerprint of the URL, who saved it and when, in UTC
Save changes Saves the card. The button shows Saving…
Send test message Posts a test message. It is available once a URL has been saved. The button shows Sending…
Disconnect Stops forwarding and deletes the stored webhook URL

Save changes is disabled when forwarding is ticked and no tenant is selected, and when a URL is needed and the field is empty.

The messages are Alert settings saved., Test message sent. and Channel disconnected.

Channel The URL must
Slack Use HTTPS and be on hooks.slack.com or hooks.slack-gov.com
Microsoft Teams Use HTTPS, be on a host ending in .logic.azure.com or .logic.azure.us, and have /workflows/ in the path

Redirects are not followed. Paste the final URL.

For Teams, the URL comes from a Power Automate flow that uses the When a Teams webhook request is received trigger. Events arrive as an Adaptive Card. The older Office 365 connectors in Teams are retired by Microsoft and are not supported. See Send alerts to Teams.

  1. On the card, choose Replace beside the masked URL.
  2. Paste the new URL and choose Save changes.
  3. Choose Send test message.

The Destination and Set by block lets you check that alerts still go to a place you control.

  • If the person who saved the webhook has left the workspace, the card warns that their address “is not a member of this workspace. Check that this destination still belongs to you, or replace it.”
  • An older webhook shows “Not recorded: stored before Identiguard recorded this. Replace the webhook to record it.”

Disconnect opens the dialog Disconnect this channel? with this text: “Event forwarding stops immediately and the stored webhook URL is deleted. You can reconnect later by pasting a new webhook URL.” Choose Disconnect to confirm.

Only Slack and Teams have Disconnect.

Control What it does
Status chip Live or Off Shows the saved state
Enable email forwarding A tick box. It is disabled until one recipient is confirmed. Until then the card reads Add and confirm at least one recipient first.
Minimum severity WARN, ERROR or CRITICAL
Email recipients The list of addresses, each with a badge and a remove button. Empty, it reads No recipients yet.
The address field and Add recipient Adds an address. The button shows Adding…
Save changes Saves the tick box, the severity and the tenant scope
Send test email Sends a test to every confirmed recipient

There is no Disconnect on the Email card. To stop email alerts, untick Enable email forwarding and choose Save changes, or remove the recipients.

Badge Meaning
Confirmed The address receives alerts
Awaiting confirmation An address outside the workspace that has not confirmed yet. It receives nothing.
No longer a member, not mailed The address was added as a workspace member, and that person has since left. It receives nothing.

As you type an address, a hint tells you what will happen:

  • “This address is a workspace member, so it starts receiving alerts immediately.”
  • “An address outside this workspace receives a confirmation email first and gets nothing until someone with access to that inbox clicks the link.”

The messages are Recipient added. for a member and Confirmation email sent. The address receives alerts once confirmed. for an outside address.

A channel can have at most 25 recipients. For more people, use a distribution list address.

To remove a recipient, choose the remove button on the row. The dialog Remove this recipient? explains that the address stops receiving alert emails and that an outside address has to confirm again if you add it back. Choose Remove. You see Recipient removed.

The confirmation email has a link. No sign-in is needed.

  1. The link opens Confirm alert emails. The page says that a workspace admin asked to send Identiguard security alerts to the address, and that nothing is sent until the person confirms.
  2. The person chooses Confirm this address.
  3. The page shows Address confirmed.

The link lasts 72 hours. A link that is expired, already used or replaced shows This link is not valid.

There is no resend button. To send a new confirmation email, remove the address and add it again.

Email is limited to 50 alert emails an hour for the workspace.

  • When the limit is reached, the recipients get one notice email. It says that the workspace has reached its limit of 50 alert emails for this hour and that further alert emails are paused until the next hour starts.
  • The other alerts in that hour are not sent by email. Every event is still in the event feed.
  • A test email counts towards the same 50.

Beside each channel card is a Tenant forwarding scope card. It decides which tenants that channel receives.

  • Each channel has its own scope.
  • New tenants are opt-in. A new tenant is not added to any channel until you tick it.
  • The card shows a Selected tenants count and a tick box for each tenant, with its name and type. There are 8 tenants on a page.
  • With no tenants, it reads No tenants in this workspace yet.
  • A change takes effect only after Save changes on the channel card.

A common pattern is a busy Slack channel at WARN for the IAM team, and email at CRITICAL for the security lead.

Limit Value
Slack and Teams posts 20 a minute for each destination
Alert emails 50 an hour for each workspace
Email recipients 25 for each channel
Confirmation link lifetime 72 hours

During a flood, ERROR and CRITICAL events are sent to Slack and Teams first. The rest are summarised on the next message. Alert delivery never slows down the event feed.

When alerts to Slack or Teams were held back or could not be delivered, the card shows a banner. It gives the number of alerts, the time since when, and the most recent time. It ends: “This workspace’s alerts to this channel are limited to a steady rate, and the rest are summarised on the next message. Every event is still in the event feed.”

If you see it often, raise the Minimum severity or select fewer tenants.

What you see Why What to do
Alerts is not in the sidebar, or the page shows Alert integrations are disabled for this workspace. Alert channels are not switched on for the workspace, or the plan is below Max. Ask a platform operator to switch on alert channels. Check the plan.
Read-only: only workspace admins can change alert settings. You are a member or a viewer. Ask an admin.
Failed to save alert settings. or Test message failed. The server gave no usable message. Try again. If it continues, tell support the time and the page.
What you see Why What to do
Slack webhook URL is required., …is invalid., …must use HTTPS., …host is not allowed. or …path is invalid. The URL is empty, is not HTTPS, is not on an allowed Slack host, or has no path. Paste the full incoming webhook URL from Slack.
Teams webhook URL is required., …is invalid. or …must use HTTPS. The URL is empty or badly formed. Paste the HTTP URL from the Power Automate flow.
Teams webhook URL host is not allowed. Use a Power Automate Workflows URL (logic.azure.com). The URL is an old Office 365 connector URL, or is on another host. Create a Workflows flow and use its URL.
Teams webhook URL does not look like a Workflows trigger. Classic Office 365 connectors are retired and are not supported. The path has no /workflows/. Use the URL from the When a Teams webhook request is received trigger.
webhookUrl is required when configuring this channel for the first time. or A webhook URL is not configured for this channel. You saved, enabled or tested with no stored URL. Paste the URL and save first.
At least one tenant must be selected when forwarding is enabled., or Save changes is disabled No tenant is ticked. Tick tenants in Tenant forwarding scope.
selectedTenantIds contains tenant IDs outside this workspace. The page is out of date. A tenant was deleted. Reload the page.
This channel is not configured. You tested before the first save. Save first.
Slack test message failed: webhook returned a status, or Microsoft Teams test message failed: webhook returned a status Slack or Power Automate refused the post. Usual causes: the webhook was revoked, or the flow was deleted or switched off. Create the webhook or flow again, then choose Replace and paste the new URL.
A test message failed with webhook redirected and redirects are not followed The URL redirects to another address. Use the final URL.
The delivery problems banner More than 20 posts a minute, or the destination failed. Raise the minimum severity or select fewer tenants. The events are still in the feed.
An address “is not a member of this workspace. Check that this destination still belongs to you, or replace it.” The admin who saved the webhook has left the workspace. Check the destination. If you are not sure, choose Replace.
What you see Why What to do
Add and confirm at least one recipient first. or Add at least one confirmed recipient before enabling email alerts. No recipient is confirmed. Add a workspace member’s address, or wait for an outside address to confirm.
A valid email address is required. The address is badly formed. Correct it.
That address is already a recipient. The address is already in the list. Nothing to do.
A channel can have at most 25 recipients. The limit is reached. Remove one, or use a distribution list.
Too many confirmation emails have gone to that address recently. Try again later., This workspace has reached its limit of N alert confirmation emails in 24 hours. Try again tomorrow. or Confirmation emails cannot be sent right now. Try again in a few minutes. A limit on confirmation emails, or a temporary fault. Wait and try again.
The badge Awaiting confirmation does not change The person has not chosen the link, or the 72-hour link expired. Remove the address and add it again to send a new email.
The badge No longer a member, not mailed The person was added as a member and has left the workspace. Remove the address. Add it again if they should still receive alerts. They then confirm as an outside address.
This link is not valid on the confirmation page The link expired after 72 hours, was already used, was replaced by a newer one, or the recipient was removed. An admin removes the address and adds it again.
No confirmed recipients yet. Add one and confirm it first. You sent a test with no confirmed recipient. Confirm one recipient first.
This workspace has used its 50 alert emails for this hour. Try the test again after the hour rolls over. The hourly limit is used up. Wait for the next hour. Consider a higher minimum severity for email.
The test email could not be sent to any recipient. Sending failed for every address. Try again. Check the addresses.

Nothing arrives although the chip says Live

Section titled “Nothing arrives although the chip says Live”
Check What to do
Is the event below the channel’s Minimum severity? Lower the level, or test with a more severe event.
Is the tenant ticked in Tenant forwarding scope? New tenants are not added automatically. Tick it and save.
Did you choose Save changes? The chip shows the saved state only. Save, then check the chip.
Is it a journey slowdown on a channel at ERROR? Slowdowns are sent at WARN, to Slack and Teams only. Lower the channel to WARN.
Was a limit reached? Look for the delivery problems banner, or the hourly limit notice email.
Does the destination still work? Choose Send test message or Send test email.

For other problems, see Troubleshooting.