When going to edit and manage a Panorama Client, the first page a manager lands on is the Panorama Manager Dashboard. There are three fields that will show up on this dashboard for managers that will be explained in this article: Seats Occupied, Seats Allocated, and Seat Limit.
Definitions
Seats Occupied
- Will trigger when a learner has redeemed a registration code or redemption code.
- Will always increase by the number of sublicenses provisioned per code (so if it’s 1 sublicense - then it will increase by 1, if it’s 2 sublicenses then it will increase by 2 at the time of redemption).
- Will trigger when a learner is manually added to the panorama, either individually or via bulk import.
Path to view Seats Occupied: Panorama > Actions > Edit > Dashboard
Seats Allocated
- Will immediately trigger for 1 seat (regardless of how many sublicenses are attached) when a redemption code is created.
- Will not trigger for a registration code until that code has been redeemed by a learner.
- Will trigger when a learner is manually added to the panorama, either individually or via bulk import.
Path to view Seats Allocated: Panorama > Actions > Edit > Dashboard
Seat Limit
- The number limitation for seats occupied within a panorama.
- Seat Limits are set in the Primary Settings for the Panorama and are strictly enforced.
Path to set a Seat Limit: Panorama > Actions > Edit > Settings > Primary
Path to view the Seat Limit: Panorama > Actions > Edit > Dashboard
Tip
Best Practice: Provisioning learners directly to a panorama and/or bulk uploading learners to a panorama will change seat allocations and you will no longer be able to track by redemption codes/registration codes alone. If you want to be able to track how every learner is added, then we recommend only using Redemption or Registration codes for a given panorama. This will also provide the best reporting options on how and when learners joined.
Behaviors for Registration and Redemption Codes
Registration Codes:
When a registration code group with 30 codes is created and a single Panorama and sublicense is attached, no changes in allotment will be made to either the Seats Occupied or Seats Allocated within that panorama until a learner has redeemed the registration code. If a learner redeems the registration code for the single panorama and sublicense, then both Seats Occupied and Seats Allocated will increase by 1.
Example
When a registration code provisions more than one sublicense (such as access to 3 sublicenses), no changes in allotment will be made to either Seats Occupied or Seats Allocated until a user has redeemed the registration code. So if a learner redeems the registration code for 3 sublicenses within a panorama, both Seats Occupied and Seats Allocated will increase by 3 within that panorama.
Redemption Codes:
When a redemption code group for 30 codes is created and a single panorama and sublicense is attached, Seats Allocated for the Panorama will immediately increase to 30, because those seats have been accounted for. But the Seats Occupied will not change (remain at 0), until a learner has redeemed the Redemption Code.
Example
If a redemption code provisions more than one sublicense (for a total of 3 sublicenses), then upon creation, the Panorama Seats Allocated field will only display 1 Seat Allocated per code created. Once a learner has redeemed the redemption code, then Seats Allocated will increase by 2 (for a total of 3).