About Aurora Email Notifications
As a community member, you receive email notifications for different types of activity across the community. To manage your email notification preferences, see Manage Follow and Notification preferences for your account. Email notification triggers Email notifications may be sent in a variety of situations. Some may require action while others may be purely informational. Below are descriptions of the notifications you may receive. More email notification types will be available in future releases. Community member notifications Content Workflow notifications Admin-only notifications Community member notifications Notification Description New Accepted Solution A post is marked as a solution on a topic a community member is following Accepted Solution Reminder Reminder to check answers on content and to mark applicable posts as solutions Answer Accepted as Solution A post is marked as a solution on a topic a community member created New Follow (Digest) Daily or weekly digest that provides updates from the community member’s followed content New Follow (Immediate) Immediate notification that provides updates based on the community member’s email notification settings Group Email Invitation Member or non-member is invited via email to join a Group Group Join Request Group owner is notified that someone has requested to join their closed Group Group Membership Accepted Community member is notified that they have been accepted into a Group Group Membership Denied Person is notified of being rejected entry into a Group. Group owners can add an optional description explaining the reason the person was rejected. Group Private Message Invitation Community member is invited to join a Group. They receive a private message invitation to join and an email notification for the new private message. New Private Message Community member receives a new private message in their Inbox Private Message Sent Admin is notified when a broadcast private message is delivered Private Community Invitation Person is invited to join the community by email and receives instructions on how to register via email New Like Community member receives a like on their content New Content Mention Community member’s content is mentioned by another user Member Mention Community member is mentioned by username by another person Email Address Change Confirmation Community member attempts to change their email address (non-SSO authentication) Forgot Password Community member begins the Forgot Password flow Confirm Registration When registered, community member confirms their email address in this notification to complete the registration process (non-SSO authentication) Email Verification Required to Publish Content Community member attempts to publish content when their email address is not verified Email Address Verification Community member requests the verification email to be resent Rank Change Community member achieves a new rank Event Email Invitation Member or non-member has been invited to an event Event Private Message Invitation Member or non-member is invited to an event. They receive a private message invitation and an email notification for the new private message. New Badge Community member is granted a new badge Content Workflow notifications Notification Description Edited Saved Draft Someone edited a saved draft in a place you follow. Submitted for Review Someone submitted a draft for review in a place you follow. Submitted for Publication Someone submitted a draft for publication in a place you follow. Recalled Draft Someone recalled a draft for publication in a place you follow. Schedule for Publication Someone scheduled a draft for publication in a place you follow. Return to Author Someone returned a draft to its author in a place you follow. Return for Review Someone returned a draft for review in a place you follow. Admin-only notifications Notification Description Abuse Report Notification Admin or moderator receives a report of abusive content, private messages, or member profiles. Related topics: About Notifications
Khoros Communities 25.9 - Release Notes
The Khoros Communities 25.09 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 windows
Khoros Communities - Updated Release Process
To improve your experience and simplify our release process, we are updating how we handle Khoros Communities releases. This process will start to apply from Communities Release 25.09. What's Changing Communities will have two types of releases going ahead - Standard releases and Patch releases Standard releases are regular releases that will happen on a cadence during Maintenance Windows. All releases will be standard releases Patch releases are critical bug fixes or security fixes, which happen out-of-band During Standard releases, our teams will automatically upgrade customers on the latest release providing windows for feedback Customers can reach out to support for upgrading legacy instances or for any other feedback Standard Releases We will have a standardized release process for both Aurora and Classic. In a standard release, we will auto-upgrade customers on the latest release. These releases will include features and non-critical bugs. 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. 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 , customers will be notified and have a week to provide feedback to their Customer Representatives on the upcoming release. After this one week, we will upgrade the stage environments. We will open a two-week testing window, where customers can test on their stage environments and provide feedback. Again, Customer Representatives will be the points of contact during this phase. At the end of the two-week window, we will perform the upgrade in production for customers whose stage environments we have successfully upgraded and do not have any open feedback. For both stage and production, we will use existing Maintenance windows, as we expect downtime. If you are on an older version and want to opt back into auto-upgrades, please reach out to your Customer Representative. They can upgrade you to the latest version at any time Patch Releases We will release patches out-of-band for critical bugs that affect multiple customers or affect a release's stability, and security and vulnerability fixes. We will apply patch releases for all customers on the latest version, given that these are critical in nature. Our team will publish the release notes, notify customers and apply patches in a three-day window. Customer Representatives will handle any customer feedback during this phase. 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. Customer support will notify customers about downtime needs. Customer representatives will reach out if a patch applies to a Customer on an older version. As always, Customer Representatives are available for any feedback. What to expect next As we stabilize and 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.Aurora: Recent Content widget configuration
The Recent Content widget displays the most recent items from blogs, knowledge bases, forums, ideas, and/or events within your community. It can be configured with different layouts, a specified number of items, and a variety of other elements. Layouts The layouts included for the Recent Content widget are Detailed list, List, and Card. From the Edit Widget panel, select any of these options to change the layout. Each layout has its own set of unique options available. Detailed list The Detailed list layout features a smaller thumbnail accompanied by the item's title, various elements, and a preview of its content. List Card Configuration Options List style The available List style options for Detailed list and List include: Space: Uses whitespace to create space between items. Divide: Adds a horizontal line to divide items. Border: Creates a border that separates items into individual boxes. Title The Title sets the title that appears at the top of the widget. If the Visible only to screen readers toggle is enabled, the title remains hidden to most visitors; however, the title information is still relayed to visitors using screen readers. Scope The Scope field enables you to select where the widget is scoped. You can scope to the community, a category, a group, or a specific board. If you select a specific board, the Content types to include drop-down menu becomes inactive. Content Types to Include Use the Content Types to Include drop-down menu to select the type(s) of content types to display in the widget. Options include: All (All content types) Blogs only Knowledge Bases only Discussions only Ideas only Sort You can set the default Sort By filter to one of the following options: Newest topics Most recent (applies only to top-level posts and replies, not nested replies) Detailed list Options The available sort options for the Detailed list layout depend on the state of the Show additional filter/sort tabs toggle. If deactivated, you can set the default Sort By filter to one of the options listed in the previous section. Below Sort and filter options, you can also turn on Show filter and sort controls to add a Tagged line where members can click + Tag to enter a tag to filter content by that tag. If, however, the Show additional filter/sort tabs toggle is active, you can configure the different sort options available to visitors through tabs that appear on the top of the widget. These include: Sort by Most Viewed Sort by Most Liked Sort by Most Replies Filter by Newest Topics Filter by Most Recent Filter by Items with No Replies Yet Number of Items The Number of items slider gives you control over the number of items displayed on the initial page load before a Show More option appears. List item/Card elements Elements are additional pieces of information that can be displayed along with each item in the widget. The list of available elements changes depending on which layout you've selected. Detailed list and List layouts have an additional Lead with drop-down menu. It enables you to choose to display the item author's Avatar, discussion style Icon, or None along with the item in the widget. More options Additional options are available at the bottom of the Edit Widget panel. Hide if empty hides any tabs that don't have corresponding items. Include "Show More" link adds a link to the bottom of the widget to enable visitors to display additional items once the Number of items has been reached.Khoros 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, 2025Aurora: Publish blog posts
When a blog post is reviewed and approved to be published, there are two possible scenarios for publication: It is ready to be published and you can go ahead and publish it. It requires a precipitating event, such as a product release or update, and needs to be published at a later date. To publish blog posts immediately, click the Publish button. The blog post is immediately available for viewers to read. Scheduling content to be published later The scheduling feature gives you control in managing when your blog post is published in the community. This makes it possible to manage your growing inventory of content. When scheduling at a future time, you can also indicate the time zone to use. Follow the walkthrough below to learn how to schedule a blog post for publication. Note: If Content Workflow is enabled, you must submit the blog post for review and submit for publication before you can select Schedule for Publication. Note: The tutorial below depicts publication scheduling when Content Workflow is turned off. 14 STEPS 1. Open the draft of the article that you want to schedule to publish. Click Edit Draft 2. The article opens in an editor. Scroll down the page and click Publication Schedule 3. Click the text box to choose the time 4. Pick a date 5. Pick a time 6. Pick a Time Zone 7. 8. Click Schedule 9. Your article is now scheduled to be published 10. Click Change if you want to reschedule 11. Select a date, time and timezone 12. Click Change 13. Click Remove, if you want to remove the scheduling 14. The schedule is removed. Here's an interactive tutorial https://www.iorad.com/player/2052286/Schedule-Publiation Permissions Permission Purpose Additional permissions required Publish posts To publish edits to previously published KB articles View draft articles Edit any published post To edit your own blog posts and blog posts published by others View draft posts Related topics: Create a blog post Edit blog posts Follow Content TagsAurora: Configure Registration and Sign-In settings
The Account & Privacy page contains settings related to registration, sign-in, and sign-out. This article covers registration and sign-in settings. To learn about configuring SSO options, see Configure SSO settings for the community. Registration settings All anonymous users must register to participate in the community. To register, they must enter mandatory fields such as Username, Password, and so on. By default, the Registration window includes these fields: Admins and members with appropriate permissions can enable or disable these registration fields from the Settings page as needed. To edit registration settings: Sign in to the community as an Admin. Open the Account menu and click Settings. Go to System > Account & Privacy. Go to the Registration section and turn on/off these options: Enable member registration: Turns on or off the community member self-registration flow. By default, this option is enabled. This option is turned off for private and invite-only communities, where anonymous users are not allowed to register in the community. Add date of birth field to registration page: Controls whether the Date of Birth field appears on the Register window. Use Date of Birth to enforce the minimum age requirement: Toggle on this option to validate the date of birth provided by the user against the minimum age required for registration. Require users to confirm that they meet the minimum age requirement: Toggle on this option to add a field on the Registration window for the users to confirm whether they meet the minimum age required for registration. Set the Minimum age required for registration. As per the Children’s Online Privacy Protection (COPPA) rule, users must be at least 13 years old to register to the community. Auto-assign role upon registration: If you want to automatically assign a role to a new member when they register, click Edit by this option. In the field on the window, enter the role you want new members to be assigned. Terms of service acceptance required: Toggle on this option to add a field on the Registration window for the users to read and accept the Terms of Service (TOS). You can turn off this option if Single Sign-On (SSO) is used and you already have TOS acceptance as a requirement in the SSO configuration. Also, Admins can View/Edit Terms of Service in the required language. Learn more about editing the Terms of Service for the community. When all the options are turned on, the Register window looks like this: Sign-in Settings To edit sign-in settings: Sign in to the community as an Admin. Open the Account menu and click Settings. Go to System > Account & Privacy. Go to the Sign in section and turn on or off the Keep me signed in setting. When you turn on this setting, the Sign In window has the Keep me signed in checkbox selected by default for the member signing in.Khoros Communities v25.04-b16 - Release Notes
Khoros Communities v25.04-b16 is a minor update that adds a Chinese (Traditional) language pack for Taiwan (zh-TW). This is a full user interface translation. There are no functionality changes included in this release. We are planning upcoming releases during August, with important bug fixes and enhancements. Release date: 2025-07-23 (release notes delayed)Aurora: Review content reported by content filters
Community content filters identify inappropriate words used in community content and take appropriate actions on the content based on how you’ve configured the filters to behave. Any posts and replies, private messages, profile information, tags, and registration flow that are flagged by the content filters are sent to the Abuse tab, where you can periodically review and take actions on them. If you have been granted the appropriate permissions, you can view the content reported by content filters from the Abuse tab: The tab lists: Title: Title of the content reported by content filters Author: Member who created the content Date Reported: The date on which the content was reported Filter: The name of the content filter that reported the content Filter action: The filter action applied on the content. The filter actions can be Do not allow, Replace term, Check inline HTML and do not allow, and Take no action. Learn more about content filters. To review and filter reported content, view the below walkthrough: 10 STEPS 1. Sign in to the community as a Moderator. 2. Open the Account menu and go to Manage > Abuse. 3. From the Abuse tab, click Filters. 4. In Reported By, select Content Filter. 5. Now, you can view the list of content reported by content filters. 6. Using Actions, you can filter the content based on the content filter actions applied to them. Let's select Replaced. 7. Using Found In, you can filter based on content types. Let's select Blogs. 8. You can further filter the list based on Filter Name, Keyword, and Author. 9. The Abuse tab is updated based on the applied filters. 10. That's it. You're done. Here's an interactive tutorial https://www.iorad.com/player/2224500/Review-content-reported-by-content-filters Based on the content type and filter action, you can take these moderator actions: Content Type Filter Action Moderator actions on the content Forum discussions/Blog posts/Knowledge Base articles/Replies/Ideas/Events Replace term/None (Take no action) Edit Mark as Spam Confirm Abuse Ignore Report Ban Member Forum discussions/ Blog posts/Knowledge Base articles/Replies and Private Messages/Ideas/Events Blocked/HTML Blocked (Do not allow/Check Inline HTML and do not allow) Ignore Report Ban Member User Registration None (Take no action) Ignore Report Ban Member User Signups Blocked / HTML Blocked (Do not allow / Inline do not allow) Ignore Report Edit posts reported by content filters After reviewing the posts reported by content filters, you can edit the posts that are inappropriate and do not adhere to the community principles. While editing content, you must be careful not to modify the context of the content that the author of the post is trying to convey. To edit a post, open the Options menu on the post and click Edit. Mark posts reported by content filters as spam While reviewing the posts reported by content filters, you might find the content as spam. You can mark these posts as spam. After you mark the post as spam, the post is removed from the community and moved to the Spam management tab. Learn more about Spam management. From the Abuse tab, you can mark reported posts as spam in these ways: Open the Options menu on the post and click Mark as Spam. Click the post from the list to review and Mark as spam. Confirm posts reported by content filters as abuse After reviewing the reported posts, you can confirm them as abusive messages. When you confirm the abuse, the posts are removed from the community and this list, and are moved to the Moderation tab in the Rejected filter where moderators can review and take necessary actions. From the Abuse tab, you can confirm abuse in these ways: Open the Options menu and click Confirm Abuse. Click the post from the list to review and Confirm Abuse. Ignore content reported by content filters From the Abuse tab, you can ignore the content reported by content filters after reviewing them so that you or other moderators do not re-evaluate them. When you ignore a report, the content is removed from this list. From the Abuse tab, you can ignore a report in these ways: Open the Options menu and click Ignore Report Click the content from the list to review and Ignore. Ban members from the Community After reviewing the reported content, you can ban members who are abusive in nature. This helps to avoid malicious behaviors across the community. Learn more about banning members from the community. From the Abuse tab, you can ban members abuse in these ways: Open the Options menu and click Ban member. Click the post to review and Ban Member.Aurora: View support cases in the community
In the community, the Case Portal lists all the cases that are created by members via different channels (phone, email, Facebook, and/or the community). The Case Portal option must be enabled in the Salesforce settings to view the support cases. Members with the Read and reply to own support cases permission can access the Case Portal to view their own support cases: The page lists: Case No.: The unique identification numbers for each case. Title: The titles for each case. Status: The current status of each case. Origin: The source through which the cases were created. Created On: The date on which each case was created. Last Update: The date on which each case was last updated. You can sort the cases based on Last Update. You can further filter cases based on View, Keyword, Status, and Origin: To view support cases in the Case Portal: Open the Account menu and click My Support Cases. Note that you must have the Read and reply to own support cases permission to view this option. The Case Portal page opens. To view the details of a case, click the Title of the case. The case details page opens. From the case details page, you can update or close your case. You can also reply to your own cases: Related topics: Create a support case in the Community Update or close support cases from the Community Set case portal permissions
