Governance Structure (Owner and Admin Roles)8% of the exam
Admin request workflows: guests, workspaces and apps
Which admin processes to move into Slack request workflows and what each form collects: Slack Connect channels, guests, multi-workspace channels, channel changes made with org channel management tools, ongoing new-hire onboarding, app requests and preapproved org-wide apps, and new workspace requests, including a custom app on the admin APIs.
Based on a client scenario, identify and advise on critical admin processes and workflows that can be migrated to Slack.
~8 min read · 8 practice questions ·
What the exam expects
- Given a client scenario, pick the admin process to move into Slack and the details its request form must collect.
- Default contractor requests to the right guest type and tell guests apart from Slack Connect.
- Route multi-workspace channel requests to Org Admins and complete channel changes with org-level channel management tools.
- Replace one-off new-hire training with an onboarding workflow, and cut app requests by preapproving org-wide apps.
- Decide whether a new workspace is justified, and automate ticket-driven workspace creation with the admin APIs.
- Key terms: single-channel guest (free guest limited to one channel); multi-workspace channel (one channel added to several workspaces in an Enterprise org); channel management tools (central dashboard for acting on channels without joining them); preapproved app (an app approved in advance so members install it without a request); admin APIs (Enterprise-only APIs an app uses to create workspaces and manage members).
Key facts
Slack Connect default
- Detail
- Shared channels need Org Admin/Org Owner approval
Slack Connect form extras
- Detail
- External org's Slack domain URL; name and email of its admin
Guest billing
- Detail
- Single-channel guests free; multi-channel guests billed as members
Single-channel guest limit
- Detail
- Up to 5 per paid active member
Multi-workspace channel requests
- Detail
- Org Admins manage them in #plz-admins; most useful at 4+ workspaces
Channel management tools by default
- Detail
- Org Primary Owner only; others via permission (Channels Admin is the matching system role)
New-hire onboarding
- Detail
- Workflow in default channels messages new users
Org-wide apps
- Detail
- Preapprove at org level; Default for future workspaces option
Workspace creation API
- Detail
admin.teams.create, Enterprise plans only
Sources for this section (7)
- Efficiently Manage Admin Requeststrailhead.salesforce.com (opens in a new tab)
- Understand guest rolesslack.com (opens in a new tab)
- Types of roles in Slackslack.com (opens in a new tab)
- Use channel management toolsslack.com (opens in a new tab)
- Effective Management of Apps and User Onboardingtrailhead.salesforce.com (opens in a new tab)
- Manage apps in an Enterprise organizationslack.com (opens in a new tab)
- admin.teams.createdocs.slack.dev (opens in a new tab)
- Why default a one-channel contractor to a single-channel guest?
- When does a multi-workspace channel request process pay off most?
- When the client hires every month, how should Slack onboarding reach new people?
- Which API method creates a workspace in an Enterprise org?
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 (8 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams