Navigation in courses - User Specific

The way I look at it, any object can be turned into a button by adding a trigger that runs when the object is clicked. In other words, it doesn't matter what the user clicks to choose their role. It only matters that clicking the object adjusts the variable to the proper role. 

However, if the buttons have a Selected state, they should be put into a button set. A button set acts like the radio buttons in a multiple-choice question. Only one item can be selected at a time. Selecting one automatically deselects the others. That's needed so it's obvious which button is selected. Here's more info: 

• Storyline 360: Working with Button Sets | Articulate - Community 
• PRIMER: Take advantage of built-in states | Articulate - Community 

I mentioned in a previous reply that inserting the variable reference isn't required (that is, you don't need to show the variable's value on the slides). But, as I also said, it can be helpful to display the variable reference when you're programming. That lets you see if the variable is changing as expected. 

You said "it doesn't seem to translate once there is a branch." It's possible that the triggers aren't adjusting the variable as expected. Or (and this is an easy mistake to make with text-variable values), the condition in the trigger for branching has the wrong value entered. 

It's difficult to troubleshoot without seeing the .story file, so I'll repeat something else from a previous reply: 

I suggest you carefully review all the previous replies and links, as well as the demo file. Then try programming the first part of your course, or even just a simplified, mock-up project. When programming and testing that, pay extra attention to ensure every trigger refers to the appropriate variable value and slide.

Then, if you have additional issues/questions, start a new discussion that includes a copy of your .story file and details about what isn't working as expected.