How to Manage Learners in Bulk Across Panoramas

Bulk actions save admins from repeating the single-learner move one at a time when a whole cohort needs to change Panoramas or sublicenses at once, such as during a reorganization, a contract renewal, or a large onboarding push.

Who can do this: bulk actions require the Editing Basic Learner Info permission. Which actions are available depends on where you start (the main site or a Panorama learner list) and whether you're a platform admin or a Panorama-scoped admin.

These four actions cover everything you can do to a group of learners' Panorama and sublicense access without opening individual profiles: moving them into a Panorama, removing them from one, or adjusting the sublicenses they hold within one. Which ones you see depends on your permissions.

• Bulk Panorama Change: move the selected learners to a different Panorama. This includes adding a Panorama, meaning moving main site learners into a Panorama for the first time.
• Bulk Panorama Remove: remove the selected learners from their Panorama, moving them back to the main site.
• Bulk Sublicense Add: grant additional sublicenses to the selected learners within their Panorama.
• Bulk Sublicense Remove: remove sublicenses from the selected learners within their Panorama.

Because a bulk action affects every learner in the batch at once, it's worth understanding these limits and defaults before you confirm one. There's no per-learner override once it's running.

• A batch can contain up to 750 learners. The UI blocks larger selections before they reach the migration endpoint, matching the backend batch limit.
• The enrollment decision you choose applies to every learner in the batch; bulk operations don't support per-learner decisions.
• If you choose to reset progress, that change can't be undone.

This is the bulk version of the single-learner move: you choose a destination, preview how each learner's access will change, and make one enrollment decision that applies to the whole batch. Follow these steps to move a group of learners to a different Panorama, or to add them to a Panorama for the first time.

1. Go to the learner list (main site or Panorama).
2. Select the learners you want to move using the checkboxes.
3. Open the bulk actions menu and choose Bulk Panorama Change.

To remove learners from a Panorama entirely and move them back to the main site, use Bulk Panorama Remove instead.

Choose the Destination

Select the destination Panorama and/or the sublicenses the learners should have.

Preview the Impact and Choose an Enrollment Decision

The wizard shows how each content item will be affected, grouped by:

• In both Panoramas (overlap content): content available through both the old and new sublicenses. There's no change in access, so enrollments and progress are preserved automatically.
• Only in the current Panorama: the content the learners are leaving behind. This is what your enrollment decision applies to.
• Only in the future Panorama: newly available through the destination sublicenses. No decision is required here, it's informative only.

When there is content the learners are leaving behind, choose one enrollment decision (see the enrollment decision options in Managing Panorama and Sublicense Access for an Individual Learner). If nothing is being left behind, the wizard shows "no decision needed" and skips straight to confirmation.

Review and Confirm

A summary shows the final outcome. Select Confirm to queue the move as a background job.

Use this when learners are staying in their current Panorama but need different sublicense access (for example, granting a newly available sublicense to a cohort, or removing access for a group whose contract has ended). Follow these steps to add or remove sublicenses for a group of learners within the same Panorama.

1. From the Panorama learner list, select the learners.
2. Open the bulk actions menu and choose Bulk Sublicense Add or Bulk Sublicense Remove.

Choose the Sublicenses

Select the sublicenses to add or remove for the selected learners, within the same Panorama.

Preview the Impact and Choose an Enrollment Decision

For removals, preview any content that will no longer be reachable and choose one enrollment decision, using the same options as a single-learner move.

Confirm

Select Confirm to queue the job.

Bulk jobs process asynchronously so you're not stuck waiting on a spinner. You can keep working elsewhere in the admin area while a large batch runs. Here's what to expect while one is processing and after it completes.

• Confirming the move queues it as a background job and returns you to the admin area right away. You don't need to keep the page open while it runs.
• A notification appears in the notification bell after you confirm, titled Bulk Panorama assignment or Bulk Sublicense assignment depending on the action, and updates as learners are processed.
• When the job finishes, the notification's status updates to Completed: {succeeded}/{total} if at least one learner succeeded, with a Download errors link if any failed, or Failed: {N} errors out of {N} if every learner in the batch failed.

• A failure for one learner doesn't block the rest of the batch. Only the affected learners are reported as failures. For example, a rare progress-reset side effect might be reported against one learner while everyone else in the batch completes normally.
• The notification stays available afterward from Users > Notifications, so you can review past bulk job results at any time, not just in the moment.

Successfully changed learners are recorded in the Management Actions Log.