Enabling Slack Success (Analytics and Adoption)10% of the exam
Aligning workflows, apps and workspaces to business units
How to match Slack to each business unit: pick repeatable processes for Workflow Builder, know that branching needs the new Business+ or an Enterprise plan, feature workflows in channels, roll out apps core-first under an approval process, review workspace requests in an Enterprise org, and set department goals with metrics that fit them.
Given a scenario, align Slack features and workflows with business unit requirements.
~7 min read · 7 practice questions ·
What the exam expects
- Identify which business unit request is a good Workflow Builder candidate (sequential, repeatable, structured) and which needs an app, a migration or a security decision instead.
- Explain that workflow branches need the new Business+ or an Enterprise plan, and make a workflow easy to find by featuring it in a channel.
- Roll out apps department by department: approval process first, core productivity apps next, role-specific tools after that, custom apps last.
- Review a workspace request in an Enterprise organization (Enterprise Grid or Enterprise+ plan) by asking for purpose, scope, sponsor and Slack Connect plans, preferring multi-workspace channels.
- Set adoption goals per department and choose the metric that matches a business goal.
- Key terms: business process (a series of sequential, repeatable tasks completed to reach a goal); branch (a workflow step that sends people down different paths); featured workflow (a workflow pinned to a channel's menu bar); pre-approved apps list (apps members can install without a request); multi-workspace channel (one channel shared across workspaces in an org).
Key facts
Business process
- Detail
- Sequential, repeatable tasks completed to reach a goal
Required components
- Detail
- Trigger and steps; variables, buttons, managers optional
Branch plans
- Detail
- Business+ (new version) and Enterprise
Branch limits
- Detail
- Up to 15 branches; up to 5 nested beneath a primary branch
Featured workflow
- Detail
- Appears in the channel menu bar for one-click access
App rollout order
- Detail
- Governance, core productivity, role-specific, custom
Workspace sprawl
- Detail
- Prefer multi-workspace channels; new workspace only for real need
Approved request
- Detail
- Requester becomes workspace owner
Department goals
- Detail
- Based on current adoption rate and desired growth
Culture metric
- Detail
- Percentage of messages sent and read in public channels
Sources for this section (7)
- Identify Potential Workflowstrailhead.salesforce.com (opens in a new tab)
- Add a branch to a workflowslack.com (opens in a new tab)
- Manage Your Workflowstrailhead.salesforce.com (opens in a new tab)
- 5 steps to launch Slackslack.com (opens in a new tab)
- Workspace creation requeststrailhead.salesforce.com (opens in a new tab)
- 5 steps to support adoptionslack.com (opens in a new tab)
- Create a Vision for Slacktrailhead.salesforce.com (opens in a new tab)
- Why is a weekly status-update form a better first workflow than a one-time data import?
- When does the Add a branch option appear?
- What should an Org Admin ask before approving a workspace request?
- Which metric tracks a goal of a transparent, searchable culture?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Slack Administrator pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 32 lessons of the Slack Administrator guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Inline practice questions and one-click topic practice (7 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams