Assignments allocate single or multiple selections of learning content to learners. They are the learning content that managers decide a learner must complete in order to best perform at their occupation. Learners receive assignments directly from their manager. They can also receive assignments automatically because of their selected tags or the learner group they are in.
Note: Self-assigned content is the courses and learning paths learners assign to themselves and is not seen as an assignment.
An assignment created by a manager consists of:
Details: what learners need to know about the assignment
- Assignment name
- Assignment type
- Assignment objective
Audience: who should receive the assignment
- A specific learner or learners
- A learner group or groups
- Can include a tag or tags
- Users with a specific tag or tags
Content: what training should the audience receive
- A course or courses
- A learning path or paths
Settings: optional automation and deadlines
- Auto-assign to new users
- Don't auto-assign to new users
- Deadline options:
- A specific date
- A timespan from the date the assignment is received
- No deadline
We recently refactored our assignment functionality and all existing assignments in a workspace were migrated so that they are supported in the new functionality.
How do I know when an assignment is a legacy assignment?
All legacy assignments will have a type of "Training" and won't have an objective.
Example of a legacy assignment
Legacy assignments can be edited to add a different type and objective.
How does the naming of legacy assignments work?
- All legacy assignments to an individual/s will show the first product in the assignment as the assignment name.
- All legacy assignments to a group/s and/or tag/s will show the existing name of the assignment.
In both cases, the legacy assignment can be edited to change the name.