Home / crm-business-applications / Salesforce Certified Slack Administrator (Slack-Admn-201) / Cheat Sheet
Salesforce Certified Slack Administrator (Slack-Admn-201)

Slack-Admn-201 Cheat Sheet

Slack-Admn-201 Tests the Narrowest Control That Fits — Not the Biggest Plan or Role

For admins and owners running Slack day to day. The Spring '26 exam rewards picking the exact role, plan feature or setting a requirement needs, so stop reaching for Org Admin and Enterprise+ by reflex.

Check Your Readiness →
Among the harder certs
Avg: Not published by Salesforce
Pass: 750 / 1000
Most candidates understand Salesforce Certified Slack Administrator (Slack-Admn-201) concepts — and still fail. This exam tests how you apply knowledge under pressure.

Slack-Admn-201 Exam Domain Map (Spring '26 guide)

Questions are short requirement lists: a stakeholder need, a plan and sometimes an Enterprise Grid org. The right answer is usually the simplest built-in option the stated plan already includes. Do not study the older seven-section Slack Certified Admin outline; this Salesforce guide replaced it.

  1. 01
    Governance, Security and Compliance (22%) — retention, legal holds, exports, audit logs, DLP, information barriers, session controls
  2. 02
    App and AI Administration and Automations (20%) — Slack AI controls, app approvals, bot vs user scopes, Workflow Builder governance
  3. 03
    Fundamentals (18%) — Primary Owner vs Owner vs Admin, system roles, guests, canvases, lists, plan gating
  4. 04
    Workspace and Org Management (17%) — archive vs delete, multi-workspace and org-wide channels, org-level policies
  5. 05
    User Lifecycle Management (13%) — SAML SSO, SCIM, JIT, IdP groups, deactivation, guest expiration, Slack Connect
  6. 06
    Enabling Slack Success (10%) — analytics dashboard, active members, feature usage, champions, targeted enablement

Wrong instinct vs correct approach

A partner company that already runs its own Slack needs twenty people working with your project team for months
✕ Wrong instinct

Invite all twenty as multi-channel guests

✓ Correct approach

Use a Slack Connect channel. The partner stays in its own organization under its own admins and policies, you avoid paid guest seats, and each side can require its own connection approval.

Legal worries that switching on Slack AI will surface private channel content to the wrong people
✕ Wrong instinct

Keep every AI feature disabled for the whole org

✓ Correct approach

Slack AI is permission-aware and only draws on content the requesting user can already open. Enable selected features for a pilot group through the AI feature controls and expand once feedback and change management are handled.

Security spots unusual file downloads from one account and must investigate who did what
✕ Wrong instinct

Review the analytics dashboard for that member

✓ Correct approach

Analytics shows usage trends, not security events. Audit logs on Enterprise+ record sign-ins, downloads and admin actions, viewable in the admin interface or streamed by API to a SIEM for alerting.

Channel sprawl is hurting search and leadership wants dormant channels cleaned up
✕ Wrong instinct

Delete every channel with no activity in six months

✓ Correct approach

Archive them. Archived channels leave active lists yet stay searchable and can be restored, while deletion destroys history permanently. Add naming prefixes and a Channels Admin system role to govern new channel creation.

A team lead needs to manage membership and settings of one project channel only
✕ Wrong instinct

Promote the lead to Workspace Admin

✓ Correct approach

Assign the lead as Channel Manager for that channel. It grants exactly the needed powers; on Enterprise Grid, narrow system roles such as Channels Admin or Users Admin cover broader but still bounded duties.

Know these cold

  • ▸ SSO authenticates, SCIM provisions and deprovisions, JIT only creates accounts on first sign-in
  • ▸ Offboard by deactivating the account, never deleting it; history and files stay for compliance
  • ▸ Single-channel guest gets one channel; multi-channel guest is billed like a full member
  • ▸ Archive keeps history and can be restored; delete is permanent and rarely the right answer
  • ▸ Org-level policy on Enterprise Grid locks workspace settings; change the policy, not the workspace
  • ▸ Legal hold preserves one custodian going forward; an export is only a snapshot
  • ▸ Full exports start at Business+; single-user exports, audit logs, DLP and legal holds need Enterprise+
  • ▸ User scopes act as the installer and carry more risk than bot scopes
  • ▸ App update requesting new scopes means a fresh approval review against policy
  • ▸ Canvas for living reference docs, List for tracked work items, pinned message for neither

Can you answer these without checking your notes?

In this scenario: "A partner company that already runs its own Slack needs twenty people working with your project team for months" — what should you do first?
Use a Slack Connect channel. The partner stays in its own organization under its own admins and policies, you avoid paid guest seats, and each side can require its own connection approval.
In this scenario: "Legal worries that switching on Slack AI will surface private channel content to the wrong people" — what should you do first?
Slack AI is permission-aware and only draws on content the requesting user can already open. Enable selected features for a pilot group through the AI feature controls and expand once feedback and change management are handled.
In this scenario: "Security spots unusual file downloads from one account and must investigate who did what" — what should you do first?
Analytics shows usage trends, not security events. Audit logs on Enterprise+ record sign-ins, downloads and admin actions, viewable in the admin interface or streamed by API to a SIEM for alerting.

Common Exam Mistakes — What candidates get wrong

Expecting SAML SSO to switch off departed employees automatically

SSO only governs sign-in. SCIM provisioning is what deactivates the Slack account when the directory record changes, and JIT provisioning only creates accounts on first login. Offboarding automation at scale means SCIM, not SSO or JIT.

Recommending Enterprise+ whenever identity or compliance appears in the question

Business+ already covers SAML SSO, SCIM and full exports of all conversations. Enterprise+ earns its cost only for audit logs, native DLP, legal holds, single-user exports or enterprise search. Match the plan to the named requirement.

Treating any Workspace Owner as able to delete or transfer the workspace

Workspace deletion and transfer of primary ownership belong to the single Primary Owner. Owners handle settings, security and billing; Admins handle members and channels and cannot change most workspace-wide policies by default.

Using an export or org-wide retention change to preserve one person's data

An export is a point-in-time snapshot, and raising org retention keeps everyone's data longer. A legal hold, run by the Legal Holds admin role on Enterprise+, preserves only the named custodian's messages and files going forward.

Re-adding a user in Slack when an IdP group controls membership

Once an identity provider group is connected to a workspace or private channel, the next sync reverses manual changes. Fix membership in the directory. Likewise, an org-level policy on Enterprise Grid overrides whatever the workspace setting shows.

Resources to help you pass Salesforce Slack Administrator on your first attempt

Slack-Admn-201 rewards picking the right role, plan and control. Find your weak spots.