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!SOCIAL LEARNING in Articulate Rise
I LOVE Articulate Rise but... I am aware of the fact that the possibilities for Social Learning with these courses are none. And what I mean by that is the letting the learners to drop comments about specific sections of the course and have replies and interactions with those comments. I know it is hard to develop something from scratch but... wait a minute! That is exactly what the REVIEW 360 section does with the courses. What if.... Articulate uses the same engine to manage comments already available for Review 360 and let us use it to be able to add comments to blocks of the course?? Please respond or vote to this if you agree. I am not optimist, but you never know.Rise 360 Theme update
With accessibility being critical could there be some future enhancements for changing theme colors for fonts and buttons? We have brand color requirements and there are too many limitations for setting theme colors for fonts and buttons. This would be a huge help to ensure course designers are meeting accessibility requirements. It would be an amazing upgrade if users had options to edit buttons and title fonts that don't carry through and change the entire course.Ideas Portal
The community has suggested a huge amount of ideas over the years. Can we have a searchable portal so we can see them all in one place: ID/Category/Post Date/Review Date/Description/Comments/Votes/Related Ideas Status Reviewed Under Consideration Low Probability of Delivery Fair Probability of Delivery In-Progress Currently AvailableWill Articulate 360 Standard Team (Non-AI) Still Be Available After March 31, 2026?
Hi! Recently, we received an email from Articulate saying: After 31st March 2026, all subscriptions will be upgraded at renewal to Articulate 360 AI, which may impact your current pricing. Does this mean the Standard Team plan (non-AI) will no longer be available for purchase after March 31, 2026? My organization currently has an Articulate 360 Standard Team subscription (expires April 2026). We buy new licenses annually through a public tender and need to plan the exact license type and pricing in advance. If anyone has official clarification from Articulate, please share. Thanks!Enhancing Review 360 Feedback Management with Categorization Tags
Currently, in Review 360, feedback and comments provided during reviews are captured in a generic format without any structured categorization. This often leads to ambiguity when interpreting feedback, as reviewers and developers must manually infer whether a comment refers to an error, an enhancement suggestion, or a query. The lack of classification makes prioritization and resolution time-consuming, especially when handling large volumes of feedback across multiple stakeholders. Post-implementation of the proposed feature—a dropdown selection allowing users to tag feedback as Error, Enhancement, Query or Not applicable—the process becomes significantly more streamlined. Categorization at the point of entry ensures clarity, enabling teams to filter and sort feedback based on type, prioritize critical issues, and allocate resources effectively. This structured approach not only improves communication between reviewers and developers but also accelerates decision-making and enhances overall productivity by reducing misinterpretation and manual effort. This categorization should also be reflected in the generated reports.
