HTML Widget, HTML Widget link

Hi - where gstager is technically correct, consider a few things before getting spun by permissions and all. There is nothing worse than sending a person a url and they get a permission error and you sit there asking yourself...”but why”? 

1. internal pages are given access to based on the Menus and Pages portion of the system. To have people land successfully, start there first (in the menus portion of the system).
2. depending on how this is wired for you, you can land up with security issues depending on what you then provide on page.
   • for example you could put a course link via the HTML widget, and a person may not land on the course. Just because you put a link to a course on a page, doesnt mean a person will have the right access.
     • If you are looking to “hard code” a link to a course on a page, I have had better success using the deeplinks provided to ensure that a person can land. It has a side effect to it (they are immediately enrolled) but that is a safeway to have them proceed without tackling permissions/rights.
   • Another way to think about it, if the page is an “open page” then you probably want to serve up courses via the catalog widget to ensure a best outcome.
     • and then catalogs can have their own security as well.
3. there are nuance(s) to how you cook this. It is the beauty of a learning experience platform and the challenge for newbies to grok and tackle. Setting up the correct menus and page structures will only lead you to happiness, so take the time to learn those nuances.
4. Consider that the rest of @gstager approach is solid - just know if you want a person to land everytime on a page they have access to? You probably want to consider your menus carefully.

Good luck.