Grid Design15% of the exam
Grid best practices: primary workspace, avoiding sprawl
The grid design best practices a consultant teaches before showing options: an 80% primary workspace, the fewest workspaces that work, channels and multi-workspace channels before new workspaces, one org-wide announcements channel, clear workspace names and icons, social and external workspaces, and an agreed admin cascade.
Understand grid design best practices.
~8 min read · 13 practice questions ·
What the exam expects
- Recite the five grid design best practices and apply the 80% primary-workspace benchmark with two or three workspaces per member.
- Recommend the minimum number of workspaces, and explain the drawbacks of workspace sprawl.
- Choose between a channel, a multi-workspace channel, temporary membership in a second workspace and a new workspace.
- Replace duplicate announcement channels with one org-wide default channel, and fix workspace confusion with naming guidelines and icons.
- Explain what social and external workspaces add, why shared-channel apps go on every workspace that shares the channel, and why the admin cascade is agreed up front.
Key terms:
- Primary (home) workspace: the workspace where a member spends 80% or more of their time.
- Workspace sprawl: workspaces created as substitutes for channels rather than out of necessity.
- Multi-workspace channel: a channel shared with several workspaces in an Enterprise organization (Enterprise Grid or Enterprise+ plan).
- Org-wide channel: a multi-workspace channel accessible from every workspace in the org.
Key facts
Primary workspace target
- Detail
- 80% or more of a member's time
Workspaces per member
- Detail
- Two or three on average, at most
Number of workspaces
- Detail
- The minimum that meets users' needs; adding is easier than consolidating
Collaboration inside one workspace
- Detail
- Use a channel in that workspace
A few people need deeper access
- Detail
- Add them to the other workspace as long as needed, then review and remove
Company-wide announcements
- Detail
- One org-wide channel, made default for all members
Every workspace needs
- Detail
- A name, URL and icon; distinctive icons aid navigation
Core workspaces
- Detail
- Open; restrict only workspaces with specific needs
Apps and bots in shared channels
- Detail
- Install on all workspaces that share the channel
Sources for this section (4)
- Compare Grid Design Modelstrailhead.salesforce.com (opens in a new tab)
- Design Workspaces on Enterprise Gridtrailhead.salesforce.com (opens in a new tab)
- Consider Alternatives for Workspace Designtrailhead.salesforce.com (opens in a new tab)
- Manage a workspace in an Enterprise organizationslack.com (opens in a new tab)
- What benchmark tests whether a design causes too much context switching?
- Why start with the fewest workspaces?
- When should a few people be added to a second workspace instead of creating a new one?
- Why does an org-wide default channel beat an #announcements channel per workspace?
- What does a social workspace do for business workspaces?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Slack Consultant pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 38 lessons of the Slack Consultant guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Inline practice questions and one-click topic practice (13 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams