How to update due dates, remove users, send reminders, and take other actions across many assignment records at once.
Bulk Assignment Editing operates on user-assignment records within a single Assignment Instance. Use it when you need to change something for many users at once — extending a due date for a delayed cohort, removing users who left the company, sending reminders to everyone who hasn't started.
What You Can Do With Bulk Editing
Within a single Assignment Instance, you can:
- Remove users who no longer need to complete the assignment
- Update due dates for selected users or all users in the Instance
- Send reminders to users who haven't started or completed
- Mark as complete for users who completed outside Continu (rare; use sparingly to preserve data integrity)
- Reset progress for users who need to start over
How to Run a Bulk Edit
1. Open the Assignment. Share → Assignments → click the Assignment.
2. Open the Instance you want to edit. If the Assignment has multiple Instances, choose the right one.
3. Filter the user list. Filter by status (Not Started, In Progress, Overdue, Completed), by department, by team, or by any combination.
4. Select users. Either select individual users via checkboxes or use Select All to apply to the entire filtered list.
5. Choose the bulk action. The action menu shows the available operations for your selection.
6. Confirm the action. Bulk operations can affect many records — review the count and the action before confirming.
Common Bulk Edit Scenarios
Extending due dates for a delayed cohort. Filter the Instance by status "Overdue" or "Not Started," select all, choose Update Due Date.
Removing users who left the company. Filter by status or attribute, select the relevant users, choose Remove. (Better solution: rely on HRIS sync to auto-suspend them — see Provisioning and Sync.)
Reminder blast. Filter to "Not Started" status, select all, choose Send Reminder. Confirm whether the reminder will use email, Slack, or in-app — match the notification channel to where your audience reads.
Removing users who should never have been included. Audit the audience, identify the wrongly-included users, remove them. Then update the underlying audience configuration so they don't re-appear in future Instances.
What Bulk Editing Does Not Do
It doesn't edit across Instances. If you want to update due dates for the same content across three different cohort Instances, you have to do each Instance separately.
It doesn't change the Assignment's underlying configuration. Bulk Editing acts on individual user-assignment records, not on the Assignment definition itself. To change the audience definition for future deliveries, edit the Assignment configuration directly.
It doesn't undo automatically. Bulk operations apply immediately. Removing users, for example, can't be reverted in one click — you'd have to add them back manually.
Common Mistakes
Bulk-removing users to "clean up" a stale assignment. If the assignment is stale because the content is outdated, fix the content. If it's stale because the audience changed, fix the audience for future Instances. Bulk-remove is a workaround, not a fix.
Not previewing the affected count. Always check how many users a bulk action will affect before confirming. A wrong filter can affect many more (or fewer) records than expected.
Using Bulk Edit instead of Automation. If you find yourself running the same bulk edit every quarter, you probably want an Automation that handles the recurring case automatically.
See Also
- Creating a Direct Assignment — the source Assignment.
- Understanding Assignment Instances — Bulk Edit acts within an Instance.
- Assignment and Automation Notifications — for reminder configuration.
- Provisioning and Sync — for keeping audiences fresh automatically.
Open the Instance → filter → select users → choose bulk action → confirm. Acts on user-assignment records within one Instance. Doesn't change the Assignment configuration itself.