What Automations do, when they earn their cost, and where to go for the build mechanics.
Automations make assignments fire automatically based on triggers — a learner gets added to a group, completes a piece of content, joins a department, hits a date, or meets any combination of conditions you define. Once an Automation is active, you don't think about it again until you change the program; new learners enter the program automatically as they meet the criteria.
This is the right tool whenever the audience is dynamic and the program needs to repeat at scale. It's the wrong tool when you're running a single cohort with explicit membership — use a Direct Assignment for that instead.
For the strategic frame on when to build an Automation vs a Direct Assignment, see Designing Assignments: Direct vs. Automated. For deeper design patterns and anti-patterns, see Automation Design Best Practices.
When Automations Are Worth Building
Onboarding tied to a start date or hire event. New hires shouldn't depend on someone remembering to assign them training. An Automation triggered by Group membership or department fires the right learning the moment a user lands in the right cohort.
Recurring certification cycles. Annual compliance, quarterly recerts, role-based recurring training. The Automation re-fires on schedule without admin touch.
Progressive learning paths. Track A completion triggers Track B assignment. This is how you chain Tracks together (since Tracks can't be nested directly).
Attribute-driven enrollment. "Anyone in Sales in North America should get the regional sales kit" — an Automation tied to Smart Segmentation membership keeps assignments accurate as people move roles.
When to Use a Direct Assignment Instead
If you find yourself defining an Automation for a one-off cohort, you're using the wrong tool. Direct Assignments exist for explicit, named groups where you want to control exactly who's in. See Creating a Direct Assignment.
Reach for an Automation when the audience is dynamic; reach for a Direct Assignment when the audience is curated.
The Automation Lifecycle
Each Automation moves through a small set of operations. Each has its own detailed article:
Create. Define the trigger, audience criteria, content to assign, notifications, and due date. See Creating an Automation.
Activate. Until an Automation is activated, it doesn't fire — even if the trigger conditions are met. See Activate an Automation.
Duplicate. Start a new Automation from an existing one when the criteria are similar. See Duplicate an Automation.
Deactivate. Stop an Automation from firing without deleting it — useful for seasonal programs and Automations that pause between cycles. See Deactivate an Automation.
Delete. Permanently remove an Automation when it's no longer needed. Existing assignments already triggered by the Automation are preserved. See Delete Automations.
Configuration Pitfalls
Creating an Automation but Forgetting to Activate It. A created Automation is dormant. Trigger conditions can be met all day and nothing happens. Activate it the moment you're ready for it to fire, not when you remember.
Audience Criteria That Match Everyone. An Automation with overly broad criteria (e.g., "all users") effectively assigns to the entire org on a recurring basis. Before activating, test with a narrow Smart Segment or a small audience to confirm the criteria fire only on the intended population.
Stacking Multiple Automations Without Coordination. When several Automations can fire for the same learner, the result is a wall of notifications and assignment overlap. Build a map of which Automations target which audiences before adding new ones to a heavily-automated org.
Using Automations for One-Off Cohorts. If the audience won't change, the Automation is harder to maintain than a Direct Assignment. The "set it once" benefit only pays off when membership is genuinely dynamic.
Not Testing the Trigger Before Going Live. Automations that fire on attributes (department, location, role) depend on those attributes being set correctly on user profiles. If profile data is inconsistent, the Automation misses learners who should have been included. Verify with sample profiles before activation.
Where This Fits
You're here because you want to understand or build an Automation. The strategic decision — whether Automation or Direct Assignment is the right tool — lives in Designing Assignments: Direct vs. Automated. The deeper design patterns live in Automation Design Best Practices. The trigger types and conditions reference lives in Automation Audience Trigger Guide.
See Also
- Automation Design Best Practices — the strategic anchor.
- Designing Assignments: Direct vs. Automated — when each tool fits.
- Creating an Automation — the full creation flow.
- Automation Audience Trigger Guide — every trigger and what it fires on.
- Creating a Direct Assignment — the other side of the assignment decision.
- Groups Automations — Automations triggered by Group membership specifically.
Automations are for dynamic audiences and repeating programs. Direct Assignments are for explicit cohorts. Activate before testing — a created Automation that's never activated doesn't fire.