Slack AI Assistant Setup: Enable, Scope, and Use It

Most setup guides fail here because they answer only one half. Someone follows a guide, cannot find the button, and assumes their workspace is broken. Usually the feature exists on a different plan tier, or it exists but an admin has it switched off, or they are looking for an installed app in the settings for the built in feature.

So this walks both paths in order: what the built in AI gives you and on which plan, how an admin turns it on or off, how to open an installed assistant, and how to stop it reading channels that should stay quiet. Every menu name here was checked against Slack's own help pages.

Worth setting expectations early. Both kinds answer when asked and go quiet afterwards. Neither owns a piece of work. If what you want is something that handles a recurring job on its own and reports back in Slack, that is an AI Employee, which is what we build at Sistava. Getting that distinction right saves the disappointment that follows a good setup.

What does Slack's built in AI actually give you?

Slack's own AI features cover conversation summaries for any channel, DM or thread, search answers with citations, huddle notes, recaps of unread channels, file summaries for text based files, and message translation. It also applies search filters automatically to plain language queries, so you do not have to remember the modifier syntax.

Which of those you get depends entirely on your Slack plan, and this is the single most common reason a setup guide seems wrong. Summaries and huddle notes reach further down the plan ladder than search answers do.

How does an admin turn AI features on or off?

Select Workspace settings from the menu, click Roles and permissions, click Feature access, and select AI. Next to the feature you want to manage, click Edit and choose whether Everyone or No one can use it. On Enterprise plans, org owners and admins can go further and limit access to specific users and groups.

Setting up an assistant in Slack, both kinds

1. Check your plan first — Before anything else, match the feature you want against the plan table above. Half of all failed setups are a plan problem wearing a settings problem's clothes.
2. Switch on the built in AI — Workspace settings, then Roles and permissions, then Feature access, then AI. Click Edit next to a feature and choose Everyone or No one.
3. Install an assistant app if you want one — Click Tools in the sidebar, or More if Tools is not there, then Apps. Search the Marketplace, then click Add to Slack. Some workspaces require an owner to approve the request.
4. Enable the app's assistant experience — Click Admin in the sidebar, then Apps and workflows. On the Installed apps page pick the app, open the App Settings tab, click Edit next to AI agent experience or AI assistant experience, choose Enabled, and click Save.
5. Open it and start a chat — From Tools, then Apps, pick the app and click New Chat, or use the Chat tab to continue an earlier one. The History tab holds previous conversations.
6. Restrict the channels it should not read — On Enterprise plans, open a channel, click the Settings tab, and next to AI use click Restrict. Do this before the rollout, not after someone notices.

There is a second way to open an assistant that is easier to remember. In split view, click Add agent in the top right corner, then either pick one of the suggested prompts or just type. A clock icon shows the message history. If several assistants are installed, that menu is where you choose between them.

Can I stop it reading certain channels?

Yes, on Enterprise plans. Open the channel, click the Settings tab, and next to AI use click Restrict or Allow, then confirm. Org owners and admins hold this permission and can grant it to workspace owners and admins. Canvas and list owners can manage AI access to their own creations.

For a canvas or a list, open it, click Share, then Advanced Settings, and check or uncheck Allow AI use. It is the same idea in a different menu, which is exactly the sort of inconsistency that makes people give up halfway.

• What the restriction blocks: AI reading that content for search answers, canvas content generation, and Slackbot responses.
• What it does not block: members can still use Slackbot to send messages into a restricted channel, or add content to a restricted canvas or list.
• It is not a substitute for channel membership: Slack states its AI features only use data members already have access to, and will not use private channels or DMs they are not part of.

What about data, training and compliance?

Slack's position is stated plainly in its own security page: customer data never leaves Slack controlled infrastructure and is never used to train large language models. It uses retrieval augmented generation instead, which means the model is given relevant content at question time rather than learning from it permanently.

Summaries and search answers are described as ephemeral. They disappear when you navigate away or close the result, and Slack says that data is not stored on devices or servers. If someone in your organization is worried about a paper trail of AI answers, that is the sentence to show them.

Data residency is the one that catches larger organizations by surprise. If your workspace stores data in Dubai or Zurich, Slack documents that AI notes in huddles are not available and transcripts for audio and video clips are not generated. Users can still upload and view clips, but the transcript never appears. No setting fixes this, because it is not a setting.

Once the plumbing is done, the interesting question is what you actually want an assistant for. If it is the daily admin, the inbox, the calendar and the follow ups nobody enjoys, that is the job a personal AI assistant is built for, and it is a different tool from a chat panel you summon. Here are two you can look at.

What the setup will not solve

It will not put knowledge into Slack that was never in Slack. A summary of a channel is only as good as what people wrote in it, and search answers cannot cite a decision that was made on a call and never typed anywhere.

• Guests get nothing. Slack states that guests cannot use AI apps or agents, so contractors on guest accounts are outside the rollout by design.
• A plan upgrade is sometimes the only fix. Search answers and recaps are not hidden behind a toggle on lower tiers, they are simply not there.
• It does not act on its own. Nothing here chases a stalled thread, follows up with a client, or notices that a task went quiet.
• It does not connect your other tools. Built in Slack AI reasons about Slack. Anything outside it needs an installed app with its own permissions.

Set it up anyway. Summaries alone pay for the twenty minutes, and the restrictions are much easier to configure on a quiet Tuesday than during an argument about privacy.

A setup order that works

Confirm the plan, switch on the built in features, restrict the two or three channels that should stay private, then install one assistant app rather than four. Tell the team what you turned on in the same message. People accept an assistant they were told about and quietly resent one they discovered.

Then watch what people ask it that it cannot do. If the pattern is "can you just handle this for me", the answer is a role rather than a panel, and you can try Sistava alongside it without removing anything you just configured. The two live together fine.

A last note on rollout order that saves arguments later. Configure the restrictions before you announce the feature, not after. Once people know AI summaries exist, the first question in any company with sensitive channels is whether it can read the HR channel, and the only good answer is one you can demonstrate in the settings screen right then. Doing it in that order turns a nervous conversation into a thirty second one.

After that, leave it alone for a fortnight. The useful signal is which features people keep using without being reminded, and you cannot see that if you are still changing settings every other day.

Sources

• Slack Help Center, Guide to AI features in Slack for the feature list and the plan availability table.
• Slack Help Center, Manage access to AI features in Slack for the Workspace settings path admins use to enable or disable AI.
• Slack Help Center, Work with AI agents and assistants in Slack for opening an assistant, the Add agent button, and guest exclusion.
• Slack Help Center, Restrict AI access to certain channels, canvases, and lists for the channel Settings path and what the restriction covers.
• Slack Help Center, Security for AI features in Slack for the training, retrieval and ephemeral response statements.
• Slack Help Center, Data residency for Slack for the regional limits on huddle notes and clip transcripts.