|
|
|
Sessions define an instance of a learning module. They are used to capture course information unique to a particular training session or that changes over time. For example, for classroom-based courses each session may have its own date, venue, instructor and participants. Sessions are also used to assign learning modules to programs.
At least one session must be defined for any module type that requires enrollment processing (except Just-in-Time learning modules, which do not have sessions), such as online and classroom-based courses. With the exception of classroom-based modules and programs, when you create a new learning module, an active session is also created. Multiple sessions can be scheduled for the same time provided that there is no conflicting resource use.
Sessions have their own properties, which you configure for a particular instance of the course. Some session properties can inherit values from the learning module, so you don't have to configure them again. Alternatively, they can be configured individually for each session and take precedence over the module-level property.
To configure a learning module and its sessions, your user role must have the required access control to the LMS features associated with course administration, such as the Catalog Editor. The required permissions are available to users with the Course Administrator System Role.
Sessions can be created and configured, along with modules, using the Course CSV Loader.
To create multiple sessions in the LMS more efficiently, you can clone a session multiple times and update only the properties with different values for each cloned session.
Session availability for enrollment is defined by its Event Status. For more information, see Session Properties.
Sessions can be deleted from the LMS if there are no users enrolled in them.
Additional Information
