Oracle Learning Management uses Learner Access to determine which individuals and groups have the ability to view and enroll in any given Class or view and subscribe to any Learning Path, Learning Certification, Forum, or Chat.
Local access to a Catalog object may be defined by Assignment (some combination of Organization, Job, and or Position) or by Learner (an actual named person that exists within Oracle HR). For example, you could grant access enroll in a Class with manager approval to everyone in the Vision Organization, all Senior Programmers, or only John Smith.
Administrators have the ability to grant Learner Access at any level of the Catalog hierarchy (except for Session). Each object inherits (and potentially adds to) the learner access designated for its parent object.
In the case of a conflict, Learner Access that is specified at the highest level is always enforced.
For example, Learner Access that is specified at the top Category level will always prevail if there is a conflict with a Subcategory, Course, Offering, Class, Learning Path, Learning Certification, Forum, or Chat.
You must define a Learner Access model before learners are able to view or enroll in any catalog object. Through the concept of inheritance, you may open up the catalog for everyone with a login, define individual Learner access for each class, or specify any combination of access in between.
In order for Learner Access to apply to a Class, you must specify that it is restricted by checking off the Restricted box in the enrollment section when you set up the Class, Learning Path, Learning Certification, Forum, or Chat.
If you do not select the Restricted option then the object will only be subject to approval rules set for the entire system and anything that you've defined for Learner Access at any level above the Class will be ignored.
Strategies for Implementing an Effective Learner Access Model
Understanding the Restricted Checkbox
In practice, I think the Restricted checkbox is a bit of a misnomer and has been known to cause confusion among Administrators during initial rollouts. It may be better to personalize this field to say "Enable Learner Access" instead, as it really is telling OLM to check to see what Learner Access settings have been set and / or inherited for this specific Class. This designated access may really not be restricting anything at all, but could instead be opening up access for self enrollment.
The Importance of Planning Ahead
It is very important to carefully plan your Learner Access strategy before rolling out OLM. If you do not set a Class to look at Learner Access when you create it by making sure to check the Restricted checkbox, it will not be possible to change this setting after someone has enrolled (or been enrolled) in that Class. It is (sometimes unfortunately) possible to uncheck this Restricted checkbox on a Class after you have initially set it (even after enrollments have occurred), but there is no turning back.
If you find yourself in a situation where you have neglected to enable Learner Access on a Class where it is necessary, you must create a new copy of this Class and end date the initial Class in order to implement the necessary Learner Access.
Thus, as a best practice, it is recommended that you enable Learner Access for every single Class that you create within Oracle Learning Management even if you do not think that you will ever need to modify Learner Access in the future. By following this advice, you reduce the risk of requiring tedious, manual updates if unforeseen changes in your Learning delivery models or content pricing structures should occur (i.e., bringing in content from a third-party vendor that requires manager approval because of added costs).
Always keep in mind that Learner Access that is specified at the highest level wins out in the case of a conflict with access that is defined at a lower level. It is also not possible to exclude specific Learners or groups of Learners through Learner Access (i.e., you cannot specify that everyone except for John Smith has the ability to self-enroll in a training Class).
When defining a model that makes sense for your specific organization, you should be sure to specify Learner Access at the:
- Highest level that makes sense so that you do not have to needlessly update multiple child objects
- Lowest level that makes sense so that you do not have to rework all of your settings when you add in new objects that have different security needs