To commence this workflow, you need to first confirm the UX around access to the Go1 Catalogue.

Some key questions to be tackled from your Product/Development team include:

Why would you choose to embed the Go1 Catalogue in your application?

What you need to consider when embedding the Go1 Catalogue in your application?

• What event triggers this iframe to display within your application, where does it live and who can access it?
• Will you create a single login to the Go1 Catalogue for all users, or will you create individual logins based on the user requesting access?
• Do you want to pre-select content filters for the user (e.g., auto-filtering to `Leadership` courses within the Go1 Catalogue)?
• How will your application handle identifying which courses to sync to your application (via a user-driven event or action vs. a schedule)?
• After retrieving Go1 Content metadata and retrieving SCORM, where does a user in your application see the course content?

Once you have a plan for the above, get started by creating a 1-time link to the Go1 Catalogue.