
Bring your Storyline and Rise courses into Juno
Imported once, then edited in plain words: same link, same assignments, every version kept.
- For
- L&DCustomer Education
- Routine
- Once
- Setup
- Juno + 2 tools
- You approve
- every draft
What you get
Before
Security basics 2023
SCORM package
Updated March 4, 2024
After
Security basics 2026
Course
Updated September 28, 2026

Phishing in practice
Interactive lesson
Updated September 28, 2026
The prompt
Written to ask before it assumes, check what already exists, and stop before anything goes live.
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.
Your AI asks you
- Q1My role and the team I support
- Q2How many packages, and where they are today (our old LMS, a drive, a list)
- Q3Which ones matter first
- Q4What usually changes in them (dates, names, logos, policy text)
The routine
- 01
Connect
Juno and the tools below
- 02
Answer
the questions, one message
- 03
Review
the draft or the view it builds
- 04
You approve
before anything goes live
What it connects
- JunoRequired
- Google Drivevia your AI assistant
- SharePointvia your AI assistant
Your AI assistant reads the tools it can reach and drives Juno.
Where this Journey Play works
Journey Plays that go with it

Change one fact in every SCORM package
A rename, a new logo, a changed rule: found and fixed across your library, one approval.
When it happens
Turn a SCORM package into a course anyone can edit
The content of a locked package, rebuilt as a native Juno course with its quiz.
When needed
Sort the library before you move it
Keep, merge, rebuild or retire: decided before the migration, not after.
Once






















