Salesforce Certified Slack Administrator (Slack-Admn-201) Exam Topics and Questions

Fundamentals carries the heaviest single share of the exam at 18 percent, and it punishes assumptions about how Slack works. You need to match requirements to features, assign the right access level, distinguish admin from owner responsibilities, and know when each plan tier unlocks what you need. The trap is treating Slack like email or another chat tool.

– Features, requirements and plan boundaries

The exam gives you a scenario and asks which feature solves it. That means knowing what workflows, canvas, huddles, clips and scheduled send actually do, and where they stop. A candidate who has only used Slack casually will guess based on the feature name. The pass comes from knowing the constraints: which features need Enterprise Grid, which work on Business Plus, and which drop away on the free tier. Plan selection questions hinge on user count, compliance needs, and whether the organization requires centralized identity management or data residency controls. You also face questions that describe a requirement and expect you to name the Slack capability that satisfies it, not the workaround someone built with a third-party app.

– Access levels and role boundaries

Access questions test whether you know the difference between workspace owner, workspace admin, org owner, org admin, and the various channel-level roles. Each has a distinct permission set, and the exam will describe a task then ask which role can perform it. Candidates lose marks by conflating admin and owner, or by assuming that being an admin in one workspace grants any privilege in another. The exam also covers when to make someone a multi-channel guest versus a full member, and when a single-channel guest is the right call. You need to know what each level can see, what they can configure, and what actions require elevation. The distinction between primary owner and workspace owner matters in deprovisioning and plan management scenarios.

How Fundamentals is tested

At 18 percent, this topic produces roughly one in every six items. Questions present a business requirement and a set of constraints, then ask you to choose the feature, role, or plan tier that fits. The exam avoids abstract definitions and instead describes a situation: a team needs to record async updates, or an admin must control who installs apps, or an organization must meet data residency rules. You lose marks by picking a feature that sounds right but lacks the required capability, or by choosing a plan tier that does not support the control being asked for. The other common mistake is assigning a role that has too much access or too little, because you did not distinguish owner from admin or guest from member. The weight means you cannot afford to skip plan comparison or role boundaries. Miss this topic and you are chasing a pass from a deficit.

User lifecycle management picks up where Fundamentals left off, focusing on provisioning, access assignment, and deactivation across the user's entire tenure. You will handle onboarding flows, authentication methods, identity provider group mappings, guest account scoping, and the mechanics of removing access when someone leaves. The exam tests whether you can choose the right provisioning method for the plan in use and configure user groups that meet the scenario's access requirements.

– Provisioning, authentication and onboarding

Provisioning questions describe an organization's identity setup and ask how to get users into Slack with the correct workspace and channel memberships. You need to know when to use SCIM, when to rely on email domain claiming, and when manual invite is the only option. Authentication scenarios cover SAML SSO requirements, session duration policies, and how plan tier affects which methods are available. The exam will present a scenario where users must land in specific channels on arrival, and you must choose between default channels, user group automation, or a provisioning attribute that drives assignment. Onboarding also includes determining whether a user should be a full member, a multi-channel guest, or a single-channel guest based on their role and the data they need to access.

– Access levels, roles and user groups

You will see scenarios that describe a job function and ask which role or permission set fits. The exam tests whether you understand the difference between workspace-level roles, channel-level roles, and the permissions inherited from user group membership. User group questions present a set of channels and permissions, then ask whether the group configuration meets the stated requirement. Candidates lose marks by granting workspace admin when channel manager would suffice, or by creating a user group that does not cascade the right default channels. The exam also covers Slack Connect and guest provisioning: when to use each, what access boundaries apply, and how to scope permissions so external users see only what they should.

– Identity provider integration and deactivation

Managing IdP groups after configuration means knowing how group membership changes flow into Slack, which attributes control workspace access, and when to re-sync or manually adjust. The exam presents a scenario where an IdP group is renamed or deleted, and you must determine the impact on workspace membership. Deactivation questions test whether you know the difference between deactivating a user, removing them from a workspace, converting them to a guest, and fully deleting the account. Each action has different consequences for message history, channel membership, and license count. You also need to know who has the authority to deactivate, and what happens to content owned by a deactivated account.

How User Lifecycle Management is tested

At 13 percent, this topic produces one in eight items. Questions describe a user's role, the organization's identity setup, and a requirement, then ask you to choose the provisioning method, access level, or deactivation process that fits. The exam avoids asking what SCIM stands for and instead gives you a scenario where users must be auto-provisioned from an IdP, then asks which plan and configuration are required. You lose marks by choosing an authentication method unavailable on the plan in the scenario, or by deactivating when the requirement was to convert to guest and retain message history. User group questions are a frequent trap: the exam describes a set of permissions and asks whether the group meets the requirement, and the error is in a default channel assignment or a missing user type restriction. The weight is moderate but the detail required is high, and provisioning mistakes are hard to recover from in a timed environment.

Workspace and org management is the second-heaviest topic at 17 percent, and it tests your ability to configure channels, manage cross-workspace access, adjust workspace-wide settings, and set up Slack Connect. The domain spans single-workspace administration and Enterprise Grid scenarios where users belong to multiple workspaces. You need to know which permissions unlock which management tasks, and how settings cascade or override across the org.

– Channel management and cross-workspace permissions

Channel management questions describe a requirement to create, archive, convert, or restrict a channel, then ask who can perform the action or which setting must change. You need to know the difference between public and private channels, when a channel can be converted, and what happens to membership and message history during conversion. The exam also covers channel posting permissions, retention policies applied at the channel level, and who can manage channel membership. Cross-workspace channels introduce another layer: you must know which role can create or manage a channel that spans workspaces, and how permissions differ when the channel is shared versus when it is a single-workspace channel that users from other workspaces join. Enterprise Grid scenarios test whether you understand org-level versus workspace-level control.

– Workspace settings, multi-workspace access and Slack Connect

Workspace settings questions present a feature that is unavailable to members, and you must identify which permission or policy is blocking it. The exam tests retention settings, app installation permissions, file sharing controls, and whether a setting is managed at the workspace or org level. Multi-workspace access scenarios ask how to grant a user access to additional workspaces, how to manage their profile and preferences across workspaces, and what happens when they are deactivated in one workspace but not another. Slack Connect configuration questions describe an external collaboration requirement and ask how to set up the channel, what approval workflow applies, and which permissions the external users receive. You also need to know when Slack Connect is restricted by org policy, and how to adjust that policy to allow specific domains or channels.

How Workspace and Org Management is tested

At 17 percent, this topic is close behind Fundamentals in weight and produces roughly one in every six items. Questions give you a workspace configuration problem and ask which setting to adjust, which role is required, or how to set up a channel that meets the scenario's constraints. The exam avoids theoretical questions about what a setting does and instead describes a situation where members cannot post in a channel, or an admin cannot create a cross-workspace channel, or an external partner needs access to three channels but not the whole workspace. You lose marks by choosing a workspace-level setting when the control is at the org level, or by granting a permission that is too broad for the requirement. Slack Connect questions are a frequent source of error because candidates confuse the channel type with guest access or assume that external users inherit the same permissions as internal members. The weight means you must be confident in both single-workspace and Enterprise Grid mechanics.

App and AI administration is the single heaviest topic at 20 percent, and it focuses on app installation workflows, approval policies, scope evaluation, and Slack AI implementation. The exam expects you to know how to control which apps can be installed, how to review and approve requests, and how to assess whether an app's permissions comply with organizational security policy. You also face scenarios that ask how to configure Slack AI given the plan and data residency requirements.

How App and AI Administration and Automations is tested

At 20 percent, this topic produces one in every five items and is the single largest contributor to your score. Questions describe an app installation request, list the scopes the app requires, and ask whether the request should be approved given the organization's security policy. You must know what each scope grants, which scopes are high-risk, and when to deny or request a scope reduction. App approval workflow questions test whether you know the difference between unrestricted installation, admin approval required, and app restriction by allowlist or blocklist. Slack AI scenarios describe a deployment requirement and ask which plan supports it, how to enable it for specific users or workspaces, and what data residency or compliance constraints apply. The exam avoids asking what Slack AI does and instead focuses on configuration steps, permission requirements, and policy alignment. You lose marks by approving an app whose scopes violate the stated policy, or by configuring Slack AI in a way that breaches data residency rules. The weight means this topic alone can determine whether you pass, and you cannot afford to guess on scope evaluation.

Governance, security and compliance is the heaviest topic on the exam at 22 percent, and it tests your ability to configure policies, manage message retention and export, track security incidents, control PII sharing, decide when to migrate to Enterprise Grid, and moderate content. This domain separates administrators who understand regulatory requirements from those who only manage day-to-day access. You need to know which controls are available on which plans, and how to apply them without breaking workflows.

– Security policies and compliance controls

Security policy questions describe an organization's requirements for session management, mobile device access, two-factor authentication, data loss prevention, and file sharing, then ask how to configure Slack to meet them. You need to know which policies are enforced at the org level versus the workspace level, which settings require Enterprise Grid, and how to restrict external sharing without blocking Slack Connect channels that are already approved. Compliance scenarios focus on message retention, legal hold, export workflows, and eDiscovery. The exam presents a regulatory requirement or a legal request and asks how to configure retention policies, apply a legal hold to specific users or channels, or export message history in a compliant format. You must know the difference between workspace-level and org-level retention, and what happens to messages when a user is deactivated or a channel is archived.

– PII, security tracking and Enterprise Grid migration

PII scenarios describe a situation where sensitive data may be shared in Slack, and you must determine how to prevent it, detect it, or respond to a breach. The exam tests whether you know how to configure data loss prevention policies, restrict file uploads, and use audit logs to track who accessed or shared specific content. Security tracking questions present an incident and ask how to investigate it using Enterprise Grid audit logs, discovery APIs, or session history. You need to know what events are logged, how long logs are retained, and which role has access to them. Enterprise Grid migration questions describe a workspace that has outgrown its plan and ask when to migrate, what prerequisites must be met, and what changes during the migration. The exam focuses on the decision criteria, not the migration procedure itself.

– Content moderation and code of conduct enforcement

Moderation scenarios present a message or conversation that violates the organization's code of conduct, and you must determine how to respond. The exam tests whether you know how to remove a message, restrict a user's posting ability, escalate to workspace or org owners, and document the incident. You also face questions about proactive moderation: configuring restricted words, setting up approval workflows for specific channels, and using third-party moderation tools where native controls are insufficient. The exam distinguishes between handling a one-time violation and configuring a policy to prevent recurrence.

How Governance, Security and Compliance is tested

At 22 percent, this is the single heaviest topic and determines the outcome more than any other. Questions describe a compliance requirement, a security incident, or a policy gap, then ask how to configure Slack to address it. The exam avoids abstract policy definitions and instead presents a scenario where a healthcare organization must retain messages for seven years, or a financial services firm must prevent PII from being posted in public channels, or an admin must investigate who accessed a confidential file. You lose marks by choosing a control that is unavailable on the plan in the scenario, or by applying a retention policy that does not meet the stated requirement. PII and DLP questions are a frequent trap because candidates assume Slack has native content scanning, when in fact most detection requires a third-party app or manual audit log review. The weight means you cannot pass without strong coverage of retention, export, audit logs, and policy configuration.

Enabling Slack success is the lightest topic at 10 percent, but it tests a skill set that many technical administrators overlook: monitoring adoption, interpreting user feedback, aligning features to business needs, and building a champion network. The exam expects you to know which analytics are available, how to read them for adoption signals, and how to respond when a feature is underused or a workflow is failing.

How Enabling Slack Success (Analytics and Adoption) is tested

At 10 percent, this topic produces one in every ten items, making it the lightest section. Questions describe a situation where adoption is low, a feature is unused, or users report confusion, and you must choose the right metric to monitor, the right feedback mechanism, or the right intervention. The exam tests whether you know which analytics are available in workspace or org analytics, what each metric indicates, and how to interpret a trend. You also face scenarios that describe a business unit's workflow and ask which Slack feature aligns with it, or how to configure a champion network to drive adoption across teams. Candidates lose marks by choosing a metric that does not measure the stated goal, or by recommending a feature that does not fit the workflow described. The exam avoids asking you to calculate adoption rates or define what a champion is, and instead focuses on practical decisions: which report to pull, which feedback to act on, and which feature to promote. The weight is low, but the questions are straightforward if you understand workspace analytics and change management basics.