Bring your Storyline and Rise courses into Juno

Imported once, edited in plain words; links, assignments, and versions stay.

For
L&DCustomer Education
Routine
Once
Needs
Juno + 2 tools
You approve
every draft

What you get

Before

Security basics 2023

Security basics 2023

SCORM package

Updated Mar 4, 2024

After

Security basics 2026

Security basics 2026

Course

Updated Sep 28

Two engineers at their screens

Phishing in practice

Interactive lesson

Updated Sep 28

The prompt

Paste it into Claude or ChatGPT. It asks its questions in one message, then starts from what you already have in Juno.

Works in Claude, ChatGPT, and GitHub Copilot
I want to move our Storyline and Rise courses into Juno Journey and be able to change them from here afterwards, without going back to the authoring tool.

Use the Juno Journey connector for anything in Juno. If it isn't connected, stop and tell me how to add it (https://docs.junojourney.com/mcp/overview).

Before you build anything, ask me:
1. My role and the team I support
2. How many packages, and where they are today (our old LMS, a drive, a list)
3. Which ones matter first
4. What usually changes in them (dates, names, logos, policy text)
Ask these in one message, then wait for my answers.

For the folder or list of packages, check it is connected in this chat; if not, I'll connect it or upload an export. Never guess what is in it.

Importing a .zip happens in Juno's admin, not in this chat: give me the steps, and wait until I tell you which ones are in.

Then, for each imported package: open it and check in a preview that completion and score are tracked (play it through yourself if you can drive a browser; if not, give me the preview link), and list what can be edited from here and what sits in generated code that only the authoring tool can change. Give me one line per package: works, tracked, editable.

Offer the first fixes. Each save is a new version on the same link and the same assignments, and any version can be restored. Save only what I approve.

Don't assign or notify anyone.

What your assistant will ask you

  1. Q1My role and the team I support
  2. Q2How many packages, and where they are today (our old LMS, a drive, a list)
  3. Q3Which ones matter first
  4. Q4What usually changes in them (dates, names, logos, policy text)

How it runs

  1. 01

    Connect

    Juno and the tools below

  2. 02

    Answer

    its questions in one message

  3. 03

    Check

    the draft or the report it builds

  4. 04

    Approve it

    Nothing is published, assigned, or sent before that.

What it connects

  • JunoRequired
  • Google DriveConnected in your assistant
  • SharePointConnected in your assistant

Your assistant reads these tools and does the work in Juno.

Teams that use it