Slack integration

The Slack integration connects your Slack workspace to Bigmind so Bigmind can send notifications directly to users in Slack. Organizations can also opt in to Slack channel sync, which lets Bigmind import messages from selected customer channels and associate that context with accounts and deals.

#What the Slack integration is for

Bigmind installs a Slack bot user in your workspace. By default, the bot is used only to post notifications to users. Reading channel history is optional and requires a separate authorization step.

Bot-based delivery: Bigmind uses the Slack bot user to send direct notifications to matched users in Slack.
User matching: When Slack is connected, Bigmind syncs Slack workspace users and matches them to Bigmind users by email address.
Optional channel sync: Organization owners can authorize additional Slack scopes so Bigmind can sync messages from channels the Bigmind app has access to.
Account and deal context: Synced channels can be associated with an account and, optionally, a specific deal so Slack conversations appear in the right customer context.

#Default permissions for notifications

When you first connect Slack, Bigmind requests the following bot token scopes. These are the minimum permissions needed for notification delivery and user matching:

chat:write — allows the bot to post messages into a conversation. Once a direct-message conversation has been opened with a user, this scope is used to send the actual notification content.
im:write — allows the bot to open a direct-message conversation with a user. Slack requires a DM channel to be opened before any message can be sent, so this scope works together with chat:write to deliver notifications.
users:read — allows the bot to list workspace members and read basic profile information such as name and avatar. This is used to sync your Slack workspace users into Bigmind for user matching.
users:read.email — allows the bot to read the email addresses of workspace members. Bigmind uses email addresses to match Slack users to Bigmind users so notifications are delivered to the right person.

These default scopes do not grant the bot access to public or private channel history, group message history, or files. If you only connect Slack for notifications, Bigmind does not sync Slack channel messages.

#Optional permissions for channel sync

Slack channel sync is opt-in. If an organization owner chooses Connect channel sync from the Slack integration overview, Bigmind asks Slack for these additional scopes:

channels:read — lists public channels the Bigmind app can see.
channels:history — reads message history from public channels the Bigmind app has access to.
groups:read — lists private channels the Bigmind app has been added to.
groups:history — reads message history from private channels the Bigmind app has been added to.

Channel sync only runs for channels that are associated to an account in Bigmind. Channel access is controlled through Slack: the Bigmind app must be added to a channel before Bigmind can sync that channel. This is especially important for private channels, which are only visible to Bigmind after the app is explicitly added.

#Limiting access to specific channels

Slack channel sync is designed so teams can choose exactly which channels become customer context in Bigmind. Authorizing channel sync gives Bigmind the ability to work with channels the app can access, but messages are only synced after a channel is both accessible in Slack and associated in Bigmind.

Add the Bigmind Slack app to the Slack channel you want to sync.
Bigmind sends a one-time setup prompt. When Slack identifies the inviter, Bigmind sends it as a DM to that person; otherwise, Bigmind posts the prompt in the channel.
Use the Slack interactive setup flow to search for the relevant account by name or domain.
Optionally select a deal for more specific attribution.
Submit the modal to associate the channel. Bigmind then starts syncing messages from that channel on an ongoing basis.

You can also manage channel associations from the Channels tab in Bigmind. The tab appears after channel sync has been authorized, and channels are listed in pages so large Slack workspaces remain manageable.

#Common use cases

Slack is useful when your team wants timely updates where they already work. Depending on which notifications are enabled for your organization and users, Bigmind can use Slack for cases such as:

Meeting analysis: Notify users when a meeting summary or analysis is ready to review.
Coaching insights: Deliver coaching-related insights and manager notifications when new coaching opportunities are identified.
Meeting digests: Send daily or weekly meeting digests so users and managers can stay on top of upcoming meetings and recent activity.
Pipeline and productivity updates: Share weekly account updates and daily suggested to-dos.
Slack channel context: Bring customer Slack conversations into the right account or deal context when channel sync is enabled.
Other important alerts: Send timely product signals and other notification-driven updates when they are enabled in Bigmind.

#How notification delivery works

An admin connects Slack from Settings → Communication data → Messaging.
Bigmind syncs Slack users from the connected workspace.
Bigmind matches Slack users to Bigmind users using email address.
When a notification is triggered, Bigmind sends the message to the matched user through the Slack bot.

#How channel sync works

An organization owner opens the Slack integration overview and selects Connect channel sync.
The owner completes the Slack authorization flow for the additional channel sync scopes.
Bigmind shows the Slack channels the Bigmind app has access to in the Channels tab, with paginated results for large workspaces.
An owner associates a channel with an account and, optionally, a deal.
Bigmind starts syncing messages from associated channels on an ongoing basis and uses them as customer context for the linked account or deal.

You can associate channels from Bigmind, or from Slack when the Bigmind app is added to a channel. In Slack, Bigmind sends a one-time setup prompt with a button that opens a modal where you can search for the account by name or domain and optionally select a deal.

#Notification settings control what users receive

The Slack connection does not decide which notifications are sent by itself. Delivery is managed through Notification Settings.

Organization defaults: Admins can define the default notification behavior for the workspace.
User-level overrides: Individual users can adjust their own notification preferences.
Channel preferences: For supported notification types, users can choose whether to receive updates by email, Slack message, both, or turn them off.

If you want Slack notifications for meeting analysis, coaching insights, digests, or other updates, make sure those notification categories are enabled and their channel includes Message or Both.

#What to check if notifications are not arriving

Slack is connected: Confirm your workspace connection is active in the Messaging integrations settings.
User matching succeeded: The user must exist in the connected Slack workspace and their Slack email should match their Bigmind account email.
Notification type is enabled: Check the relevant category in Notification Settings.
Channel includes Slack: The notification channel must be set to Message or Both.

#What to check if channel sync is not working

Channel sync is authorized: On the Slack integration page, confirm the Channels tab is visible. If it is not, reconnect channel sync from the overview.
The Bigmind app has channel access: Add the Bigmind Slack app to the channel you want to sync. For private channels, this is required before Bigmind can see the channel.
The channel is associated: A channel must be linked to an account before Bigmind syncs its messages. You can optionally link it to a deal as well.
CRM records exist: Confirm the account or deal exists in Bigmind before associating the channel.