Naming each Assignment Instance with a clear, custom label — so reports, tracking, and Bulk Editing remain navigable as your assignment library grows.
By default, an Assignment Instance inherits the name of the content being assigned (e.g., "Security Training – Q2"). When the same content is sent to multiple audiences or via multiple Automations, default names produce duplicates. Naming the Instance explicitly avoids this — each delivery gets a label that distinguishes it from every other delivery of the same content.
Why Naming Matters
Reporting clarity. When you filter reports by Assignment, named Instances are immediately identifiable. "Security Training – Q2" appearing five times tells you nothing; "Security Training – EMEA Sales – Q2 2026" tells you which delivery you're looking at.
Bulk Editing precision. When you Bulk Edit, you select an Instance to edit. Named Instances make the right one easier to find.
Manager and learner visibility. Some manager-facing reports show the Instance name. A clear label helps managers understand what their team is being assigned.
Audit trail. Six months from now, when someone asks "who took this training and when," named Instances let you answer the question without spelunking through metadata.
How to Name an Instance
1. When creating a new Instance (or Assignment), enter the name in the Name field rather than leaving the default.
2. To rename an existing Instance: Open the Instance and edit the Name field. Save.
What Makes a Good Instance Name
Include enough detail that the name stands alone:
- Audience (EMEA Sales, New Hires, Tier 1 Partners)
- Timing or cohort (Q2 2026, January 2026, FY26)
- Program context (Onboarding, Annual Recert, Launch Training) if not obvious from content
Examples of good names:
- "Security Awareness Annual Recert — EMEA — Q2 2026"
- "New Hire Onboarding — Sales — January 2026 Cohort"
- "Partner Certification — Tier 2 Resellers — H1 2026"
Examples of names to avoid:
- "Security Training" (which Instance?)
- "Assignment 2" (no context)
- "Test" (and yet — this happens)
Naming Conventions for Teams
For organizations running many Assignments, a consistent naming pattern saves time long-term. A typical pattern: [Program] — [Audience] — [Period]. Document the convention somewhere your team will find it (typically a Continu admin doc or internal wiki).
See Also
- Understanding Assignment Instances — how Instances work.
- Creating a New Assignment Instance — naming during creation.
- Bulk Assignment Editing — where named Instances pay off in management.
Name every Instance with audience, timing, and program context. Default names produce duplicates; clear names produce navigable reports.