How to send the same content to a new audience without creating a new Assignment from scratch — using Assignment Instances.


An Assignment Instance is a single delivery of an Assignment. If you assign the same content to three different teams at three different times, you create three Instances of one Assignment. Instances let you track each delivery separately while keeping them grouped under one Assignment for easier management.

For the conceptual foundation, see Understanding Assignment Instances.


When to Create a New Instance

Create a new Instance when:

  • The same content is going to a different audience (new team, new region, new cohort)
  • The same content is being re-sent on a different cadence (Q1 vs Q2 rollout)
  • You want separate due dates, notifications, or naming for the same content delivery
  • You want separate reporting on each delivery

Don't create a new Instance when you're delivering completely different content — start a new Assignment instead.


How to Create a New Instance

1. Open the existing Assignment. Share → Assignments → find and click the Assignment.

2. Click + New Instance on the Assignment's detail page.

3. Name the Instance. Use a name that identifies the audience and timing. Example: "EMEA Sales Cohort — Q2 2026" rather than just "Sales Training."

4. Select the audience. Same options as the main Assignment — individual users, Groups, Teams, Departments, Smart Segmentation rules.

5. Apply exclusionary logic if needed.

6. Set the due date for this Instance specifically.

7. Configure notifications.

8. Review and activate.

The Instance is delivered to its audience immediately. The parent Assignment's reports now include this Instance alongside any others.


What's Shared Across Instances

Content. All Instances of an Assignment deliver the same content. Updating the content updates it for all Instances.

Assignment-level reports. The parent Assignment's report rolls up data from all Instances.

What's unique to each Instance:

  • Name
  • Audience
  • Due date
  • Notification configuration
  • Per-Instance reports

Common Mistakes

Creating a new Assignment when an Instance would do. If you're delivering the same content to a new audience, a new Instance keeps reporting cleaner than a separate Assignment. Assignment-level rollups won't capture both unless you use Instances.

Naming Instances generically. "Instance 2" and "Instance 3" make Bulk Editing and reports painful. Always name Instances by their audience and timing.


See Also


Open the Assignment → +New Instance → name, audience, due date, notifications → activate. Use Instances for same content to different audiences or different timings.

Was this article helpful?
0 out of 0 found this helpful