App and AI Administration and Automations20% of the exam
App request automation rules and scope ratings
How to rate scopes as low, medium or high risk and build automation rules that approve, restrict, cancel or send app requests for review: the rule components, the difference between scopes requested and scopes resolved, why rule order and activation matter, and what each resolution does.
Assess a given scenario to determine how to manage app installation and approvals.
~7 min read · 7 practice questions ·
What the exam expects
- Rate scopes as low, medium or high risk and use the rating lists in an automation rule.
- Pick the rule component that matches a requirement: scopes requested, scopes resolved, previous resolution, app distribution or app IDs.
- Choose between "includes any of those in" and "includes only those in" when a rule must catch one risky scope or allow only safe ones.
- Explain why a rule did not fire (not activated, or an earlier rule matched first) and fix it.
- Predict what Restrict, Approve, Cancel and Review do to a request and to future requests.
Key terms:
- Automation rule: an "If any or all component + condition + comparison, then resolution" statement applied to incoming app requests.
- Scope rating: your own low, medium or high risk label on a scope, which fills the rating lists rules compare against.
- Scopes requested: all the scopes in the app being requested now.
- Scopes resolved: the scopes of an app that was previously requested and approved.
- Resolution: the outcome a matching rule applies: Restrict, Approve, Cancel or Review.
Key facts
Plans
- Detail
- Automation rules and scope ratings on all plans
Scope ratings
- Detail
- High, medium or low risk, set by you; unrated scopes form the Unrated list
New rule state
- Detail
- Not enabled until activated
Multiple rules
- Detail
- Resolved at the first matching rule; order matters
Removing a rule
- Detail
- Earlier resolutions stay; cannot be undone
Scopes resolved
- Detail
- Scopes of a previously requested and approved app
Restrict
- Detail
- No reinstall or re-request unless scopes change
Cancel
- Detail
- Dismissed; can be requested again anytime
Sources for this section (2)
- Why must scopes be rated before a scope-based rule can work?
- When should a rule use scopes resolved instead of scopes requested?
- Why can a broad approval rule defeat a restrictive rule below it?
- What is the difference between Restrict and Cancel for the requester?
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