How to Manage Learners in Bulk Across Panoramas

You can move multiple learners between Panoramas, or add and remove sublicenses for a group of learners, in a single action from the learner list. The bulk workflow mirrors the single-learner wizard: you pick the destination Panorama and sublicenses, preview the impact, and choose one enrollment decision that's applied uniformly to every learner in the batch.


Bulk operations run in the background, so you can navigate away while a large batch processes. When the job finishes, you'll receive a notification summarizing how many moves succeeded, failed, or were skipped.

Managing Learners in Bulk Across Panoramas is behind a feature flag.

Contact your Account Team or Support to have this feature enabled.

Use Case Information

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.

Where you start Who Available bulk actions
Main site learner list Platform admin Bulk Panorama Change, Bulk Panorama Remove
Panorama learner list Platform admin Bulk Panorama Change, Bulk Panorama Remove, Bulk Sublicense Add, Bulk Sublicense Remove
Panorama learner list Panorama-scoped admin Bulk Sublicense Add, Bulk Sublicense Remove only

The Four Bulk Actions

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.

A Few Things to Keep in Mind

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.

Note

Achievements, certificates, and transcript records are always preserved, even when Remove access and reset progress is selected.

Bulk Move Learners to Another Panorama

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.

Follow the steps in the wizard:

Choose the DestinationPreview the Impact and Choose an Enrollment DecisionReview and Confirm

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

cpa-1-destination.png

cpa-1b-subl-filled.png

 

Tip

Golden rule for a clean migration: if the preview flags courses that exist only in some learners' current Panorama and you want them carried over as normal Panorama access, pause the move, provision that content into the destination Panorama or sublicense, then re-run the move. Once the content exists in both places, it shows as overlap and is preserved automatically, so no enrollment decision is needed and no progress is at risk for those learners. See Managing Panorama and Sublicense Access for an Individual Learner for the single-learner version of this tip.

Bulk Change Sublicenses

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.

Follow the steps in the wizard:

Choose the SublicensesPreview the Impact and Choose an Enrollment DecisionConfirm

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

Background Processing & Notifications

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.

Note

Bulk jobs started through the REST API surface the same progress and completion notifications as bulk jobs started from the admin UI.

  • 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.

w13-bulk-notifications.png

  • 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.

Tip

If any learners failed, download the CSV from the completion notification before dismissing it: each row includes the learner's user ID, email, first name, and last name, plus the reason it failed (for example, "No license changes to apply"). Failed learners are not written to the Management Actions Log, so this CSV is your only record of who still needs attention.

 

Note

The learner list doesn't refresh automatically when a job finishes. If you're viewing a list affected by the move, refresh the page to see the updated Panorama and sublicense assignments.

Successfully changed learners are recorded in the Management Actions Log.

FAQs

What happens if I close the browser tab while a bulk job is running?

Nothing. Bulk jobs run in the background on the server, so closing the tab or navigating away doesn't interrupt the job. You'll still get a notification when it finishes.

Can I select more than 750 learners for a single bulk action?

No. The UI blocks selections larger than 750 learners because that's the backend batch limit. Split larger cohorts into multiple batches instead.

Can I apply a different enrollment decision to different learners in the same batch?

No, bulk operations apply a single enrollment decision to every learner in the batch. If different learners need different decisions, run separate bulk actions for each group.

Will achievements, certificates, or transcripts be lost if I reset progress during a bulk move?

No. Achievements, certificates, and transcript records are always preserved, even when Remove access and reset progress is selected.

How do I find out which learners failed in a bulk job?

Open the completion notification from the notification bell (or from Users > Notifications) and download the errors CSV, which lists each failed learner's user ID, email, name, and failure reason.

Was this article helpful?
0 out of 1 found this helpful

More resources

  • Academy

    Go from beginner to expert with hands-on training

  • Community

    Ask questions, swap ideas, and learn from people like you

  • Developer Docs

    Reference guides and code samples for developers