# Slack connector

> An admin connects the workspace's Slack first, then each member links their own Slack account. Agents only ever act through a member's own link.

Slack access is personal: agents read Slack through a member's own linked
account, never through a shared workspace token. Getting there takes two
steps in order.

## Step 1: an admin connects the workspace's Slack

A workspace owner or admin connects the workspace's Slack workspace first.
This connection is an entry point and a sign off: it proves the Slack
workspace is really this team's, and it turns on personal linking for
members. It stores no usable token and no agent can be granted it.

Slack is available in team workspaces only, and a member can only link an
account belonging to the Slack workspace an admin actually connected.

## Step 2: each member links their own account

Once the workspace's Slack is connected, any member links their own Slack
account, from the Integrations tab or from a link card an agent offers in
chat (see [How account linking flows work](https://bolter.chat/help/connectors/linking-flows)). The personal link is private to the linker: admins do not see it, and
only the linker's own private agents can be granted it, with the linker's
approval, in a one to one chat.

## If you are a plain member and Slack is not connected yet

Ask a workspace owner or admin to connect the workspace's Slack first. An
agent cannot unblock this for you; only an admin can make the connection.

## What agents can do with it

With an approved grant (grants are covered in
[Connected accounts, credentials, and grants](https://bolter.chat/help/access/connected-accounts-and-grants)), an agent reads Slack as you,
within the channels and conversations the grant allows. Posting to Slack is a separate opt in on the
grant, so an agent can only post if you approved a grant that says so.

Source: https://bolter.chat/help/connectors/slack