Grid Design15% of the exam
Centralized vs distributed grid models and workspace access
How to build and present feasible grid options: the centralized and distributed models with their benefits and considerations, when a separate workspace is justified, the global workspace, the four workspace access levels, example channels, and tying the recommendation to discovery objectives.
Design and articulate feasible grid design options for your client.
~8 min read · 12 practice questions ·
What the exam expects
- Choose between a centralized and a distributed design from the client's needs, and state each model's benefits and considerations.
- Recognize when one team's different retention, file upload, app approval or admin needs justify a separate workspace.
- Identify the global workspace and use it for org-wide channels and, without an external workspace, Slack Connect channels.
- Pick Open, By Request, Invite Only or Hidden for each workspace, and route By Request join requests to a channel.
- Present two or three options with example channels, benefits, considerations and a recommendation tied to discovery objectives.
Key terms:
- Centralized design: one workspace for all employees in an Enterprise organization (Enterprise Grid or Enterprise+ plan).
- Distributed design: two or more workspaces, each based on different policies, privacy requirements or team segmentation, connected by multi-workspace channels.
- Global workspace: a workspace every employee is added to by default, for channels not specific to one business unit.
- Workspace access: how org members find and join a workspace (Open, By Request, Invite Only, Hidden).
Key facts
Base models
- Detail
- Centralized (one workspace) and distributed (two or more)
Centralized key limit
- Detail
- No granular workspace control over retention, guests or channel management
Centralized success factor
- Detail
- Process-building and training up front
Centralized variation
- Detail
- One unit with different policies gets its own workspace and designated admin
Global workspace
- Detail
- All employees added by default; hosts Slack Connect if no external workspace
Invite Only
- Detail
- Visible to all; members must be invited or added
Hidden
- Detail
- Not visible; invited by Workspace Owner or Admin, or added by Org Owner or Admin
By Request approvals
- Detail
- Requests go to a chosen channel; anyone in it can approve
Visualizing options
- Detail
- Fill in example channels on each option
- When does a centralized design get a second workspace?
- Why does a centralized design need process-building and training up front?
- Which access level keeps a merger workspace out of view for non-members?
- Why fill in example channels on each grid option?
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 (12 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams