Forum Discussion
Authorized access to modules
Hi everyone,
I'm creating some e-Learning for a company and I want them to have access to modules that pertain to their job i.e., sterile compounding. If the mod does not pertain to their job, they don't get access. Is there a way to do this? Right now, I have all the mod with a hyperlink to a separate course, I'm hoping to add users to each course that pertain to that mod. If a user tries to access a mod they do not have access to, I'd like a page that states something like " you do not have access to this mod... please contact admin."Is a page like this possible?
Your LMS normally takes care of who has access and who not. Depending on the LMS they use most have a lot of options for this.
Hi Tara, I agree entirely with Math, you should try to control this via your LMS, however, if you must do this from within Storyline you could try this simple method.
Precisely! Trying to use storyline and not an LMS.
Thanks.
Hi Tara and welcome to the community!
I'll third the vote for using your LMS for this. A good LMS with access to HR data should make it easy to assign content based on role.
That said, if your LMS doesn't have access to that data and you're okay with learners self-identifying their role, you have some options directly in Storyline 360.Use branching:
- Create a start screen where learners click a button to identify their role.
- Each button links to a different version of the rest of the course, with role-approporate content in each branch. So in your Storyline project file you'll you have a shared home screen and multiple branches that lead to each of your different versions of the course.
Use variables:
- Create a main start screen where learners click a button or type in a text entry field to identify their role.
- Now you need to create a variable that tracks their choice. If you used a text entry field, that's taken care of you automatically. If you used a button, then create a variable for each role and add a trigger to each one to mark it as True.
- With that done, you can use variable triggers to change what content learners see. For instance, you could use a trigger to have Storyline skip a slide or branch your content based on their role. Or you can use triggers to show different layers on a slide, so a single slide can show different content based on the role that learners selected.
- Your final Storyline file will look like a single experience (possibly with a few small branches that come back into the main course) but will be different thanks to the variables changing the content.
The first of these options is best if you just have a small number of roles (such as a course that just has Manager and Individual Contributor versions) and/or a short course. It's really easy to copy and paste the first version of the course and then just quickly make the role-specific changes to each new branch. If you have a lot of different roles, though, a branch for each one leads to a LOT of slides and a large course file size. In that case, you can keep your course file size lighter by going with the second option.
Thank you for the warm welcome and the great information #BiancaWoods. This makes total sense. Appreciate the help
