Overview
App and AI Administration and Automations carries 20% of the exam through only three objectives: implement Slack AI, manage app installation and approvals, and evaluate app scopes for compliance with security policies. The section title also brings automation into scope, which in practice means Workflow Builder and the permissions around who can build, publish and connect workflows.
Slack AI includes summaries, recaps, search answers, translations, huddle notes and the AI-powered Slackbot, with features varying by plan and controllable by owners and admins. AI agents, including Agentforce agents and apps connected through the Model Context Protocol, add another layer to govern. App management covers app approval settings, approved and restricted app lists, app request workflows and app managers, and on Enterprise Grid org-level app policies. Scope evaluation asks whether the permissions an app requests, such as reading all public channel history, are justified and acceptable under company policy.
How it's tested
Expect scenarios where a team asks for an app or AI capability and security or compliance has concerns. You choose how to enable it, who approves it, which scopes are acceptable, and what limits apply. Correct answers balance adoption with control, often through approval workflows, restricted scopes or phased rollouts.
-
Roll out AI safely
Leadership wants Slack AI, and you choose the plan, the admin controls and the pilot or phased approach that fits the stated concerns.
-
App request handling
Members want to install apps freely, and you configure approvals, app managers or an approved list instead of blocking everything.
-
Scope review
An app requests permissions, and you judge whether each scope is needed for its stated purpose and allowed by policy.
A team requests a meeting-notes app that asks to read messages in all public channels, post messages and access user email addresses. Its stated purpose is posting summaries into one channel. Reading every public channel and email addresses exceeds that purpose, so the administrator should ask the developer for narrower scopes or restrict the app before approval, rather than approving the full request or blocking app installs entirely.
Objectives 3
Official objectives from the Salesforce outline, in outline order.
4.1 Given a scenario, determine how to implement Slack AI.Enabling, controlling and rolling out AI features.
- What it means
- Slack AI covers channel and thread summaries, recaps, AI search answers, translations, file summaries, huddle notes, workflow generation and the AI-powered Slackbot. Under the current plans, Pro includes summaries and huddle notes, Business+ and Enterprise+ include the broader set, and Enterprise+ adds enterprise search across connected tools.
- What to understand
- Implementation is a governance decision as much as a switch. Owners and admins can turn individual AI features on or off for a workspace or org, and can limit some features to selected people. Slack AI respects existing permissions, so it only uses content the requesting user can already access, and Slack states that customer data is not used to train the underlying models. A pilot with a champion group, clear guidance and feedback collection is the usual recommended rollout.
- How it shows up
- An organization wants AI summaries and search but legal is cautious, and you choose controls, scope and rollout order.
- Common confusion
- Believing Slack AI can surface private channel content to users who are not members of that channel.
4.2 Assess a given scenario to determine how to manage app installation and approvals.Approval settings, app managers and app lists.
- What it means
- Admins can let members install apps freely, require approval for all apps, or approve some apps in advance and restrict others. App requests can be routed to app managers, and on Enterprise Grid, org admins can approve or restrict apps for the whole organization and decide whether workspaces can install them.
- What to understand
- The balanced answer is usually app approval with a pre-approved list for common tools and named app managers to handle requests quickly. Restricted apps cannot be installed until the restriction is lifted. Custom apps built for the company and workflow steps from apps follow the same governance. Removing an app also removes its access to data.
- How it shows up
- Security wants control over integrations, while teams complain that requests take weeks, and you choose the approval model.
- Common confusion
- Turning off all app installs, which blocks business needs instead of governing them.
4.3 Given a scenario, evaluate the app scopes for compliance to security policies.Reading OAuth scopes against policy.
- What it means
- Scopes are the OAuth permissions a Slack app requests, such as reading public channel history, reading private channels it is invited to, posting messages, reading user profiles or email, or acting on behalf of users. Admins see requested scopes when reviewing an app.
- What to understand
- Judge each scope against the app's purpose and the company's policy. Bot scopes act as the app itself; user scopes act on behalf of the person who installs it and are more sensitive. Broad read scopes on history, files or email deserve scrutiny, and a scope change during an app update triggers a new approval. When an app asks for more than it needs, request narrower scopes or decline.
- How it shows up
- An app's scope list includes access to all messages or user email, and you decide whether that is acceptable for its stated purpose.
- Common confusion
- Assuming an approved app's scopes stay fixed; new scopes after an update require review.
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
Slack AI feature controls
Owner and admin settings that turn individual AI features on or off.
- Remember
- Features can be enabled selectively rather than all at once.
- Tested as
- AI rollout and caution scenarios.
- Trap
- Assuming AI is all-or-nothing.
-
Permission-aware AI
Slack AI only draws on content the requesting user can already access.
- Remember
- AI does not bypass channel membership or private channels.
- Tested as
- Legal or privacy objections to AI.
- Trap
- Believing AI exposes private channels.
-
AI by plan
Pro includes summaries and huddle notes; Business+ and Enterprise+ include the broader AI set.
- Remember
- Enterprise search is limited to Enterprise+.
- Tested as
- Plan-fit AI questions.
- Trap
- Recommending an AI add-on that is no longer sold on the website.
-
Slackbot as AI assistant
Slackbot can answer questions, find information and take actions using AI.
- Remember
- It works inside the same access boundaries as the user.
- Tested as
- Productivity and AI enablement scenarios.
- Trap
- Treating it as the old rules-only bot.
-
Model Context Protocol (MCP)
An open standard that lets AI tools connect to apps and data sources.
- Remember
- Connections are still governed by app approvals and admin settings.
- Tested as
- Questions about connecting AI to other tools.
- Trap
- Assuming MCP connections skip app governance.
-
App approval
A setting requiring admin or app manager approval before an app is installed.
- Remember
- Pre-approve common apps to keep requests moving.
- Tested as
- App sprawl and integration control.
- Trap
- Blocking all apps instead.
-
Restricted app
An app admins have blocked from installation.
- Remember
- Restriction remains until an admin lifts it.
- Tested as
- Policy violation scenarios.
- Trap
- Thinking a member can install it by request alone.
-
App managers
People allowed to approve or manage app requests.
- Remember
- They speed approvals without full admin rights.
- Tested as
- Slow request backlog scenarios.
- Trap
- Making every requester an admin.
-
Bot vs user scopes
Bot scopes act as the app; user scopes act as the installing person.
- Remember
- User scopes are more sensitive.
- Tested as
- Scope review questions.
- Trap
- Treating both scope types as equal risk.
-
Workflow Builder governance
Settings that control who can create and publish workflows and which connectors they use.
- Remember
- Workflows that use app steps follow app approval rules.
- Tested as
- Automation enablement scenarios.
- Trap
- Assuming workflows bypass app governance.
-
Agentforce in Slack
Salesforce AI agents that work in Slack conversations and can take actions in connected systems.
- Remember
- Agents are installed and governed as apps, with their own permissions.
- Tested as
- Questions about AI agents acting on business data.
- Trap
- Assuming agents inherit full admin access.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
App installation models
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Open installs | Any member can install apps | Fast, least control | Choosing it when security requires oversight |
| App approval | Requests go to admins or app managers | Balanced control | Leaving no pre-approved apps, causing backlogs |
| Pre-approved list | Selected apps installable without a request | Speeds common tools | Approving apps without reviewing scopes |
| Restricted apps | Blocked from installation | Firm no for policy violations | Using it for every unknown app |
Scope types
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Bot scopes | Permissions the app uses as itself | Limited to where the bot is added for many actions | Ignoring broad read scopes |
| User scopes | Permissions the app uses on behalf of a person | Inherit that person's reach | Underestimating the risk |
| Scope changes on update | New permissions requested later | Trigger review and reapproval | Assuming earlier approval covers them |
Ways to automate or assist
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Workflow Builder | No-code automation with triggers, forms and steps | Deterministic, repeatable processes | Using AI where a fixed process fits |
| Slack AI features | Summaries, recaps, search answers, translations | Assist people with information | Expecting them to run processes |
| AI agents | Agentforce agents and connected AI apps | Can reason and take actions | Deploying without reviewing their permissions |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Block everything
- What candidates pick
- Disable all app installs to satisfy security.
- Why it looks right
- It removes risk instantly.
- Why it's wrong
- It stops legitimate work and pushes teams toward unmanaged tools; app approval with scope review meets the security goal.
Clue to watch for The scenario says business teams still need integrations.
-
Approve because it is popular
- What candidates pick
- Approve the app since many companies use it.
- Why it looks right
- Popularity suggests safety.
- Why it's wrong
- Approval depends on whether the requested scopes fit the purpose and your policy, not on market share.
Clue to watch for The scenario lists broad scopes such as reading all history or email.
-
AI sees everything
- What candidates pick
- Keep AI off because it could expose private channels.
- Why it looks right
- Fear of data exposure is common.
- Why it's wrong
- Slack AI is permission-aware and only uses content the user can already access, so the concern is addressed by existing access controls.
Clue to watch for Legal worries about private channel leakage.
-
Turn AI on for all
- What candidates pick
- Enable every AI feature for every member at once.
- Why it looks right
- It maximizes value quickly.
- Why it's wrong
- When concerns or change-management needs are stated, a phased rollout with selected features and a pilot group fits better.
Clue to watch for The scenario mentions caution, training or feedback.
-
Old approval covers updates
- What candidates pick
- Leave an approved app as is after its update requests new scopes.
- Why it looks right
- It was already approved.
- Why it's wrong
- New scopes change what the app can access and must be reviewed against policy again.
Clue to watch for The app's update adds permissions.
-
Workflows need no review
- What candidates pick
- Let any member publish workflows with any app connector.
- Why it looks right
- Workflow Builder is no-code and seems low risk.
- Why it's wrong
- Connector steps move data into other apps, so they follow app approval rules and admin settings.
Clue to watch for A workflow sends Slack data to an external tool.
Answer framework
When an app, AI or automation request appears, run through these five steps.
- Clarify the business goal and decide whether it calls for Workflow Builder automation, a Slack AI feature, an AI agent or a third-party app.
- Check that the customer's plan includes the feature, noting AI differences between Pro, Business+ and Enterprise+.
- For any app or agent, read the requested scopes and compare each one to the stated purpose and the security policy.
- Pick the governance control that fits: approval with app managers, a pre-approved list, a restriction, or feature-level AI settings.
- Prefer a phased rollout with a pilot group, training and feedback when the scenario mentions risk, change management or user concerns.
Practice question
Want more like this? The Slack-Admn-201 practice test has questions for every domain.
Checklist
0 of 12
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
Give this section a large share of your time, since three objectives carry a fifth of the exam. Start with app governance: complete the App Governance in Slack badge, then in a trial workspace switch on app approval, request an app as a member and approve it as an admin. Read the scopes shown on a few real app listings and decide, for each, whether you would allow it for a narrow purpose.
Next, study Slack AI using the Slack AI badge, the Slackbot quick look and Slack's admin adoption guide for AI. Build a table of AI features by plan from the current plans and features article, and note which controls admins have over each feature. Read the help articles on security for AI features and on the Model Context Protocol so you can explain how data access is limited.
Finish with Workflow Builder: build a form-triggered workflow that posts to a channel and adds an item to a list. Highest-yield ideas are permission-aware AI, the approval model and scope review. Most often underestimated is how quickly AI plan packaging changed in 2025.
FAQ
How much of the exam does App and AI Administration and Automations cover?
App and AI Administration and Automations is 20% of the exam, about twelve of the 60 scored questions as a planning estimate, from only three objectives.
Is Workflow Builder tested even though no objective names it?
The section title includes automations, and the official trail includes a Workflow Builder module, so expect questions on when to use workflows and how to govern them.
Do I need to know Agentforce for this exam?
The guide does not name Agentforce. Know that AI agents can work in Slack, are installed and governed like apps, and should be reviewed for the data and actions they can reach.
Is the Slack AI add-on still a thing?
Slack stopped selling the AI add-on on its website after the 2025 plan changes and moved AI features into the plans. Answer plan questions with the current packaging.
Does Slack AI train on our messages?
Slack states that customer data is not used to train the underlying large language models, and AI features only use data the user can already access.
How deep is the scope knowledge required?
You do not need to memorize every scope name. You must recognize broad or sensitive permissions, such as reading all history or user email, and judge them against a stated purpose.
Other CRM & Business Applications certifications
Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.
- HubSpot Inbound Marketing Certification Study guide
- Salesforce Certified Platform Developer I Study guide
- Google Ads Search Certification Study guide
- ServiceNow Certified System Administrator Study guide
- Salesforce Certified Platform Administrator Study guide
- ServiceNow Certified Application Developer Study guide
Test your Domain 4 knowledge
You have covered Slack AI rollout, app approvals, scope evaluation and workflow governance. Check how well you balance adoption and control in timed questions.
Keep going
- Training Training Built on your Weak areas
- Practice test Questions by domain, with explanations
- Mock exam Full length, timed like the real exam
- Readiness test Find your weakest domain in minutes
- Cheat sheet Key terms and formulas on one page
- Ask the Slack-Admn-201 AI tutor Get any concept explained your way