Named Assignments let you give each assignment instance a clear, custom label, so you (and your team) can easily identify it across reporting, tracking, and learner views.
🔍 Why Name Your Assignments?
By default, an assignment pulls the name of the content being assigned (e.g., “Security Training – Q2”). But when you send that content to multiple groups or use it in different workflows, it can be hard to tell them apart.
Naming your assignment instance helps you:
-
Clearly differentiate between use cases (e.g., “Q2 Security – Managers Only” vs. “Q2 Security – All Staff”)
-
Quickly spot which instance is which in your reports
-
Collaborate with other admins without confusion
-
Make bulk edits or removals easier by filtering assignments by name
📊 Where You'll See the Name
Assignment names now appear in:
-
Assignment Reports
-
User Progress Reports
-
The Instances tab for Direct Assignments
This makes it easier to filter, analyze, and communicate performance, especially when the same content is used across teams or learning initiatives.
✏️ Best Practices for Naming
-
Be specific and consistent (e.g.,
[Team] – [Topic] – [Quarter]
) -
Include context if it's tied to a project, region, or workflow
-
Use names that will make sense to your future self (or someone else on your team)
Related Articles
Assignments: Best Practice Guide