Khoros Communities: Trainings and Coaching Sessions
To enhance your communities expertise, we offer a comprehensive suite of world class training videos and personalized coaching session. our tailored resources are designed to guide you through every aspect of building and maintaining vibrant communities, from foundational concepts to advanced engagement strategies. By leveraging our expert-led-training and customised coaching, you can unlock the full potential of Khoros communities and create exceptional experience that drives meaningful connections and results. Khoros Communities - Aurora: Start your journey here Product Coaching (1-on-1) Sessions Introduction to Aurora Aurora Community Settings Overview Aurora Community Designer Overview Aurora Community Analytics Overview Aurora Community Content Moderation Aurora Roles & Permissions Deep Dive Aurora Spam Management Best Practices Approaching Aurora in Analytics Aurora Community Experience Survey Don't see the session you need? Sign up for a 20-minute Q&A Coaching session if you have specific questions on the Khoros Communities - Aurora Platform. Aurora Training Videos Exploring Settings within Aurora (For New Admins) Khoros Communities - Classic: Start your journey here Classic Communities Admin Hub: Admin Training Videos Getting Started as an Admin Community Bulk Archive Content Admin Product Coaching (1-on-1) Sessions Admin Console Overview Introduction to Communities Classic Communities Analytics Hub: Classic Community Analytics Training Videos Getting Started as an Analyst Analytics Advanced Filter Community Analytics Personalization Classic Community Analytics Product Coaching (1-on-1) Sessions Community Analytics Overview Classic Communities Moderators/Managers Hub: Classic Community Moderation/Manager Training Videos Getting Started as a Manager Building Community Structure Introduction to TKB and Blog Workflow Article Dashboard Article Workflow Blog Dashboard Community Events 3-step workflow for Blogs Getting Started as a Moderator Moderation in Manage View - Care/Community Classic Community Moderation/Manager Product Coaching (1-on-1) Sessions Moderation Tips & Tricks Spam Management Roles & Permissions Deep Dive Group Hubs Studio Overview Events Overview Classic Communities Developer Hub: Classic Community Developer Training Videos Getting Started as a Developer SDK and Freemarker in Community - Tech Stack and Customization Community Events Studio Component Help Resource Center Community Classic Community Developer Product Coaching (1-on-1) Sessions Khoros Communities Search Tools Community Syndication Blogs & Knowledge Base Workflow Don't see the session you need? Sign up for a 20-minute Q&A Coaching session if you have specific questions on the Khoros Communities - Classic Platform.7.9KViewsSign in to react to this post6Comments
Khoros Communities 25.9 - Release Notes
The Khoros Communities 25.9 release includes performance improvements, stability enhancements, and bug fixes across search, caching, authentication, and moderation features. Classic Fixed inbox search not returning results for partial word matches. Fixed an issue where the private notes page would error when performing an empty search. Fixed image URLs not being indexable by search engines due to incorrect robot headers. Fixed an issue where Salesforce user ranks were not updating after the initial sync. Fixed archive dashboard totals showing incorrect counts due to deleted boards being included. Fixed delete confirmation errors preventing content deletion. Fixed event pages showing errors after creating and publishing new events with optional livestream details. Aurora Fixed an issue where Salesforce user ranks were not updating after the initial sync. Fixed archive dashboard totals showing incorrect counts due to deleted boards being included. Fixed an error that occurred when viewing analytics for occasion reply messages. Fixed unread and view counts not updating without a page refresh. Fixed inbox search not returning results for partial word matches. Fixed an issue where the private notes page would error when performing an empty search. Fixed image URLs not being indexable by search engines due to incorrect robot headers. Fixed an authentication issue where cookies were not being properly echoed during login/logout flows. Fixed an issue where session cookies were being incorrectly cached for anonymous users. Improved page caching performance by moving from memory-based to filesystem-based storage. Fixed a page caching issue that was reusing parent frame IDs across different users. Fixed the 3-dot action menu not working properly in text key mode within Manage Content. Fixed the 3-dot action menu not appearing for reported private messages in Manage Abuse. Fixed message action menus not responding consistently across different content types. Fixed message preview pages reloading endlessly and preventing user actions. Fixed duplicate replies being created when responding to messages at deeper thread levels. Fixed pagination issues with archived messages where the cursor was not advancing properly. Fixed a null pointer exception occurring when deleting articles via API. Fixed an issue where followers were not consistently receiving edit notifications according to their preferences. Fixed subscribers receiving unnecessary emails for non-publish workflow actions. Fixed an infinite initialization loop occurring in SDK preview for custom components. Fixed an issue where component assets were not loading correctly when switching branches. Fixed database errors caused by custom field metadata keys exceeding the allowed size limit. Fixed an issue where pasted email addresses were being replaced with suggested users when pressing Enter in group/event invites. Fixed delete confirmation errors preventing content deletion. Fixed event pages showing errors after creating and publishing new events with optional livestream details. Staging and Pre-Prod rollout: September 15 Production rollout: September 29 The rollout will follow the standard maintenance windowsViewsSign in to react to this postCommentsTake a tour of Aurora
Welcome to Aurora. We've put together this video training course to help you get familiar with key features and concepts about Khoros' re-imagined Community Experience. This 12-video series is grouped by four community roles: Managers Moderators Developers Members The entire course takes about 1 hour to complete. Note: We will be updating these videos and adding new ones as we continue to roll out new Aurora features. Subscribe to this article to be notified when new videos are available. Community Managers Community Overview Building your community structure Designing your site Configuring feature settings Roles and permissions Gamification Measuring success Community overview (3:49) Building your community structure (6:03) Designing your site (7:54) Configuring feature settings (4:52) Roles and permissions (4:51) Gamification (4:23) Measuring success (3:08) Community Moderators Moderating your community (9:14) Community Developers Getting Started as a Developer Getting Started with Handlebars Creating Handlebars GraphQL API Getting Started as a Developer (4:58) Getting Started with Handlebars (6:56) Creating Handlebars (4:20) GraphQL API (3:54) Community Members Personalize your community experience Getting around and finding the content you want Contributing to the community Using your inbox Personalize your community experience (3:45) Getting around and finding the content you want (1:54) Contributing to the community (4:55) Using your inbox (2:46) What to read next: Getting Started as an Administrator Getting Started as a Community Manager Getting Started as a Site DesignerViewsSign in to react to this postCommentsKhoros Communities 25.12 Release Notes
The Khoros Communities 25.12 release delivers extensive accessibility improvements across both Classic and Aurora platforms, critical security fixes, significant search and analytics enhancements, and numerous stability improvements for content management, rich text editing, and API functionality. Classic Applied input sanitization for survey form submissions to ensure data integrity and security. Fixed slide-out navigation menu accessibility violations including improper button element nesting and focus management issues affecting screen readers. Fixed spoiler tags scrolling to page top instead of expanding content on first visit due to script loading latency. Fixed Q&A structured data linking accepted answer URLs to author profiles instead of actual solution posts, improving SEO accuracy. Fixed LiQL query operator "!=" to correctly apply multiple exclusion conditions, allowing users to exclude multiple nodes in a single query. Fixed code snippet syntax highlighting disappearing when editing posts containing li-code elements. Fixed post counter incorrectly decreasing when deleting product idea status updates. Enhanced V2 API error messages to specify which field and content caused validation failures, providing actionable feedback to API consumers. Fixed post approval failures in moderation manager showing false success messages when approving spam in archived threads. Fixed kudos leaderboard displaying empty slots when deleted users were included in rankings. Fixed API errors when querying subscriptions for label objects. Enabled text key scoping for TKB template selection page to support template-specific customization. Fixed API errors when retrieving posts containing malformed CSS classes in HTML content. Optimized settings editor to reduce search reindex latency from 20-90 seconds to under 3 seconds when updating large custom settings. Added comprehensive accessibility improvements including: proper combobox roles for all search and autocomplete fields; ARIA expanded/collapsed states for image upload controls; corrected button roles for file upload and avatar controls; keyboard focus management in settings tabs; screen reader announcements for file upload status messages; and notification settings sections defined as proper headings for navigation. Aurora Fixed critical authorization vulnerability in GraphQL endpoints to properly enforce permission checks for privileged operations. Implemented multi-select functionality for idea status filter in ideas widget, providing filtering parity with Classic Community. Implemented SEO improvements for tag pages including lowercase URLs, updated robots meta tags, and dynamic meta descriptions. Enabled notifications and email alerts for followed tags, resolving "No activity yet" displays despite active content. Fixed image lightbox not opening when clicking images in post replies. Fixed spotlight search bar disappearing for anonymous users when typing specific search terms. Fixed date calculations showing incorrect year values in user profiles due to improper rounding of negative numbers. Updated tooltip text from deprecated "Kudos received" to "Likes received" throughout Aurora. Fixed cookie banner reappearing on page refresh despite user accepting or declining consent. Fixed pixelated thumbnail image display across community pages on high-DPI displays. Fixed date preference not applying to profile page elements when set to absolute format. Fixed internal links not opening in new window when using Cmd-click on Mac or Ctrl-click on Windows. Fixed ZIP file attachment failures on Windows systems due to MIME type mismatch. Fixed GraphQL ancestorId constraint returning zero results for boards queries. Fixed timestamp mouseover displaying incorrect timezone after user login/logout cycles. Fixed idea status updates displaying status ID instead of custom status name in user profiles. Enabled bold formatting for hyperlinked text in rich text editor regardless of formatting order. Fixed roles filter in analytics to display all community roles instead of only 25. Fixed LithiumVisitor cookie being reset on every asset request, causing inflated visitor counts in analytics. Fixed graphqlAdmin permission elevation for addUsersToRole mutation in endpoints. Removed "Category:" prefix from browser tab titles on category homepages used as localized entry points. Fixed search filters being cleared when performing consecutive searches. Fixed quote button being hidden by browser context menu on touch devices by repositioning below selected text. Fixed card view image quality on high-DPR displays by increasing thumbnail dimensions. Removed inappropriate content filters from OAuth SSO token validation and abuse content moderation workflows. Fixed place filter in ideas analytics report to correctly scope data to selected category. Fixed missing user names in reply notification emails. Fixed featured badge display to show highest earned badge level instead of first earned. Fixed featured content widget briefly displaying restricted content to anonymous users during page load. Fixed image upload order and caption issues when uploading multiple images simultaneously. Fixed publication scheduler being obscured by footer UI elements. Fixed oversized image warning notification persisting across page navigation. Fixed "Show More" button resetting page scroll position to top on large threads. Fixed duplicate author attribution display in TKB contributor lists. Fixed locked indicator not displaying on threads with zero comments. Fixed date display formatting issue causing text wrapping in published article tables. Fixed analytics report table displaying incorrect numbers for values above 10 million. Fixed inconsistent auto-hyperlink conversion when pasting URLs and quickly pressing Enter. Fixed text pasting issue when replacing highlighted text from Notepad or VSCode. Whitelisted @fluentui/react package for custom component development. Added permission check to prevent image paste operations when user lacks image posting permissions. Fixed missing UI error message when group names exceed 40 character limit. Fixed images uploaded in HTML widgets displaying as broken due to malformed URLs. Fixed closed private messages in inbox failing to load when messages referenced deleted users. Fixed Annual Total Visits mismatch and incorrect contract period display in Community Analytics billing dashboard. Fixed missing GroupHub "Invite Sent" events in Firehose when invitations were sent via email. Fixed blank member registration graph in analytics caused by Elasticsearch circuit breaker exceptions. Fixed day-of-week misalignment in analytics "Match day of the week" year-over-year comparisons. Added comprehensive accessibility improvements including: text color control swipe accessibility on mobile; alt text for like icons and profile images; descriptive labels for form fields in private messaging; proper combobox announcements for all autocomplete fields; ARIA states for menu selections, sort controls, and expandable elements; improved button labels for skin tone picker, logo links, and context-specific actions; corrected button roles for rich text editor toolbar controls; and screen reader support for tooltips on mobile devices. Pre-Prod Rollout: December 15-16. Testing window open from December 16 through January 4. Production Rollout: January 6-7 The rollout will follow the standard maintenance windowsViewsSign in to react to this postComments
Khoros Communities - Updated Release Process
Updates 13-Oct-2025: Added more details and clarified communication process To improve your experience and simplify our release process, we are updating how we handle Khoros Communities releases. This updated process will start to apply from Communities Release 25.10. What's Changing Communities will have two types of releases going ahead - Standard releases and Patch releases Standard releases happen on a regular cadence and include features and bug fixes. Opted-in customers are automatically upgraded with clear windows to change their decision throughout the process Patch releases address critical issues outside the regular release schedule and are automatically applied to all customers on the latest version Automated support tickets make it easy to manage your upgrade preferences, request immediate upgrades. Normal support tickets can be used to update your Upgrade Notification Contacts (and for all of the requests your account team is also available) Email notifications keep your Upgrade Notification Contacts informed at every stage: release notes publication, stage upgrade completion, and production upgrade completion Production releases are published as scheduled maintenances on our status page, providing real-time visibility and updates if anything changes Clear timelines provide transparency with defined windows to adjust your preferences Standard Releases We will have a standardized release process for both Aurora and Classic. In a standard release, opted-in customers will be auto-upgraded to the latest release. These releases will include features and bug fixes. Version numbers for the standard release will follow the existing version numbers. However, we will no longer be treating releases as major or minor - we will treat every release as a standard release. Throughout this process, you can manage your upgrade preferences using automated support tickets or by contacting your account team, who can assist with any of these requests. The process will begin when we publish the release notes. The release notes will announce the plan and scope of an upcoming release. After we post the release notes here on ATLAS Community, customers will be notified by email and will have six days to change their automatic upgrade preference (opt-in or opt-out). After this period, we will upgrade the stage environments. We will then open a testing window, where customers can test on their stage environments and report any issues through support tickets. Customers will have thirteen days to opt-out if needed, allowing you additional time to validate the release with your specific customizations and integrations, for example. At the end of the testing window, we will perform the upgrade in production for customers who have not opted out during this period. For both stage and production, we will use existing Maintenance windows, as we expect downtime. Production releases will also be published as scheduled maintenances on our status page, where you can find real-time updates if anything goes out of schedule or is delayed. If you are on an older version, you have the following options: Use the automated opt-in ticket to opt back into auto-upgrades (you will receive the next scheduled release) Use the automated upgrade request ticket to upgrade to the latest released version at any time Communication All email notifications for standard releases are sent to your Upgrade Notification Contacts for each instance. To add, remove, or change your Upgrade Notification Contacts, contact our support team or your account team. Release Notes Publication Email When we publish the release notes here on ATLAS Community, your Upgrade Notification Contacts will receive an email containing: Link to the release notes Your current upgrade decision (opt-in or opt-out) The upgrade timeline for this release All customers, regardless of their upgrade decision, can change their preferences at any time using the automated support tickets. Stage Upgrade Completion Email After your stage environment is successfully upgraded, your Upgrade Notification Contacts will receive an email confirming: Stage upgrade completion Your current upgrade decision (opt-in) The scheduled production upgrade date How and when you can opt-out if needed (anytime during the two-week testing window) Production Upgrade Completion Email After your production environment is successfully upgraded, your Upgrade Notification Contacts will receive a confirmation email. Example Timeline Here's a typical timeline for a standard release: Day 1: Release notes published here on ATLAS Community; Upgrade Notification Contacts receive email with release details, current upgrade decision, and timeline Days 1-6: Period to change automatic upgrade preference Day 7: Release preparation (not possible to change decision anymore) Day 8-9: Stage environments upgraded; Upgrade Notification Contacts receive email confirming stage completion, upgrade decision, and production upgrade date Days 10-22: Stage testing window (opt-out available anytime during this period) Day 23: Release preparation (not possible to change decision anymore) Day 24-25: Production upgrade for opted-in customers; Upgrade Notification Contacts receive confirmation email Patch Releases Patch releases address critical issues outside the regular release schedule. These include security vulnerabilities, bugs affecting multiple customers, or issues impacting release stability. Patches are automatically applied to all customers on the latest version and cannot be opted out of due to their critical nature. Our team will publish the release notes, notify customers, and apply patches in a three-day window. Upgrade Notification Contacts will receive email notification when patch release notes are published. Version numbering for patch releases will follow <standard release version number>.<number>, where number will be incremented for each patch and reset after a particular standard version. As an example, the first patch after 25.8 will be numbered 25.8.1, the second patch as 25.8.2 and so on. However, the first patch applied after 25.9 will be 25.9.1. We will use Change windows for non-downtime needs and maintenance windows timeslots for downtime needs. Patch releases will also be published as scheduled maintenances on our status page, where you can find real-time updates if anything changes. If a patch applies to customers on an older version, your account team will reach out to coordinate the upgrade. Tickets We provide two types of support tickets to help you manage your upgrades: Automated Support Tickets Opt-in ticket: For opted-out customers who want to opt back in for automatic upgrades Opt-out ticket: For customers who want to opt out of automatic upgrades Upgrade request ticket: To upgrade to the latest version immediately at any time For more information on managing your instance upgrade settings, see How to Manage Instance Upgrade Settings with the AI assistant. Regular Support Tickets Manage Upgrade Notification Contacts ticket: To add, remove, or change contacts who receive upgrade notifications [Khoros Classic can also use this guide] Use these to enquire about a release, report bugs, or any issues encountered during testing or in your environment: How to Make the Best Use of the Khoros AI Support Agent. You can go to our product-specific support portal here: Khoros Community Classic and Khoros Community Aurora. What to expect next Moving forward, based on feedback on the new release process, we will also be reviewing the cadence of releases, which is right now monthly. The intent is to provide high-quality releases, minimizing customer disruptions, and allowing customers time to provide feedback and adjust.ViewsSign in to react to this postCommentsAurora Upgrade Playbook
Getting Started What is Aurora? "Aurora is a game-changing update to the industry-leading Khoros Communities solution, with a set of transformative capabilities that make it easier to deliver an exceptional member experience." Aurora is the major upgrade for Khoros Communities (Classic). First released officially on July 31st, 2023, Aurora is a total transformation of our top-notch community platform. We've completely revamped it, utilizing cutting-edge technologies and adopting a modern headless architecture. We have intentionally bolstered Aurora with powerful APIs that provide flexibility and robustness. From the very beginning, we've focused on creating an exceptional user experience, designing it with mobile-friendliness, performance, SEO, and accessibility in mind. It's a fresh start with a foundation built for the future of online communities. Jump to Features. Discovery: Am I ready for Aurora? The first step is to determine your readiness for upgrading to Aurora. There is no rush to move from Classic as of 2024, so it is essential to review where you stand and what you need in order to upgrade successfully. Secondly, it's good to remember that any change to your community presents an opportunity to revisit what success means and how your community experience supports success today and in the future. With this in mind, we encourage you to challenge yourself at each step of planning and ask, "How does this align to and support our business goals?" Getting started Understand Your Goals: While Aurora improves drastically upon the day-to-day community design, admin configuration, moderation, and end-user experience, in evaluating your readiness to upgrade to Aurora, ask yourself: What are your plans for the community in the coming year? How do they align with your business goals & strategy? Do you require certain features or integrations to support your community strategy and day-to-day management? How do you use them? Do you use SSO authentication? How does the authentication process work? (You may need to gather this information from the team that manages SSO at your organization.) How long will it take to gather resources to help you in the upgrade to Aurora? Evaluate Customizations: As a best practice, customizations should be limited to those where there is a clear business value and no alternative feature. With this in mind, we recommend you evaluate existing customizations in line with your community goals, and as part of your upgrade plan, consider your path to sunset any customizations you use today that do not provide measurable value to the community experience and its success. You may have custom features today (like widgets, special pages, etc.)—many of these can now be replaced with Aurora's built-in features. Where you can, we recommend switching to Aurora's features. It will not only save you the cost and effort to rewrite those components using new Aurora development tools but also help maintain your technical debt to that which is absolutely required. You can refer to the feature table on available features in Aurora. If you need help in this step, reach out to your development team, development partner, and/or your Khoros account team for assistance. Scope Customizations: If upon completing evaluation of your existing customizations you identify key customizations you need to maintain when moving from Classic to Aurora, send a request to your Khoros account team to start the process on scoping the Aurora upgrade work and cost for updating your customizations. Structure Changes: The community structure informs the user path through community and supports their ability to find content relevant to their need. As best practice it should be reviewed annually or whenever a change occurs in community or the business (e.g., redesign, product/service changes, etc.) Simply upgrading to Aurora takes your community structure, content, and members as is. As part of your upgrade planning, we recommend that you review the effectiveness of your structure in its current form, identify opportunities to improve, and plan to implement those changes. Structure changes can be made in advance of an upgrade. In fact, we highly recommend that you identify any opportunities to make these changes ahead of time—it can only positively impact the existing experience. If you would like structure changes to be included as part of your Aurora upgrade, this requires a migration to be added to your upgrade scope, which is an additional cost. Please review this need and communicate to your Khoros account team. Consider Previewing Aurora: If you think you might be ready to upgrade to Aurora in the next few months, you can request a temporary Aurora Preview instance with your CSM. Read on for more info on Aurora Preview instance set up. Engage with Khoros: If you have questions, please ask in this forum: Community Aurora Discussions Aurora Upgrade Tasks Overview & Recommended Actions When a community is upgraded to Aurora, automated tasks run in the background to ensure the data from Classic is now supported in Aurora. Here is a run-down on how that works: Upgrade Task What happens in the upgrade? Required Actions for Khoros Customer Tags and Labels Tags and Labels both merge into "Tags" in Aurora. Similar to Labels in Classic, you can set pre-defined and freeform tags. Root-level labels and tags are carried forward as is, but reply-level tags are not. Pre-defined labels are carried forward and set in the Aurora admin as "pre-defined tags." If a particular Tag and Label have names identical to each other in Classic, these will merge into one collective tag in Aurora. Before Aurora upgrade, it is recommended (but optional) to clean up tags and labels as they will come over to Aurora as is when you upgrade your community. If you decide to clean up tags after the Aurora upgrade, you will still have the options to replace and remove tags. URL Redirects URLs to pages in Classic have 301 redirects automatically set to the corresponding pages in Aurora. None Images & Videos Images and videos are now associated with content in Aurora. Images and videos contained within galleries (and not attributed to content) will not be moved to Aurora, but all images and videos within content will be moved forward. User avatars are kept on the upgrade to Aurora. Any custom avatars collections in Assets within Studio are not moved forward into Aurora. If you plan to move forward your custom user avatars, save these assets. Once your stage community has upgraded to Aurora, upload your custom user avatars in Designer. Roles & Permissions All existing roles and permissions configurations will be moved forward to Aurora. None Community Settings (Nodes, Content, Users) All applicable community settings in Classic will be applied in Aurora automatically. Certain settings are not available in Aurora, so expect discrepancies between Classic and Aurora. None Ranks All ranks and existing criteria will be moved forward. The icons will not be moved forward, you will need to add icons back in Aurora. There are new options for visual styles in ranks for the customer to choose. Review ranks and set the new visual style for the ranks that you'd like after the upgrade. Badges All "live" badges and existing criteria and badge icons will be moved forward. Badges in the "Create" tab in Classic will not be moved forward. Badges will be unorganized and placed in a single set right after the upgrade. Badges can now be organized into "sets." Review badges and organize badges into newly created sets after the upgrade. Idea Statuses All predefined idea statuses are carried forward. Statuses will be unorganized and placed in a single set. Idea statuses can now be organized into "sets." Review idea statuses and organize them into newly created sets after the upgrade. Upgrade Process Overview During an Aurora upgrade project, you can expect these steps: Customer Preparation: Use your temporary Aurora Preview environment to configure and design your community. You can request that Khoros import your existing stage admin settings (Structure, Roles/Permissions, and Ranks are supported) to this environment. Upgrade Stage to Aurora: Once you kick off your project, your Stage environment is upgraded first, and Khoros moves your configurations over from your Aurora Preview environment. In this step, configure Stage with structure, ranks, designs, customizations, etc. Test and validate everything on this instance primarily. In this step, you no longer have access to your Aurora Preview instance. Important Note: You are no longer able to use Studio Self-Publish after Stage is upgraded. Testing Your Data in Aurora (optional): Khoros Services team sets up a special temporary environment for you to test your Aurora configurations & designs with a scrubbed (no PII) copy of your production data (with content & members). This step may not be available if you upgrade on your own or with a partner. Final Validation and Launch: After testing and approvals, your Classic Production environment is upgraded to Aurora. Upgrade tasks are run in the background to make your data compatible with Aurora. In this step, you perform final validation and testing for go-live. Completion and Cleanup: Once the upgrade is complete and validated, you have successfully upgraded to Aurora! Aurora Preview Environments Once you have an Aurora Preview instance set up, you can collaborate with your Khoros account team on steps you can take before your Aurora upgrade. We recommend starting to complete these tasks when you first gain access to your preview environment: Explore Aurora features and capabilities. Collect assets, style guide, and taxonomy from your brand. Once you have an admin account, begin to customize the look and feel using the Theme editor (colors, fonts, design). Set up the community structure and create test content as needed. Add badges & ranks, and adjust designs if necessary. Review and validate preset tags. Customize pages using the Page Templates builder (page layouts, widgets, text). Review roles and permissions, and test user access levels. Fine-tune miscellaneous settings such as Robots.txt and Content Settings. We are confident that you will become comfortable with using Admin and Designer tools as you progress through this list, but feel free to leverage the Aurora educational material in Atlas: Getting Started in Aurora. Features Feature Description Accessibility WCAG 2.1 AA VPAT (in progress) Admin & Permissions Content Features, Audit Logs, Roles & Permissions Analytics Dashboards, Reports, Bulk Data API, Analytics APIs Authentication Registration, Sign-In, MFA**, SSO (SAML, OAuth), Multi-Auth (multiple SSOs) Blogs Blog Posts, Content Workflow and Approval, Co-authoring & Contributors, Version History Developer Experience GraphQL APIs, SDK, GitHub, Metadata, Custom Components (Handlebars & React**), Endpoints, Custom Pages, Forms Events Events, Zoom Integration Follows & Notifications Follows, Notifications, Email Templates Forums, Threading & Comments Forums, Solutions, Replies, Comments, Likes, Deep Linking Gamification Ranks, Badges, Top Members Privacy Cookie Banner, Terms of Service, GDPR/CCPA Ideas Ideas, Statuses, Filtering, Reporting Inbox & Private Messaging Inbox, Private Messages, Broadcast KBs Articles, Content Workflow and Approval, Co-authoring & Contributors, Version History Localization** Localized Text, User/Node Settings, Navigation, Text Overrides, Localized Community Rich Media & Video Images, Videos Embed, Video Hosting/Streaming Message Editing & Posting RTE, Attachments, emojis, Embedly, Autosave Content Moderation Abuse/Content Reports, Spam Management, User Bans, Content Filters, Flood Controls, Moderation, DSA Site Structure & Navigation Community Structure, Header, Footer, Breadcrumbs, Hover Cards, Navigation Links, Featured Places & Content, Recent Top Content, Custom Text/HTML Designer Page Templates, Widgets, Theme Editor, Custom Fonts, Avatars, Design Language Elements Search Spotlight, Embedded Search, Auto-Suggest, Related Content SEO Page level SEO, Sitemap, Robots.txt Groups Groups (Open, Closed, Hidden), Group Membership SFDC Integration User Sync, Case Portal, Escalations Tags Preset, Freeform, Management of Tags, Tags Widgets User Profile & Settings User profile, settings **In development The improvements to community in Aurora help community managers easily manage the day-to-day community with low hassle, are more intuitive for building customizations in the community, and allow for greater extensibility to bring outside platforms closer to your Khoros community via integrations. To discover more, check out the following resources: Aurora 2024 Roadmap (Now, Next & Future) Getting Started in Aurora Aurora Release Notes Developer Documentation Frequently Asked Questions Am I able to migrate data into or within my community during an upgrade? In the scenario where you need to migrate another community into your community, it is an option to engage with Khoros Services for migration during your Aurora upgrade project. Consult with your account team to discuss further and define your requirements. Can I update my structure or do a re-structuring during my upgrade to Aurora? When you upgrade your community to Aurora, it will upgrade it 1 to 1. There is no need for a migration map as the upgrade process is not a migration. All content, members, structure, and settings remain in place as your community is upgraded. This means that if you need to move content around in your structure or do a re-structuring during an Aurora upgrade, it is recommended that you do this prior to the Aurora upgrade. If your restructuring is extensive, it may require a migration, which will require scoping with Khoros and additional cost. Will I retain access to Classic Community Analytics (also known as LSI - Lithium Social Intelligence)? After you upgrade to Aurora, you will have access only to Aurora Analytics (metrics definitions can be found here). Though you will no longer have access to Classic Community Analytics dashboards, up to 2 years of historical data will be available in the Aurora Analytics Dashboard. Also, Bulk Data API v3 is available in Aurora, so you will be able to continue usage of the API for your own internal analytics needs.ViewsSign in to react to this postCommentsKhoros Communities 25.10 - Release Notes
Due to unforseen circumstances, the rollout has been delayed. The updated dates are reflected below. The Khoros Communities 25.10 release includes accessibility improvements, localization enhancements, performance optimizations, and bug fixes across search, messaging, and community management features. Classic Fixed a memory leak affecting system stability by improving object deduplication in integration point processing. Enhanced image upload security validation to prevent potential issues with malformed or malicious image files. Fixed global and embedded search not returning results when using Traditional Chinese characters. Upgraded Image Service to Node.js 22 for improved security, stability, and long-term compatibility. Aurora Fixed recurring 503 Service Unavailable errors affecting community pages by implementing automated service stability improvements. Added full localization support for Turkish (tr-TR). Added full localization support for Indonesian (id-ID). Added full localization support for Vietnamese (vi-VN). Corrected French translations for "Board" and "Post" across UI and email templates. Fixed private messages in the inbox not loading for users with large recipient lists. Fixed an issue preventing users from joining hidden groups via email invitations. Fixed global and embedded search not returning results when using Traditional Chinese characters. Fixed an error preventing administrators from accessing Localized Categories Settings due to duplicate key entries. Upgraded to official undici library release for improved long-term maintainability and security updates. Upgraded Image Service to Node.js 22 for improved security, stability, and long-term compatibility. Enhanced image upload security validation to prevent potential issues with malformed or malicious image files. Fixed intermittent HTTP/2 connection timeout issues by implementing client-side TTL management for pooled connections. Improved accessibility across the platform including: correcting heading structures in Tags modal, editor, and Notifications; properly grouping radio buttons with fieldset and legend elements; updating placeholder text contrast to meet WCAG standards; enhancing tooltips with hover persistence and ARIA labels; grouping related form controls; correcting labeling for filters in Manage Content; adding proper scope attributes to table headers in Manage Members; fixing invalid ARIA attributes in Inbox; and ensuring form error messages are properly announced by screen readers. Pre-Prod Rollout: October 25-26. Testing window open from Oct 27 through Nov 8. Production Rollout: November 10-11 The rollout will follow the standard maintenance windows.ViewsSign in to react to this postCommentsAbout Khoros Community: Aurora
Aurora is Khoros’ re-imagined Community experience that leverages more than 20 years of experience and learnings in the digital community space. Aurora delivers a sleek, modern, high-performance UX framework that adheres to community best practices while still giving brands complete flexibility to make changes or updates to address their specific needs. While built on the same platform as Khoros Community Classic, Aurora includes significant changes in the new framework: New member experience: Aurora delivers both better performance (load times, mobile-friendly pages) and design (modern UX, beautiful layouts, and pre-configured community best practices). Aurora also provides more personalization, integration with other digital properties through syndication, and an overall better experience so that communities can more easily become the heart of any brand’s digital experience. New community manager experience: Aurora enables community managers and designers to build and customize pages easier with a visual Page Template designer and control the look and feel of the community with pre-defined and customizable themes to ensure that your community reflects the visual message and tone of your brand. Moreover, you no longer need to know how to code to build these pages. New developer experience: Aurora improves the developer experience so your developers can more easily find, use, test, and extend any integrations, custom objects, or data calls (in and out of the community) to extend the capabilities of your community to do something new and provide your members with a more customized experience. Backend and Platform changes: Aurora uses new front-end technologies like React and Storybook and leverages tools like Jest and Typescript for rapid iteration and robust design. On the data side, Aurora uses GraphQL (replacing LiQL) as the way to program API interactions and get data out of the platform. Finally, the entire architecture is completely built on modern cloud services from AWS and Docker. When you’re ready to dive in, we recommend starting with one of our Getting Started Guides: Getting Started as a Community Manager Getting Started as a Community Administrator Getting Started as a Site Designer New to communities? Check out our Community Basics and take a tour of Aurora in this 1-hour video training course, which will help you familiarize yourself with key Aurora features and concepts. Moving to Aurora Since Aurora is built on the same backend data architecture as Community Classic, existing customers do not need to do a full-scale migration to move to Aurora. However, most Community Classic customers do have some customization on the front end and UI. For these customers, some additional work is required to move to Aurora. Review the Aurora Upgrade Playbook and reach out to your account manager to learn more about what to expect when migrating to Aurora. Related topics What's changed in Aurora from Community Classic Glossary of common Community Aurora termsViewsSign in to react to this postCommentsKhoros Communities 25.8 - Release Notes
The Khoros Communities 25.8 release includes several important security improvements and bug fixes. [Classic] Fixed a cross-site scripting (XSS) vulnerability affecting embedded YouTube videos on community pages. [Aurora] Certain specific custom access permissions was blocking user registration, due to attempting to verify permissions before the user was registered. This has been addressed so that permissions are checked in the correct sequence. [Aurora] Fixed an issue where users were unable to join Zoom meetings when registration was set to "required"; users would instead see an error message. [Aurora] Fixed an issue with headers and footers appearing multiple times on some community pages. [Aurora] Addressed an Aurora GraphQL API issue where certain custom fields were omitted from responses. These values now appear correctly. [Aurora] Resolved an issue where the "CurrentUser" endpoint returned information about the anonymous user, not the actual current user, when using the Authorization header method of authentication. Release Date: August 20, 2025ViewsSign in to react to this postCommentsWhat's changed in Aurora from Community Classic
This article captures some of the high-level changes (terminology, features, and concepts) that have changed (or will be changing) in Aurora from Community Classic. Terminology changes For Aurora, we have updated several terms that were previously used in Community Classic. Kudos are now called Likes. Subscriptions are now called Follows. Discussion Styles are now called Content Types. Content Types is the collective term used to describe the different types of boards community supports (forums, knowledge bases, blogs, etc.). Group Hubs are now called Groups. Tags and labels have been combined are now just all called Tags. There are two types of tags (preset and freeform). Tool changes and enhancements The site-building tool Studio has been replaced with Designer and Dev Tools. In Aurora Designer, you can edit your site’s Theme and manage Page Templates. In a future release, you'll also use this area to manage Email Templates and text strings. In the Dev Tools, you will find the tools needed to develop and customize your site. The Content Editor has been enhanced with several new features and meets accessibility requirements. Auto-save is enabled by default for all content types. Members have access to full version history of content with the ability to Delete, Edit, Compare, and Restore versions. Integration with Unsplash image libraries for Blog cover images and Page Template sections. Community Analytics is no longer a separate tool and now is built into the Community application. Where did it go? Not sure where something moved to? Here’s a list of some of the bigger things that have moved to a new place in Aurora: Admin Settings: Several of the settings pages have been simplified (or removed) and grouped differently. Settings pages that used to be in the “Community Admin” or “Admin” area are now available under Settings. Each card (tab) groups related settings into a new page. As we continue to build out more Aurora features, more cards/tabs will be added to the Settings area. Content Management Areas: Most content-related management tasks (find and edit drafts, review and manage reported abusive content, Spam Quarantine, and Moderation) are now performed from the Manage Content space: Developer Experience Aurora is built on the philosophy that internal and external developers should have access to the same development tools, empowering everyone involved with your community's user experience while providing a seamless, simple, and powerful SDK to help you get the most our of Khoros Communities. Why React? We chose React to power the web layer of our technology stack because of its ubiquitous nature and powerful built-in toolset. React, coupled with React Bootstrap, offers developers the ability to create powerful customizations to the user interface without losing out on the popular Bootstrap DLS that has been a part of the success of Khoros Communities over the years. Add the powerful Apollo Client state management library makes takes the communication between your React components and your community's data to the next level. It provides GraphQL call management, a catchable data store that monitors and responds to data updates. This update gives developers a better toolkit without taking away some of the most popular time-saving capabilities our developer community has come to appreciate. Why GraphQL? GraphQL is the query language for all of Aurora's APIs. This solution is consistent across our entire user interface, giving external developers the same backend experience we use to create Aurora's built-in features. REST API served us well in Khoros Communities for many years, but in Aurora, we wanted to give developers access to a more precise, flexible, and capable API to make data more accessible across the board. Where communities once relied on custom REST endpoints or multiple individual calls to retrieve necessary data, GraphQL can handle multiple operations at one time, and return only the data you need when you need it.ViewsSign in to react to this postComments
7.9KViews
6Comments
