In Storyline, how can I prevent the Player Next button from working until all layers are visited?
I am using Storyline. I have a large course with many slides. One slide has four layers in it. I want the player's next button to remain inactive until all of the layers are viewed. Each layer has several icons to be viewed, as well as a close button to go back to the main layer. How can I prevent the player's next button from being active UNTIL each layer has been viewed? I added a Storyline file to help with this solution.Changing Status on the Dashboard?
I have a Rise course currently in review and created a PDF copy for an SME. Unfortunately, publishing to PDF changes the status from "In Review" to "Published." I've been trying to figure out how to change it back. Will saving another version to Review change it back? At this point I don't want to play around with it without a clear understanding of how the dashboard status works. I searched for an answer and didn't see anything. Thanks! PennyCelebrate: AI Image Generator
Hi, I used the AI image generator to create a few images for a process block. The images turned out great!! When I generated an image that needed edits, the iterations were spot-on. Usually, it's hard to correct an existing AI image, but it was effortless! I also uploaded an existing image and asked it to incorporate the character into a new AI image, and I couldn't believe how good it was! Kudos, Articulate Team! Things are progressing fantastically! KandicePrint Slide Blank on Edge
I’m working on a Storyline 360 project where the goal is for users to be able to print a specific slide. The content of this slide was a bunch of variables that we gathered throughout the project (such as answer choices, client's name, etc.). Back in July, testing the published project in Review 360 in Edge worked perfectly. However, in late August 2026, the client reported that clicking the Print button in the Print Preview popup only showed a blank screen. I was able to replicate the issue after republishing to Review 360 and testing in Edge. Interestingly, the problem doesn’t occur in Chrome, where printing the slide works just fine. Anybody has this issue?Player play button not starting Audio in Review 360
I would like to know if anyone else is experiencing player issues on a project from storyline published to review 360. The project was playing correctly on yesterday. I am also experiencing this in old projects that have already gone through review and are now published to the LMS. Some slides play others I have go to the previous slide and return to the slide and then the audio plays. When I preview the entire project in Storyline all works fine. I believe Review 360 is glitching...Is anyone else experiencing this?Did the accessibility checker cause duplicate closed captions?
Hey, First off, I'm totally new to the accessibility checker before I publish in Articulate Storyline. After I selected almost all the issues (I really should study this accessibility tool before moving forward), I now see duplicate closed captions when I play Storyline as a published file in Review 360. How do I correct this issue? Thank you for your help,Review 360 links keep saving to another user's Private account, even after moving to a Team folder
I'm running into a Review 360 ownership issue that I can't shake, and I'm hoping someone here has seen it before. Here's the setup: courses are built in Rise 360. One team member, our Reach Admin, was the original publisher of a course to Review 360, which put the item in their Private directory by default. Since then, I (a different user on the same Articulate 360 team) have made edits in Rise and generated new review links for updated versions of the course. The problem: every new review link I generate still saves to the Reach Admin's Private account, not to my account or to a shared space. I can't update or replace the existing review link. My only option is to generate an entirely new link each time. What I've already tried, and ruled out: Moved the Review 360 item into a Team folder. Confirmed I have Editor/Manager access on the actual Rise 360 course itself, not just the Review 360 folder. Confirmed I am publishing from the Rise 360 dashboard, not from inside Review 360. None of that changed the behavior. New versions I publish still land somewhere outside my control instead of updating the existing Team item, and I still can't update the existing review link, only generate a brand new one. A few specific questions: Is review link ownership tied permanently to whoever first published the item, even after it's moved to a Team folder and the correct Rise-level Editor/Manager access is in place? Is there a setting beyond course-level Editor/Manager access and folder access that needs to be changed, maybe on the Reach Admin's account or a team admin setting, to let another editor publish updates to the same item? Does this behave differently depending on whether we're all seatholders on the same Articulate 360 team versus separate team accounts? For context: the person whose Private account this keeps saving to holds the Reach 360 admin role on our team, which is a separate permission system from Rise/Review 360. I checked and I don't have Reach 360 access myself, which just returns the standard "publish from your authoring app" message, so that appears to be unrelated to the Review 360 issue rather than the cause of it. We're all on the same team subscription, so this doesn't seem to be a cross-team permissions issue. I've seen at least one other report of a collaborator with Manager-level access getting an incorrect or unrelated "publish new version" dropdown, so I'm wondering if this is a known bug rather than a permissions gap on my end. Any insight into what's actually controlling this, or a workaround for keeping one stable review link across multiple contributors, would be a huge help. Thanks in advance.Articulate Storyline Publishing to Review - 'Something Went Wrong' Error Message
I've been attempting to publish to review an Articulate Storyline containing several MP4 files. Unfortunately, when I go to publish to review I get this pop up notification. I suspected that this was occurring because the MP4 file was originally stored on my personal drive before being imported into Storyline but had then been deleted. However, when I try to delete the videos and reimport them from SharePoint (where they will not be moved, renamed or deleted), I still receive this error message. My colleagues who have their own Articulate licenses are however able to publish to review my Storyline file once, but when they go to do it a second time they also receive the same error message. Has anyone come across this before and how did they fix it? So far I have tried the following troubleshooting but with no luck: Ensuring the blank Storyline file is automatically saved to SharePoint and never lives on a local drive Importing MP4 files from a shared space rather than a local drive Opening the Storyline file through both SharePoint online & SharePoint via files navigationReview 360 - Screenshot annotation is not what's displayed on Screen
I'm using Review 360 in Chrome for Mac OS. When I see a section I want to comment on, I create a comment and create a screenshot annotation and its not what I'm seeing. I've tried clicking inside the content to change the focus. Sometimes this works, sometimes this doesn't. Is there a trick to getting the right screenshot annotation that I am missing? BTW waiting a minute or two for the UI to catch up doesn't help.
