Preview a Rise Course with Mighty Quick Share

Stakeholder review can get awkward when your Rise course uses Mighty features but you only need a simple preview link. Mighty Quick Share gives you that lightweight review link without asking reviewers to install extensions, dig through Review 360 code, or wait for a full LMS publish.

Mighty Meetup August 2026

This walkthrough is based on the August 2026 Mighty Meetup, where Mighty Developer John Pinkster and the team showed how the new Mighty Quick Share works directly inside Rise. If you have ever used Articulate’s quick share option and wished it preserved your Mighty blocks and Studio interactions, this one’s for you.

What Mighty Quick Share solves#

Articulate Rise has a handy quick share workflow for sending a standalone course link. But historically, this kind of instant Rise output did not include Mighty’s functionality.

That meant if your course included things like Mighty blocks, a moved or restyled Start button, or a custom Mighty Studio template, your reviewer might not see the course the way you built it.

The old workaround was not the kind of thing you want to explain to a stakeholder. It involved publishing to Review 360, opening the course output, and inspecting the embedded iframe code.

It worked, but it was fiddly. Mighty Quick Share replaces that with a direct share link from the course level.

When to use Mighty Quick Share#

Use this when you need a fast, low-friction preview of a Rise course that includes Mighty enhancements.

It is especially useful for:

• Sending a course to a stakeholder for a content review.
• Sharing a draft with another instructional designer.
• Previewing Mighty Studio templates in context.
• Checking how Mighty blocks behave in a standalone course link.
• Avoiding a full LMS or web-server publish just to get feedback.

It is not a replacement for final LMS testing. If you need completion, tracking, SCORM behavior, xAPI statements, or LMS-specific launch testing, keep using your normal publishing workflow.

Step-by-step: create a Mighty Quick Share link#

Here’s the practical workflow shown in the video.

1. Open your Mighty-enhanced course in Articulate Rise 360.
2. Go to the course-level publishing area.
   In the video, this starts from the top-level course screen—the same general area where you would normally publish or share your Rise course.
3. Choose Mighty Quick Share.
   Instead of using the native Rise quick share path, open Mighty Quick Share. This is the Mighty-specific option designed to package the course with Mighty functionality included.
4. Select Create Quick Share Link.
   Mighty generates a shareable link for the current version of the course. The link is ready right away.
5. Once the link is generated, copy it.
   You can open it in your own browser to check it, send it to a teammate, or drop it into a stakeholder review message.
6. Test the course from the link before sending it broadly.
   This is a good habit for any review workflow. Open the link in a browser and click through the spots where Mighty is doing work.

In the video demo, the shared link preserved the Mighty-enhanced course experience, including:

• A Start button that had been moved and modified.
• A Studio template inserted into the course.
• Other Mighty blocks and course content.

That is the whole point: the reviewer sees the Mighty version of the course, not a stripped-down approximation.

What the reviewer sees#

The reviewer opens a standalone course link in the browser. They do not need to install Mighty’s Chrome extension to view the shared output.

That matters because review audiences are often mixed. Your fellow course builders may know exactly what Mighty is doing inside Rise. Your SMEs, managers, legal reviewers, or clients probably do not—and shouldn’t have to.

Mighty Quick Share keeps the review experience focused on the course itself:

• Does the interaction make sense?
• Is the content accurate?
• Does the design match expectations?
• Are there layout issues to fix before publishing?

That is a much better review conversation than “hang on, you need this browser extension first.”

Important: it’s a snapshot, not a live draft#

One detail from the demo is worth underlining: a Mighty Quick Share link is a snapshot of the course at the time you create the link.

If you make edits in Rise after creating the link, those changes do not automatically appear in the existing shared version.

For example, in the video, the course was edited after the quick share link had already been created. When returning to the share link, it still showed the course as it existed at the time of sharing.

That behavior is familiar if you already work with Articulate publishing flows. A shared or published version reflects a point in time. It is great for review control, because everyone is looking at the same version, but it does mean you need to regenerate or update the share when you want reviewers to see the latest changes.

A simple review habit

When you send a Mighty Quick Share link, include a version note in your message:

• “Draft shared August 12—content review only.”
• “Version 2—updated intro lesson and scenario block.”
• “Final SME check before LMS publish.”

That tiny bit of context can save a lot of back-and-forth, especially when multiple people are reviewing on different days.

A note about zipped interactives#

There is one small loading behavior to know about.

If you’re adding an interactive through zipped files, reviewers may briefly see a loading screen when that content appears in the quick share output.

That does not mean anything is broken. It is just not quite as instant as a fully published final output. In the demo, it still loaded quickly and allowed full course navigation.

For stakeholder review, that is usually more than enough. For final QA, especially if performance is a concern, test the fully published output in the environment where learners will actually launch the course.

Where Mighty Quick Share fits in your workflow#

Think of Mighty Quick Share as the middle step between “I’m still building this in Rise but it needs to be reviewed” and “this is ready for the LMS.”

A practical workflow might look like this:

1. Build your Rise lesson with native blocks and Mighty enhancements.
2. Preview the course yourself in Rise.
3. Create a Mighty Quick Share link.
4. Send the link to stakeholders for review.
5. Make revisions in Rise.
6. Create a fresh share link when the review version changes.
7. Publish through your normal LMS or web workflow for final testing and delivery.

That keeps the messy middle of course development moving without turning every review into a publishing event.

Why this matters for IDs and L&D teams#

Most instructional designers are managing more than design quality. You’re also managing time, stakeholder confidence, brand expectations, accessibility checks, and the very real problem of getting clear feedback before launch.

A clean preview link helps with all of that.

When reviewers can open the course quickly and see the same Mighty-powered experience you see, they can respond to the content and design instead of getting distracted by access issues. And when the link is a snapshot, you have a stable review artifact: everyone is reacting to the same course version.

That is especially helpful on projects with tight timelines. You can share a polished-enough version for feedback without pretending it is final or rushing into LMS packaging before the course is ready.

Quick troubleshooting checklist#

Before you send your link, do one short pass yourself:

• Open the Mighty Quick Share link in a browser.
• Check the first lesson and Start button behavior.
• Visit any lesson that includes a Mighty block.
• Click through your Studio interactions if the course includes any.
• Watch for brief loaders on zipped interactives.
• Confirm the version you are sharing is the version you want reviewed.

If you spot an issue, go back to the Rise course, make the fix, and create a new or updated share link before sending it out.

The takeaway#

Mighty Quick Share gives you a practical way to send Rise courses for review while preserving the Mighty features you actually built. Use it when you need fast stakeholder feedback, treat the link as a point-in-time snapshot, and save the full LMS publish for final QA.