Overview
Workspace and Org Management has five objectives. You must decide how to manage channels, identify the permission needed to manage cross-workspace channels, find the setting that lets every member of a workspace use a feature, manage a user account's access to multiple workspaces, and configure a Slack Connect channel.
Channel management includes naming conventions and prefixes, public versus private channels, converting a channel or a group DM, archiving instead of deleting, posting permissions, channel managers and moving channels between workspaces. On Enterprise Grid you also work with multi-workspace and org-wide channels, workspace design and consolidation, and org-level policies that override workspace settings. Slack Connect adds external organizations, with admin approval, invitation permissions and controls on what external members can share. Questions assume you know where each setting lives and which role can change it.
How it's tested
Scenarios describe channel and workspace problems: duplicate channels, a feature some members cannot use, a channel that must reach two business units, or a partner that needs a shared space. You decide the action, the setting, or the role that is required, usually at the org level on Enterprise Grid.
-
Channel lifecycle decision
A channel must be renamed, converted, archived, moved or deleted, and you pick the action that keeps history and access correct.
-
Setting locked above you
A feature is unavailable to members, and you identify whether the workspace setting or an org-level policy must change.
-
Crossing boundaries
Work spans workspaces or companies, and you choose a multi-workspace channel, a move, or a Slack Connect channel with the right approvals.
Sales and support sit in separate workspaces on Enterprise Grid, and both need one escalation channel. Creating twin channels splits the conversation, and moving the channel would cut off whichever workspace lost it. A multi-workspace channel shared to both workspaces keeps one history visible to both teams. Sharing it requires an Org Owner, Org Admin or a Channels Admin role, so a Workspace Admin in sales alone cannot complete it.
Objectives 5
Official objectives from the Salesforce outline, in outline order.
3.1 Given a scenario, determine how to manage channels.Naming, privacy, conversion, archiving and posting rights.
- What it means
- Channel management covers creating channels with consistent names and prefixes, choosing public or private, converting channels and group DMs, setting who can post, assigning channel managers, archiving inactive channels and, rarely, deleting them.
- What to understand
- Archiving keeps a channel's history searchable and lets it be restored; deletion permanently removes messages and should be rare. A public channel can be converted to private, and converting a private channel to public is restricted because it would expose earlier messages. Posting permissions can limit announcement channels to specific people. Naming prefixes such as proj- or help- make channels easier to find and govern.
- How it shows up
- A workspace has dozens of stale or duplicate channels, and you choose between archiving, renaming, merging conversation or deleting.
- Common confusion
- Deleting inactive channels to tidy up, which destroys history that archiving would keep.
3.2 Assess the given scenario to determine which permission is required for management of cross-workspace channels.Who can share channels across workspaces.
- What it means
- On Enterprise Grid, a multi-workspace channel is a single channel shared to more than one workspace, and an org-wide channel reaches every workspace. Managing these channels, including sharing them to new workspaces, takes org-level authority.
- What to understand
- Org Owners and Org Admins can create and manage multi-workspace and org-wide channels, and the Channels Admin system role can grant this power without full org admin rights. Workspace Admins act within their own workspaces and cannot by themselves share a channel to a workspace they do not administer. Moving a channel to another workspace also requires admin roles on both sides.
- How it shows up
- A workspace admin tries to share a channel to another workspace and fails, and you identify the role that is needed.
- Common confusion
- Assuming a Workspace Admin can share channels to any workspace in the org.
3.3 Given a scenario, determine which setting needs to be adjusted to allow for all members in a workspace to access a feature.Finding the setting and the level it sits at.
- What it means
- Many features, such as creating channels, using huddles, installing apps, using Workflow Builder, using AI features or sending Slack Connect invitations, can be allowed for everyone or limited to certain roles. On Enterprise Grid, an org-level policy can lock the choice for every workspace.
- What to understand
- When some members can use a feature and others cannot, check who the permission is limited to, then check whether an org policy overrides the workspace setting. The correct answer changes the setting at the level where it is enforced, and only as broadly as the scenario requires. Plan availability matters too: no setting will enable a feature the plan does not include.
- How it shows up
- Members cannot start huddles or create channels, and you identify the permission or org policy to change.
- Common confusion
- Changing the workspace setting when an org-level policy is locking it.
3.4 Given a scenario, determine how to manage a user account's access to multiple workspaces.One account across several Enterprise Grid workspaces.
- What it means
- On Enterprise Grid, each person has one account in the organization and can be a member of any number of its workspaces. Admins can add users to workspaces directly, through IdP groups, or by letting users join open workspaces, and can set a default workspace for new users.
- What to understand
- Workspace membership is a set of joins on one account, not separate accounts per workspace. Removing someone from one workspace leaves their other memberships intact, while deactivating at the org level removes all of them. Workspace visibility settings decide whether people can find and request to join a workspace. Consolidating many small workspaces is often recommended when teams constantly need cross-workspace access.
- How it shows up
- An employee transfers between business units and needs access to the new unit's workspace while keeping one shared workspace.
- Common confusion
- Creating a second account for the employee in the new workspace instead of adding the existing account.
3.5 Given a scenario, determine how to configure a Slack Connect channel.Shared channels with external organizations.
- What it means
- A Slack Connect channel is shared between your organization and one or more external organizations. Each side keeps its own members, retention and policies. Admins decide who can send and accept invitations, whether invitations need admin approval, and which external organizations are allowed.
- What to understand
- Typical configuration steps are: confirm who may invite externals, send the invitation, have the external admin accept or approve, and set the channel as private or public on your side. Admins can restrict file uploads or set approved organization lists, and on Enterprise Grid can manage connections at the org level. Each organization's data retention applies to its own copy of messages.
- How it shows up
- A partner needs a shared channel but invitations require approval, and you lay out who approves and what can be restricted.
- Common confusion
- Expecting your retention policy to control what the partner organization keeps.
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
Archive vs delete
Archiving hides a channel from active use but keeps history; deleting removes it permanently.
- Remember
- Archived channels can be restored and remain searchable.
- Tested as
- Channel cleanup scenarios.
- Trap
- Deleting channels to reduce clutter.
-
Private to public conversion
Changing a channel's visibility.
- Remember
- Making a private channel public exposes its past messages, so it is tightly restricted.
- Tested as
- Privacy-change scenarios.
- Trap
- Assuming conversion works the same in both directions.
-
Multi-workspace channel
One channel shared across several Enterprise Grid workspaces.
- Remember
- One history, many workspaces.
- Tested as
- Cross-business-unit collaboration.
- Trap
- Creating duplicate channels in each workspace.
-
Org-wide channel
A channel that every member of every workspace in the org belongs to.
- Remember
- Used for company-wide announcements.
- Tested as
- Announcements that must reach everyone.
- Trap
- Using a default channel in one workspace only.
-
Channels Admin role
A system role for managing channels across the org without full org admin rights.
- Remember
- Least-privilege choice for channel governance.
- Tested as
- Permission questions on cross-workspace channels.
- Trap
- Granting Org Admin instead.
-
Posting permissions
Limits on who can post in a channel, such as admins only.
- Remember
- Ideal for announcement channels.
- Tested as
- Requests to reduce noise in key channels.
- Trap
- Making the channel private instead.
-
Org-level policy
An Enterprise Grid setting that applies to and can lock every workspace.
- Remember
- Org policies override workspace settings.
- Tested as
- Features unavailable despite workspace settings.
- Trap
- Editing the workspace setting repeatedly.
-
Workspace consolidation
Merging several workspaces or moving channels to reduce fragmentation.
- Remember
- Moved channels keep messages but apps must be reinstalled.
- Tested as
- Sprawl and duplicate-workspace scenarios.
- Trap
- Expecting apps and analytics to move unchanged.
-
Slack Connect approvals
Admin settings that require approval before external connections are made.
- Remember
- Both organizations can require their own approval.
- Tested as
- Partner channel setup questions.
- Trap
- Assuming one side's approval is enough.
-
Channel prefixes
Agreed name prefixes that group channels by purpose.
- Remember
- They support findability and governance at scale.
- Tested as
- Naming convention scenarios.
- Trap
- Treating names as cosmetic.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
Channel lifecycle actions
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Archive | Stops activity, keeps history | Reversible and searchable | Choosing delete instead |
| Delete | Removes channel and messages | Permanent | Using it for routine cleanup |
| Convert to private | Limits visibility going forward | Allowed for public channels | Assuming the reverse is equally easy |
| Move to another workspace | Relocates a channel on Enterprise Grid | Needs admin rights on both workspaces; apps reinstall | Moving when both teams still need access |
Reaching people beyond one workspace
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Multi-workspace channel | Shared across chosen workspaces in your org | Internal, one history | Duplicating channels instead |
| Org-wide channel | Includes everyone in the org | Company-wide reach | Using it for team-level topics |
| Slack Connect channel | Shared with external organizations | Each org keeps its own members and policies | Treating partners as internal members |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Delete to declutter
- What candidates pick
- Delete every channel with no messages in six months.
- Why it looks right
- It looks like the cleanest outcome.
- Why it's wrong
- Deletion permanently removes history that may be needed later; archiving achieves the cleanup while keeping messages searchable and restorable.
Clue to watch for The scenario mentions cleanup or channel sprawl without any legal requirement to remove data.
-
Workspace setting first
- What candidates pick
- Turn on the feature in the workspace settings.
- Why it looks right
- That is where most admins look first.
- Why it's wrong
- If the organization has an org-level policy locking the feature, the workspace setting cannot override it.
Clue to watch for The workspace setting appears enabled but members still cannot use the feature.
-
Duplicate channels
- What candidates pick
- Create matching channels in both workspaces.
- Why it looks right
- Each team gets a channel immediately.
- Why it's wrong
- Conversation and files split in two; a multi-workspace channel keeps one shared history.
Clue to watch for Two business units need the same conversation.
-
Move the channel
- What candidates pick
- Move the channel to the other workspace.
- Why it looks right
- Moving is a familiar consolidation tool.
- Why it's wrong
- Moving removes access for members not in the destination workspace and does not share it with both.
Clue to watch for Both workspaces must keep access.
-
Our retention covers partners
- What candidates pick
- Rely on your retention policy to delete shared Slack Connect messages everywhere.
- Why it looks right
- You own the channel, so your policy seems to apply.
- Why it's wrong
- Each organization applies its own retention to its own copy of a Slack Connect channel.
Clue to watch for A compliance requirement mentions an external organization's copy of messages.
Answer framework
For channel, workspace and Slack Connect scenarios, apply these steps in order.
- Identify the object in question: a single channel, a channel spanning workspaces, a whole workspace, a user's memberships, or an external connection.
- Choose the action that preserves history and access, preferring archive over delete and sharing over duplicating or moving; archived channels stay searchable and can be restored later.
- Determine the level where the control lives, checking org-level policies before workspace settings on Enterprise Grid.
- Name the least-privileged role that can perform the action, such as Channels Admin or Channel Manager before Org Admin.
- For external work, confirm invitation permissions, approval requirements on both sides, and any file or retention restrictions before choosing, since both organizations must approve a Slack Connect channel.
Practice question
Want more like this? The Slack-Admn-201 practice test has questions for every domain.
Checklist
0 of 11
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
Start with the channel lifecycle, because the first objective is broad and appears in many forms. In a trial workspace, create, rename, convert, archive and restore channels, and set posting permissions on one of them, noting which actions are reversible. Then read Slack's help articles on channel management tools, converting channels and moving channels between workspaces in an Enterprise organization.
For Enterprise Grid, sketch an org with three workspaces and mark which roles act where. Add a multi-workspace channel, an org-wide channel and a locked org policy to the sketch. The Slack Workspace Design and Workspace Consolidation modules on Trailhead cover the reasoning behind these structures.
Slack Connect deserves a focused session: walk through an invitation from both sides, including who can send it, who approves it, and what each organization controls afterwards. Highest-value areas are archive versus delete, org policy overrides and cross-workspace permissions. The most underestimated area is the effect of moving a channel, especially reinstalling apps and checking destination membership first.
FAQ
What share of the Slack Admin exam is Workspace and Org Management?
Workspace and Org Management is 17% of the exam, around ten of the 60 scored questions as a planning estimate.
Do I need Enterprise Grid experience?
It helps a lot. Three of the five objectives involve multi-workspace concepts, so study org-level roles, policies and channels even if you administer a single workspace.
Can a deleted channel be recovered?
Deleting a channel permanently removes it and its messages. Archived channels can be restored, which is why archiving is the usual answer for cleanup.
What moves with a channel when it changes workspaces?
Messages, threads, files, pins, topic and retention settings move. Apps and custom bots must be reinstalled, analytics reset, and members missing from the destination lose access.
Who controls a Slack Connect channel?
Each organization controls its own side, including its members, approval rules and retention. Neither side can manage the other's users.
Does this section cover workspace creation and design?
Not as a separate objective, but channel management, multi-workspace access and Enterprise Grid structure draw on workspace design and consolidation, which the official trail covers.
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 3 knowledge
You have covered channel management, cross-workspace permissions, org-level settings, multi-workspace access and Slack Connect setup. Try these decisions under time pressure.
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