Skip to main content
Connect Slack when you want Chief to search messages and read channels as a Project source. An Organization Owner first connects the workspace to the Project; each member then authorizes their own Slack account, so results follow that person’s Slack access.

​
Set up Slack for the Organization

An Organization Owner opens Organization › Integrations and selects Add Slack workspace. The setup panel starts with an App name field — Slack shows this name on the app and its bot, so give each integration in a workspace its own name (it defaults to Chief) — followed by the app manifest to use when creating an internal Slack app.
  1. In Slack’s API dashboard, select Create New App › From an app manifest, choose the workspace, and paste Chief’s manifest.
  2. Install the app to the workspace and copy its Bot User OAuth Token, Client ID, and Client secret.
  3. Return to Chief, enter those credentials, and select the Projects that should use the workspace.
  4. Click Connect workspace.
Only an Organization Owner can complete this setup. If every Project already has a Slack integration, the Select projects list shows No projects available to deploy to.

​
Connect your own Slack account

After an Owner enables Slack for your Project, link your own account from either place:
  • From your settings. Open Settings › Connected accounts. Under Slack, each workspace an owner has deployed to a Project you’re in is listed; click Connect Slack next to it and approve access in Slack. Once linked it shows Connected with a Disconnect button. If the list is empty, no workspace has been deployed to your Projects yet.
  • From a task. Open Tools & integrations, find Slack under Connected, and click Connect. The row explains that Slack search and private-channel reads use your own account. Approve access in Slack, then return to the task.
Either way, Slack is now available as a source for searches and channel reads. Linking your account is also what lets Chief identify you and answer when you mention it in Slack. Chief may also show a Slack banner above the prompt bar or ask you to connect when a task first needs Slack; these entry points use the same authorization flow.
⚠️ Important: Chief can search only the Slack content your connected account can access. Connecting Slack does not give you access to another person’s private channels or messages.

​
Manage the connection

Organization Owners manage which Projects can use the Slack workspace from Organization › Integrations. Individual members can disconnect or reconnect their own account under Settings › Connected accounts, or reconnect from the task tools when a token is revoked or a new permission is required. For controls that can take actions through an integration, see managing integration permissions. Slack access is separate from Google connections and Notion.

​
FAQ

Your Organization may not have connected a Slack workspace, or Slack may not be enabled for the current Project. Ask an Organization Owner to complete the setup or add this Project.
Slack searches run under each person’s own account. Your teammate may belong to a channel or conversation that your Slack account cannot access.
A stored connection may no longer work because Slack revoked it or Chief now needs another permission. Open Tools & integrations and select Reconnect on the Slack row — or, if a task shows a card saying Reconnect Slack to grant the access this action needs., click Connect Slack on it — and approve the requested access.