Help center
HelpIntegrationsSlack notifications.
Slack notifications.
What we post to Slack, how to scope the channel, and how to keep candidate-identifying data out.
Last reviewed 30 June 20263 min read

The Slack integration posts a single message per event into a channel of your choice. By default the message contains role-level data only; candidate names and identifying details are hidden behind a link to the dashboard.

The events we post on.

  • Role posted. "<Workspace> posted <role title>. Live on syndication."
  • First applicant. "<Role title> has its first applicant."
  • Three finalists ready. "<Role title> has three finalists. Read the cards in the dashboard."
  • Override logged. "<User> overrode the rank on <role title>. Rationale logged."
  • Cap warning, cap hit, billing event. Routed to the billing channel if separately configured.

What we never post.

We never post candidate names, candidate transcripts, candidate scores, or any protected characteristic to Slack. The dashboard link in the message takes the authenticated user to the candidate card; the candidate data lives in the dashboard, not in the chat surface.

Per-event opt-outs are available under Settings, Integrations, Slack, Events. A common setup is "finalists only", which silences the role-posted and first-applicant pings and keeps the higher-signal events on. Microsoft Teams parity ships in the first 90 days post-launch.

You can scope the integration to a private channel and restrict the install to admins. The audit log records every install and uninstall.

What to do next: install the integration, pick a private channel for the finalist alerts, and pick a separate channel for billing if you want it siloed.

slacknotificationschannelintegrations
Still stuck?
One email gets a human reply inside 24 hours.
Email help@picked.aiStatus page
Slack notifications. | Help · Picked.ai