Foundant Courses are only supported on desktop sites. In order to access Foundant content use a laptop or desktop device.
General Course Guidance
- Click on the laptop with the graduation cap icon to access Foundant Courses or return to the Course at any time. This icon is only visible in Sandbox sites.
- You may be prompted to login after a period of inactivity; this is normal.
- Collapse each lesson section using the triangle icon to minimize scrolling when locating a new or incomplete lesson.
Wait For Each Step to Appear
If a lesson takes you through a workflow you’re already familiar with, you might find yourself getting ahead of the steps. This can cause the lesson to get stuck. Always wait for each step to appear before proceeding with the process, even if you already know which page you are going to and what you are doing. In addition, a slow internet connection may also be a cause for step delays. If this is the case, be patient as it may take a few seconds for the next step to appear.
Read All the Content Provided in Each Step
While some steps are simple and say, "Click Funds," other steps include important content for properly completing the lesson. Follow all the directions on the step as intended, so that you are able to complete the step properly and ensure the lesson continues without issue. Click the Foundant Courses icon to return to the lessons menu if you need to restart the lesson.
X Button in a Step
The x button is available in the top right corner of every step in a lesson. This x button allows you to leave the lesson without completing it.
Complete the actions described in each step until you reach the final step, and then click Done to ensure the lesson is fully completed. The Done button is typically located in a step that says, “Complete!"
Refresh a Page Using Ctrl+F5 (Command+R for Safari/Mac Users)
By refreshing your page using these hotkeys, you will refresh the saved cache for the page you are on. This will also refresh Foundant Courses and will occasionally resolve a "stuck" step if it wasn't caused by the above three reasons. If this does not resolve the issue, reach out to our Support for assistance.