How to Ensure Mighty Features Stay Intact When Sharing Rise Courses
Articulate Rise preview links do not always show Mighty mods and blocks. Here’s a practical Review 360 workaround for sharing courses with Mighty features baked in.
You’ve added Mighty functionality to a Rise course, sent a preview link to a stakeholder, and then—nothing. The course opens, but the Mighty mods and blocks you carefully built don’t render.
This can be frustrating, but fear not! There’s a reliable workaround using Review 360 that lets you share the course with Mighty features intact.
Why Rise preview links can miss Mighty features#
Articulate Rise preview and share links are convenient, but they work a little differently behind the scenes.
When you use a standard Rise preview or share link, Articulate builds the course on the fly. Because of how that preview environment works, Mighty can’t always inject all of its functionality into that version of the course—unless the person viewing it also has the Mighty Chrome extension installed.
And most of the time, that’s not the case.
Your SME, client, manager, or stakeholder probably doesn’t have the extension installed. They’re just opening a link. So, if you send the regular Rise preview link, they may see the basic Rise course, but not the Mighty functionality you expected them to review.
This is a Rise sharing limitation, not a sign that your Mighty work is broken.
The better option: publish to Review 360 first#
Instead of using the standard Rise preview link, publish the course to Review 360. Once the course is published there, you can open the Review version and grab the course iframe directly.
That iframe version does not include all the Review 360 interface around the course, but it does include the Mighty functionality baked into the published course.
Here’s the workflow.
How to share a Rise course with Mighty features intact#
1. Finish your Mighty-enhanced Rise course
Start in the Rise editor with your course open.
This workaround is meant for courses that include Mighty functionality—things like Mighty mods, blocks, or other enhancements that won’t reliably render through a standard Rise preview/share link for someone without the Chrome extension.
Before publishing, give the course a quick check on your end with the Mighty extension installed so you know the experience is working as intended.
2. Publish the course to Review 360
From Rise, publish the course to Review 360.
This creates a Review 360 version of the course. It’s different from the normal Rise preview/share link, and that distinction matters here.
Once the publish is complete, open the course in Review 360.
3. Let the Review 360 course load fully
When the Review 360 link opens, wait for the Rise course itself to load.
You’ll see the course embedded inside the Review 360 page. Review 360 adds its own commenting and review functionality around the course, but the course content is sitting inside an iframe.
That iframe is the piece we want.
4. Inspect the Review 360 page
Right-click on the page and choose Inspect.
This opens your browser’s developer tools. If that sounds more technical than your usual Rise workflow, don’t worry, you’re not editing code here. You’re just locating the iframe that contains the actual course.
5. Find the iframe object
In the Elements panel, scroll up until you find the iframe object for the course.
In the video walkthrough, the iframe appears in the page structure, and inside it you’ll see a #document item. That #document is the embedded course document inside the Review 360 page.
You’re looking for the iframe that contains the Rise course—not the Review 360 wrapper, comments, or surrounding page controls.
6. Open the iframe document in a new tab
Right-click where it says #document inside that iframe.
Then choose Open in new tab.
This opens the course itself in a new browser tab, without the extra Review 360 functionality around it.
This direct iframe version has the Mighty functionality baked into the course, so your reviewer can see the enhanced experience without needing the Mighty Chrome extension.
7. Copy and share the new tab URL
Once the iframe opens in a new tab, copy that URL from your browser’s address bar.
That’s the link you can send to your stakeholder, SME, client, or teammate.
They’ll get the course experience with the Mighty features intact, without the Review 360 interface around it and without needing to install anything.
When to use this workaround#
This is especially useful when you need someone to review the learner experience rather than comment directly inside Review 360.
Use it when you’re sharing:
- A Rise course that includes Mighty mods or blocks
- A custom interaction that needs to be tested
- A stakeholder preview where the Review 360 wrapper would be distracting
- A course link for someone who does not have the Mighty Chrome extension installed
It’s also handy when you’re trying to avoid the awkward feedback moment where a reviewer says, “I don’t see what you’re talking about,” because they’re viewing a version of the course that can’t render the Mighty work.
A quick note about Review 360 comments#
This workaround gives you a cleaner course link, but it also means you’re bypassing the Review 360 commenting layer.
So, if you need line-by-line stakeholder comments inside Review 360, send the normal Review 360 link. If you need someone to experience the course with Mighty features working and without the Review interface, send the iframe link.
A simple approach is to send both:
- “Use this Review 360 link if you want to leave comments.”
- “Use this direct course link if you want to preview the learner experience with the custom interactions working.”
That little bit of guidance can save a lot of back-and-forth.
Why this matters for real course reviews#
Mighty is often used to push Rise beyond the standard block library—more tailored interactions, custom-feeling layouts, and functionality that better matches the learning experience you’re designing.
But stakeholders usually don’t care how the course was built. They care whether they can open the link and see what learners will see.
This workaround helps you protect that review experience. It lets you share a course that reflects the work you actually did, not a limited preview version that happens to be missing the Mighty pieces.
It’s a small step, but it can make the review process feel much smoother.