Slack & email notifications

A@H&*█?GW?K@▓M13▒X8G·BC6QA/FUT329GH█▒Y█F$░PJF*>X░NZ%FF&YF*A6QE$%2KWJ1J%WW<AZ\<·&·<<7D*2S▒WA$▒UCR2CSU6G█>Q#<9YC*▓*R$0<░WB░/0%&%WN1YNFY?75?U7HYZ<U4M@9▓%1<%░*?X▒TV3Z█BGG4D2>R57B2B>2M*4?#QVM$JFGP35\243@%UKZ?4N▓6#5F&2<6\N@NP5▒1▒6E2/VA\AK█3Z6YY▓▒█░5A3DA24█▒>$█EY▒7ZEPYCJY\3░J2@#X&▓$T2&·Z<@#BS9/S2@▓0█J6#BMMW246ZUXK·CY6@JQM█<&JA@H&*█?GW?K@▓M13▒X8G·BC6QA/FUT329GH█▒Y█F$░PJF*>X░NZ%FF&YF*A6QE$%2KWJ1J%WW<AZ\<·&·<<7D*2S▒WA$▒UCR2CSU6G█>Q#<9YC*▓*R$0<░WB░/0%&%WN1YNFY?75?U7HYZ<U4M@9▓%1<%░*?X▒TV3Z█BGG4D2>R57B2B>2M*4?#QVM$JFGP35\243@%UKZ?4N▓6#5F&2<6\N@NP5▒1▒6E2/VA\AK█3Z6YY▓▒█░5A3DA24█▒>$█EY▒7ZEPYCJY\3░J2@#X&▓$T2&·Z<@#BS9/S2@▓0█J6#BMMW246ZUXK·CY6@JQM█<&J

1001101111111101101100010100111111110000111010001001111010101010001001010010101100110101100000101101101011100010111010011001011011000101111011011011001000001011100100100111111001110011101110010001111001011001101000110010011000000100101111001111111100101111001101111011000111101000111110011100001110001110010111001000010010011011111111011011000101001111111100001110100010011110101010100010010100101011001101011000001011011010111000101110100110010110110001011110110110110010000010111001001001111110011100111011100100011110010110011010001100100110000001001011110011111111001011110011011110110001111010001111100111000011100011100101110010000100

Wire QorTrace to Slack and configure per-event notification routing.

Get the right alert in front of the right person, without overwhelming anyone.

Slack integration

Step 1 — Add the Slack app

Account → Integrations → Slack → + Add to Slack. We open Slack's OAuth flow. Approve the app — we ask only for the incoming-webhook scope (write to one channel you pick).

Step 2 — Pick a default channel

Choose any channel where the bot has permission to post. We default to #qortrace-alerts.

Step 3 — Per-event routing (Team+)

Override the default per event type:

Event	Default channel	Common override
`audit.delivered`	#qortrace-alerts	#appsec
`atlas.alert.fired` (Critical)	#qortrace-alerts	#incidents
`scan.completed`	(silent)	#scan-firehose

Configure in Account → Integrations → Slack → Routing.

Step 4 — Mention rules

Optional: tag specific Slack users on certain events.

audit.failed → @your-team-lead
atlas.alert.fired (Critical) → @oncall
account.plan.changed → @cfo (lol)

Email notifications

Every account user has notification preferences in Account → Settings → Notifications:

Audit delivered — on by default
Audit failed — on by default
Atlas alerts — Critical only by default; toggle for Moderate/High
Weekly team digest — on for Team plan owners
Marketing emails — opt-in only (we never default-on this)

You can fully unsubscribe from any cadence with one click from any email.

Email digest

Team plans get a Monday-morning digest:

Audits delivered last week
Atlas alerts fired
Credits consumed vs remaining
Top contributors (audit submitters / acknowledgers)

Customise the recipients in Account → Settings → Notifications → Digest.

Compliance receipts

These never go through Slack — they're always email-delivered (typically to your compliance officer's address). Configure the recipient in Account → Settings → Notifications → Compliance.

Quiet hours

Set quiet hours per channel — alerts queue up and deliver at the end of the quiet window. Useful for non-Critical events at 3am. Configure in Account → Integrations → Slack → Quiet hours.

Webhooks > Slack?

If you want richer routing (e.g. PagerDuty for Critical, Slack for High, no-op for Moderate), use the Webhooks integration with your own routing logic. See Webhooks.