Connect a Slack workspace and use Slack in chat
Chief can now search Slack, read the channels you have access to, and post messages, replies, DMs, and reactions with your approval.
Your team's decisions live in Slack, and until now Chief could not see any of it. You had to copy threads into chat by hand to ask a question about them.
Slack workspace connection
An organization owner opens Integrations and adds a Slack workspace. Chief gives you an app manifest to copy, a link to Slack's app creation page, and fields for the Bot User OAuth Token, client ID, and client secret. The field name matches what Slack shows on its OAuth and Permissions page, so you know which token to paste.
You then pick which projects get the workspace. A search box above the project list filters by name as you type, and your existing selections stay checked while you search.
Slack in chat
Ask about a channel, a thread, or a person and Chief searches Slack and reads what you have access to. Results come back as cards for channels, people, messages, and search hits, each with a link to open the item in Slack.
The first time a project needs it, Chief shows a Connect Slack card so you can grant your own access in a click. When your workspace app is missing a permission, the card names what is missing instead of failing silently.
Message actions with approval
Chief can post a channel message, reply in a thread, send a DM, or add an emoji reaction. Each one arrives as a confirmation card showing the channel, the message text, and a note that it posts as Chief. You approve before anything reaches Slack.
If you would rather not confirm the same action every time, turn on auto approval per action in your settings.
Connect Chief to Channels
Connecting the workspace lets Chief sign in, but Chief cannot read a channel until it is invited there. A Connect Chief to Channels section now appears after you connect, on both the org integrations page and the connect card in chat, with a copyable /invite @Chief command and an explanation of how workspace access differs from channel access.
Entities tab
Project settings has a new Entities tab listing the Slack channels, Slack people, Gmail contacts, and labels Chief has seen through your integrations, with filters, search, how often each was seen, and the connections between them. Anything drawn from your private Google data stays visible only to you.
Start by connecting a workspace in Integrations, then invite Chief to the channels you want it to work in.