Where to find it
Open Notifications in the left rail of the Workflow product. The page has two parts: the client's alert channel (pick the client in the client picker first) and your personal Slack settings, which follow you across all clients.
The client's notification channel
When Omega surfaces a new signal for a client, it can post the alert to a Slack channel so the account team sees it without having the app open.
In Slack, add the Omega Alerts app to the channel: open the channel, click Add members, and type Omega Alerts. Omega can only post to channels that app has been added to — and a private channel it hasn't been added to is invisible to it entirely, which is what makes that particular failure so confusing.
Back in Omega, with the client selected, find the Notification channel section.
Enter the Slack Channel ID for the channel where this client's alerts should go.
Leave the field blank to use the org-wide default channel instead — that's the fallback for any client without its own channel.
Check the Posting to line to confirm which channel is currently active.
Send a test before you trust it
Don't wait for a real signal to find out the channel is wrong:
Click Send test message.
Check the Slack channel for the test post.
If it doesn't arrive, the result line under the button says what went wrong and what to do about it.
The two failures worth knowing:
"Omega can't see <channel>" — usually a private channel the Omega Alerts app hasn't been added to. Add it (step 1 above) and re-test. If the channel is public, the ID is probably wrong instead: re-copy it from View channel details in Slack.
"The Omega Alerts app isn't in <channel>" — the ID is right and the channel is public; the app just needs adding. Same fix.
A channel ID that looks valid is not the same as a channel Omega can reach, which is why the test button exists.
Weekly and monthly reports
Whether a client's scheduled weekly and monthly reports run at all is an opt-in, with a sensible default: a client with a Slack channel configured has somewhere for reports to land, so their reports default on; a client without one defaults off. The two toggles — one per cadence — live on the Client settings page, under Scheduled reports.
Set a toggle by hand and it stays put. Leave it untouched and it follows the channel — so wiring up a channel later opts the client in automatically. A reset to default link takes a hand-set toggle back to the derived behavior.
Your personal Slack delivery
The Slack DMs section is about you, not the client:
Turn on Also send my mentions & replies to Slack to get a DM when a teammate mentions you or replies to you in Omega — useful if Slack is where you actually live during the day.
The same delivery covers signal activity that involves you — for example, when a teammate sets or changes the due date on a signal you own, the alert lands the same way.
Omega matches your Slack account automatically from your work email. If the match fails (say your Slack email differs), paste your Slack member ID into the override field and save.
Click Send me a test DM to confirm delivery. The result line explains any failure — for example, if the toggle above is off, or no Slack account matched your email.
Tip: Set the notification channel as part of client onboarding, right after metrics and coverage. The usual pattern is the client's internal team channel — alerts reach the people who'd act on them, without waiting for someone to check the board.
Note: In-app signals are unaffected by any of this — everything still appears in Omega regardless of Slack settings. Also, demo clients never post to Slack by design, so don't be alarmed when a test for one stays in-app only.
Note: The in-app New signal pop-ups and bell entries follow the client picker, not these settings. Pick a client and you're notified as that client's new signals land; with All clients selected you get none. Notifications addressed to you — mentions, replies, runs you started, signals assigned to you — reach you whichever client is picked.