> ## Documentation Index
> Fetch the complete documentation index at: https://docs.chief.bot/llms.txt
> Use this file to discover all available pages before exploring further.

# Connecting Slack and searching as yourself

> Connect Slack to a Project, then authorize your own account so Chief searches only messages and channels you can access.

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**. Chief provides an 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](/help/projects-sharing-teams/what-is-a-project) 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, Chief shows **Every project in this organization already has a Slack integration.**

## Connect your own Slack account

After an Owner enables Slack for your Project:

1. Open a task and open its source or tools controls.
2. Find **Search Slack as yourself**. Chief explains that Slack search and private-channel reads use your own account.
3. Click **Connect Slack** and approve access in Slack.
4. Return to the task. Slack is now available as a source for searches and channel reads.

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.

<Warning>
  ⚠️ **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.
</Warning>

## Manage the connection

Organization Owners manage which Projects can use the Slack workspace from **Organization** › **Integrations**. Individual members can reconnect their account 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](/help/integrations/managing-integration-permissions-connection-status). Slack access is separate from [Google connections](/help/integrations/google-drive) and [Notion](/help/integrations/notion).

## FAQ

<AccordionGroup>
  <Accordion title="Why does Chief say Slack setup is required?">
    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.
  </Accordion>

  <Accordion title="Why can another teammate find a Slack message that I cannot?">
    Slack searches run under each person's own account. Your teammate may belong to a channel or conversation that your Slack account cannot access.
  </Accordion>

  <Accordion title="Why does Chief ask me to reconnect Slack?">
    A stored connection may no longer work because Slack revoked it or Chief now needs another permission. Select **Reconnect Slack** and approve the requested access.
  </Accordion>
</AccordionGroup>