Skip to main content
Connect Metaview to Slack to get a direct message the moment your Notes are ready or a Sourcing search needs you, and to run Sourcing searches from a Slack thread without keeping Metaview open. This is the native Slack integration. It is separate from Slack via Zapier, which posts completed meeting summaries into a channel — see the comparison below if you are deciding between them.

​
How the connection works

Slack is connected once for your whole Metaview workspace, not once per person. One person authorizes the Metaview Slack app. Metaview then matches each Metaview user to their Slack account by email address and sends notifications through that shared connection. Everyone else simply chooses their own notification preferences in Personal Settings — they never grant separate Slack access. Notes and Sourcing use the same Slack app, so a single connection covers both.

​
Connect Slack

Any active member of your Metaview workspace can do this:
  1. Select Settings near the bottom of the Metaview sidebar.
  2. Open Integrations.
  3. Find Slack and select Connect Slack.
  4. Review the permissions Slack asks you to approve, then select Allow.
Once connected, everyone in the workspace should see Slack as connected, and Sourcing notifications are enabled by default. You can change your own preferences in Personal Settings. Metaview does not require a Metaview admin. Your Slack workspace’s own app policy still applies: if members are allowed to install apps, any member can connect it; if app approval is restricted, a Slack admin has to approve or install it.

​
Disconnect Slack

Select Disconnect Slack from the same Integrations page. Disconnecting applies to the whole workspace. It stops Notes and Sourcing notifications and removes Slack-based Sourcing access for everyone, not just the person who disconnects.
Disconnecting the native integration does not affect Slack via Zapier. Zaps that post to a Slack channel keep running.

​
What Metaview can access in Slack

Slack permissions are granular: an app has no access beyond the scopes granted to it at install. The grant is workspace-wide and made once, at the point of installation — it is not renewed or narrowed per user. These are the permissions shown on Slack’s approval screen. They are granted as a single set — Slack does not let you approve them individually.
Message history is not workspace-wide. The channels:history and groups:history scopes cover only channels the Metaview app has been added to, and im:history covers only the app’s own direct messages. Metaview cannot read channels the app is not in, and cannot read direct messages between other people.
These are standard, granular Slack scopes for an app that identifies people by email, sends them direct messages, and takes part in threads it is invited to. Sending notifications uses only users:read, users:read.email, im:write, and chat:write — none of which can read messages. The rest support Sourcing conversations in Slack. You only ever receive notifications about conversations and searches you already have access to in Metaview.

​
Notes notifications

When enabled for your workspace, Metaview sends you a Slack notification after your call has been transcribed and its Notes summary is ready. This needs three things: an active Slack connection, the workspace-level setting enabled, and your own Receive summary notifications in Slack preference enabled. Both settings are on by default. You also need a Slack account whose email matches your Metaview account.

​
Sourcing in Slack

You can use Slack to:
  • Start or continue a Sourcing search.
  • Respond when the Sourcing agent needs input.
  • Continue a Sourcing conversation from its Slack thread.
  • Attach job descriptions or other relevant files.
  • Receive a notification when results are ready.
  • Open the full search and Candidate Pack in Metaview.
For instructions and best practices, see the Sourcing Guide.
Receive Sourcing notifications in Slack controls notifications for searches you create in the Metaview web app. It does not silence a search you deliberately started in Slack, because Slack is that search’s primary surface.

​
Native Slack integration vs Slack via Zapier

  • Native Slack integration: sends personal Notes-ready and Sourcing notifications and supports Sourcing conversations in Slack.
  • Slack via Zapier: posts completed meeting summaries or selected fields into a Slack channel as part of a Zap.
You can use either integration or both. See Slack via Zapier for channel-posting setup.