Limiting Visibility of Feedback Comments - Review360
When I have a course out with several reviewers for feedback, it would be useful if I could choose to limit visibility of everyone's feedback to just the person doing the review. For example: Person A is very influential and opinionated in their feedback comments on the course. Person B can see Person A's comments and just "echoes" them rather than providing their own, sometimes different perspective and feedback, because they do not want to be different to Person A. Please could you consider adding the option of choosing if the comments are visible to "All" reviewers or "just their own" please from our review project settings.Ability to See Active Reviewers in Review360
I think it would be very helpful to add a feature that allows course authors to see when SMEs or reviewers currently have a course open in Review 360. There are times when I notice a minor issue that needs to be corrected or want to make a quick update before additional reviewers access the course. However, one drawback of publishing a new version in Review 360 is that if someone currently has the course open, publishing the update resets their progress and takes them back to the beginning of the course. Being able to see whether reviewers are actively viewing the course would help authors determine when it is safe to publish an updated review version without disrupting the reviewer experience.PDF Reader or View PDF via Scrolling Panel
The ask: Could a PDF reader or an addition to the scrolling panel allowing PDFs be added to Storyline's functionality? Our team is required to present manual pages in our lessons, necessitating the use of a scrolling panels. To display manuals or textbook pages that are saved as PDFs in Storyline, you must process the conversion of the PDF in a third-party program. After the conversion, you must import the images and align each page individually in the scrolling panel. The pages must be grouped in a certain way for the scrolling panel to populate correctly. I’ve included a Review 360 link with an example of what the end results looks like: Review 360: PDF Scrolling Panel Example If a PDF reader was included in Storylines toolset, it would make life for designers much easier. Our team is looking for the following features: Allowing PDFs to be imported into Storyline without the need for conversion to JPEG or PNG Automated scrolling for multiple pages. Say the PDF has multiple pages, the user can either flip through the pages or scroll through them. How would it function?: Additional functionality to scrolling panels OR including a built in PDF reader to Storyline's toolset Additional Functionality: Zoom functions Enable PDF bookmarks We appreciate any updates or notice on building this functionality, if possible.Centralized Alt Text Manager with AI Suggestions for Rise 360
Description: I'd love to see a centralized Alt Text Manager within Rise 360 where authors can view and edit the alt text for every image in a lesson or course from a single location. Instead of opening each individual image block, the Alt Text Manager would provide an accessibility dashboard that streamlines authoring, SME review, and quality assurance. Suggested functionality: Display every image in the lesson or course with a thumbnail preview. Show the current alt text or clearly indicate when alt text is missing. Allow authors to edit alt text directly from the dashboard. Identify decorative images separately from informative images. Include filters (e.g., Missing Alt Text, Decorative Images, AI Suggestions). Optionally provide AI-generated alt text suggestions that authors can review, edit, and accept. Why this would help: As instructional designers, we frequently collaborate with subject matter experts (SMEs) to review course content. SMEs are often the best people to describe the educational purpose of an image, but the current workflow requires them to open each image individually to review or edit its alt text. A centralized Alt Text Manager would allow SMEs and instructional designers to: Review all image descriptions in one place. Quickly identify images that still need alt text. Ensure descriptions accurately reflect the instructional intent of the image. Perform accessibility reviews much more efficiently during QA. AI-generated suggestions could further reduce authoring time by providing a strong starting point, while still allowing human review and editing to ensure descriptions are accurate and instructionally meaningful. For courses with dozens or even hundreds of images, this feature would save significant time, improve collaboration between instructional designers and SMEs, and help authors produce more accessible courses with greater consistency."Proofing Mode" toggle to bypass forced navigation for SME review
Hello! I'd like to put in a feature request for a "Proofing Mode" toggle in Rise 360 that allows SMEs who are reviewing/proofing courses to bypass any restricted navigation, especially those restricted using the Continue block completion settings. Courses built with restricted/forced navigation are great for learners but painful for SME reviewers, who have to click through sequentially even when they just need to jump to a specific lesson to verify content. This restriction happens at two levels: the Continue block's Completion Type (Complete Block Directly Above / Complete All Blocks Above), which gates progression within a lesson, and the course-level navigation setting, which gates movement between lessons. Requesting a single-click "Proofing Mode" (available in Preview or via a review link) that overrides Continue block completion requirements for reviewers only. I believe course-level restricted navigation should follow suit automatically; if a reviewer can bypass block completion, they should also be able to move freely between lessons. If implemented, this would save real time for L&D teams as SMEs review content before launch. Thank you!Microsoft 365 Copilot connector
I would like to request a Microsoft 365 Copilot connector for Articulate tools, starting with Review 360 and potentially extending to Rise and Storyline. The goal is to enable a single Copilot-powered “Peer Review Assistant” that can access course content and support structured, consistent review workflows aligned to defined quality standards. The connector would enable a Copilot Agent to: Review course content and provide structured feedback Access courses within Review 360 Analyse on-screen content, structure, and interactions Interpret course flow, scenarios, and learner decision points Evaluate content against: Instructional design quality Accessibility standards Storytelling and scenario-based learning principles Action-oriented and decision-based learning design Generate actionable feedback linked directly to specific on-screen content Reference examples from the course to support review comments Distinguish between confirmed issues and areas requiring human validation Integrate with style and governance sources Connect to a Style Guide hosted in Rise 360 or Sharepoint Validate tone of voice, terminology, and consistency Flag deviations from writing, accessibility, or branding standards Identify opportunities for designer development Map identified issues to underlying skills, for example accessibility, scenario design, and assessment design Explain why the issue matters from a learning design perspective Provide practical guidance on how to improve Encourage reflective improvement rather than only corrective feedback Value Reduces manual effort in peer review and QA processes Improves consistency across reviewers and courses Embeds accessibility, instructional design, and style standards into the workflow Enables scalable, repeatable review practices across teams Supports more effective learning experiences by focusing on outcomes, not just content Supports ongoing capability development for learning designers, not just course quality assurance I’m also keen to hear from anyone else in the community who would benefit from this idea. Thanks!Allow publishing access for more than one owner
My team works in a very collaborative environment and the "owner" of the course in Rise360 may not be the only owner or the only person that needs access to publish the course to our LMS. We previously all had access to publish the course as long as we were listed as collaborators (manager or editor). As of today, this access is gone and only the owner has the option to publish the course. I saw in Articulate Community that this question has been asked previously in the context of an employee leaving the organization and it was recommended to just share the link. This does not allow us to publish the course in our LMS to track completion for compliance. I'm not sure what changed for us to previously have access to the publish feature regardless of ownership or why we no longer have the access to do so, but there should at the very least be an option to assign collaborators as "co-owners" so we can have equal publishing/modification rights on team projects. Thank you!Review Rise - Comment or Reply
Hello, ISSUE 1: I frequently notice that SME's tend to keep using the reply bar instead of a new comment during review. In below image you see 4 remarks which all should have been separate comments with their own screenshot of what they are talking about. When logging in as reviewer myself, I understand the flow these people had while reviewing and cant really blame them. The UI is just leading them astray a bit in my opinion. FIX 1: I think the comment bar should be made dark gray instead of kept white and should be moved all the way to the bottom, or at least below the comments. This way it should catch the reviewers eye better. ISSUE 2: While on this topic, I also noticed that when I am processing all the comments, the order of the comments is in reverse to what I need them to be as authorer. This means the comments made last (bottom of their page) by the SME are showing on the top when I am working a e-learning page. FIX 2: The comments could have a sorting button maybe, or just reverse the order which should be a really easy fix. Hope this helps!
