Connect Slack to ChatGPT: Setup, Permissions, Limits

The search itself is ambiguous, which is why the results are confusing. "Connect Slack to ChatGPT" can mean you want ChatGPT sitting inside Slack where your team talks, or it can mean you want ChatGPT, in its own window, to be able to see what happened in Slack. Those are two different switches in two different places.

This guide covers both, in order, with the permission screens explained in plain language. It also covers the parts nobody warns you about: the approval your workspace admin may have to give, why the app can see some channels and not others, and the compliance settings that will quietly block the install in a larger company.

It is worth saying up front what this kind of setup is and is not. A chat assistant in Slack answers when you ask. It does not own a job. If what you actually want is something that handles a recurring piece of work without being prompted every time, that is a different shape of tool, and it is the shape we build at Sistava. Both are useful. Knowing which one you are installing saves a week of disappointment.

What does connecting Slack to ChatGPT actually do?

Once the ChatGPT app is installed in Slack, you get a one to one chat with ChatGPT in a dedicated sidebar inside Slack. From there it can summarize long threads into action items, draft posts and replies, and search the Slack messages and files you already have access to. Conversations you start in Slack can also show up in ChatGPT so you can pick them back up later.

The app and the connector are two different things

The Slack app puts ChatGPT inside Slack. The Slack connector, which you turn on from inside ChatGPT, lets ChatGPT reach into Slack while you are chatting in ChatGPT. If you installed the app and then wondered why ChatGPT on the web still knows nothing about your workspace, this is the reason. You need the connector too.

How do I install the ChatGPT app in Slack?

You install it the same way as any Slack app. Click Tools in the sidebar, click Apps, search for ChatGPT, click Add, then click Add to Slack and follow the prompts. If your sidebar shows More instead of Tools, use that. Some workspaces show an Automations tab in that spot instead.

Installing the ChatGPT app, start to finish

1. Open the app browser in Slack — Click Tools in the sidebar, or More if Tools is not there, then click Apps. This opens the Slack Marketplace inside Slack.
2. Find the official listing — Search for ChatGPT and check the publisher before installing. There are several unofficial apps with similar names and similar icons.
3. Click Add, then Add to Slack — Slack shows you the permission categories the app is asking for. Read them. This is the only screen where you see them all in one place.
4. Approve, or send a request — By default any member of a Slack workspace can install an app. If your workspace requires approval you will be asked to add a message explaining why, then click Submit, and an owner reviews it.
5. Connect your ChatGPT account — Sign in when prompted. The Slack side and the ChatGPT side are separate accounts, and the app is not useful until both are linked.
6. Turn on the connector separately — If you also want ChatGPT on the web to see Slack, open your ChatGPT settings and enable the Slack connector there. Installing the Slack app does not do this for you.

The install takes about two minutes. The approval, if your workspace needs one, takes as long as your admin takes. Plan for that rather than being surprised by it, especially if you are trying to demo this to your team on a Friday afternoon.

Who has to approve it?

By default, any member of a Slack workspace can install an app, so often nobody has to approve anything. But workspace owners can turn on app approval, and many do. When approval is on, your install becomes a request with a note attached, and an owner accepts or declines it.

Owners manage this under Admin in the sidebar, then Apps and workflows, then App Management Settings. One setting there is worth knowing about even as a normal user: owners can choose to only allow apps from the Slack Marketplace, which blocks anything installed by direct link.

• Enterprise Grid organizations add another layer. An org level admin usually has to allow the app before individual workspaces can add it, so a workspace owner saying yes may still not be enough.
• ChatGPT has its own admin side. On business and enterprise ChatGPT plans, an owner or admin may need to enable the Slack app and grant access to specific users or groups before anyone can sign in.
• Guests are excluded. Slack states that guests cannot use AI apps or agents, so a multi channel guest in your workspace will not see the assistant at all.

Which messages can it actually read?

Only what you can already see. The Slack Marketplace listing is explicit about it: ChatGPT respects Slack's existing permissions, and only the messages and files you can already see are searchable. Installing it does not hand ChatGPT a master key to the workspace.

The permission screen lists broad categories rather than exact scopes, which is why it looks alarming. It asks to view content and info about you, about channels and conversations, and about your workspace, and to perform actions in the same three places. Those categories cover the ceiling of what the app could ask for, filtered down by what your own account can reach.

Private channels behave differently from public ones and this trips up almost everyone. An app cannot read a private channel it has not been invited into. You invite it the same way you invite a person, by typing a slash invite command with the app name in that channel, or through the channel's integrations menu. You repeat that per private channel. There is no bulk switch.

Direct messages between other people are never in scope. If two colleagues discussed something in a DM, the assistant cannot see it, summarize it, or find it, regardless of what permissions you granted.

So far this is all one shape of tool: you ask, it answers. The other shape is a coworker you hand a job to. That is what we build at Sistava, where you hire an AI Employee with a role and a brief, connect Slack as one of the places it can be reached, and it keeps working between your messages instead of only during them. Here is what that looks like when you pick a role.

What this setup will not do

It will not act unless you ask. A chat assistant in a sidebar has no schedule, no queue, and no memory of a job you gave it last Tuesday. It answers, then it waits. That is the single biggest gap between what people expect from "connect Slack to ChatGPT" and what they get.

• It will not read what you cannot read. Useful for privacy, frustrating when the answer lives in a channel you were never added to.
• It will not survive a compliance block. Organizations with strict data residency or app approval settings can prevent the install entirely, and there is no user side workaround.
• It will not know your business by default. Out of the box it knows the conversation in front of it. Your pricing, your policies and your customers are not in there unless you paste them in every time.
• It will not own an outcome. Nobody is chasing the client who went quiet. It drafts the message, you still have to notice it is needed.

Where to start

Install it in one channel first, not ten. Pick the channel where people ask each other the same question most often, watch what it gets right for a week, and pay attention to the moments where someone asks it for something and it politely cannot help. Those moments are the useful data.

If the pattern you keep hitting is "I want this to happen without me asking", the gap is not a settings problem, it is a category problem. That is when it is worth trying an AI Employee instead: one you brief once, give a job to, and reach in Slack among other places, rather than a chat window that resets between questions.

One last practical note. Whatever you install, tell your team it is there and tell them what it can see. The fastest way to make a workspace assistant unwelcome is to have people discover it after the fact and assume it has been reading everything. Two sentences in a channel post prevents a week of quiet suspicion, and it usually doubles the number of people who actually try it.

Then give it one real job for a week. Not a demo question, a genuine piece of work someone on the team is tired of doing. That is the only test that tells you whether the connection is worth keeping.

Sources

• Slack Marketplace, ChatGPT listing for what the app does and the permission categories it requests.
• Slack Help Center, Add apps to your Slack workspace for the install steps and the app approval request flow.
• Slack Help Center, Manage app installation settings for the owner controls and the Marketplace only restriction.
• Slack Help Center, Work with AI agents and assistants in Slack for how assistants are opened and the note that guests cannot use them.
• Slack developer docs, conversations.history for why an app can only read conversations it is a member of.
• OpenAI Help Center, ChatGPT app in Slack for the current plan requirements, which we deliberately did not restate here.