Khoros Communities: Aurora 25.03 Release Notes
The Khoros Communities: Aurora v25.03 Release introduces performance improvements, several new permissions, the ability to download your case list, moderation enhancements, post activity limit updates, improvements to the developer experience, and many bug fixes to improve the member experience.Flood controls for Aurora communities
With Khoros, there are limits on how often people are allowed to post, upload images, videos, and attachments, tag content, send private messages, and other community actions before triggering activity limits. Activity limits are in place to help combat potential spam. Note: Those with the Administrator and Moderator role are exempt from activity limit restrictions; these thresholds affect only regular members. The following table lists the default activity rate settings for various actions performed by the member within a specified period of time. Actions Activity Limits Post content A member can't post more than: 5 posts in 30 seconds 15 posts in 10 minutes 50 posts in an hour Send Private Messages A member can't send more than: 5 private message in 30 seconds 15 private messages in 10 minutes 50 private messages in an hour Upload Images A member can't upload more than: 100 images at a time 5000 images per day 5000 images in the community Upload Videos A member can’t upload more than 500 videos in the community. Upload Attachments Members can’t upload more than 100 attachments per post per day. Like content A member can't give more than: 50 likes per minute 500 likes per hour 5000 likes per day Tag content A member can’t add more than: 50 tags per minute 500 tags per hour 5000 tags per day Mention people A member can’t mention more than 50 members in single post. Related topics: Activity limitsAurora: Filter the Analytics Dashboard
Aurora Analytics enables you to filter data for more granular insights. You can filter based on: Roles Ranks New Topics Username Thread ID To add filters to your dashboard: Open the Account menu and select Analytics. On the dashboard page, select + Filter. Select a filter. Enter relevant values to filter. Select Add. The dashboard displays data for the selected filter. Let's look at an example of filtering data for specific roles. Assume that you want to view metrics and activities by Administrators for the "Products" category in your community for the last 30 days. To filter for this data: Change the scope to Products. Set the date range to Last 30 days. Select +Filter. Select Roles. Select Administrator from the menu. Select Add. The Dashboard displays metrics and activities by Administrators for the "Products" category for the last 30 days. Thread ID You can use this filter to view the metrics related to a particular thread or topic in your community. The Thread ID is the ID found at the end of the community URL. For example, in the below URL, "236502" is the Thread ID for a topic in the community: https://community.khoros.com/kb/supportinformation/khoros-cookies-datasheet-community-care-marketing-khoros-bot/236502 You can add this filter under Dashboard and Reports by selecting the Filter option. You can add more than one Thread ID to the filter. After you select Add, the dashboard displays the metrics for the added Thread IDs or, in other words, the topics with those Thread IDs. Related topics: About Dashboard Settings Scope Analytics data to specific place in the community Set date ranges and data comparison time frame for Aurora Analytics Dashboard Set the Trending Discussions options for Aurora Dashboard View metrics by content type Aurora Analytics Metric DefinitionsAurora: Enable languages in your community
From Designer, you can define which languages are used in your community. You can also set which language to use by default. English is set as the default language for all new communities. To enable additional languages in your community: Open the Account menu and go to Designer > Community Text. In the row of Enabled languages, select Edit. Use the Add language drop-down menu to select languages you want to be available in your community. Enabled languages list above the Add language menu. Select Remove beside a language in that list to remove languages you no longer need. (Optional) If you want to set a language other than English as the default, in the row of that language in the Enabled languages list, select Set as Default. Select Save. Related topics: About Aurora community languagesAurora: Enable content moderation and set content moderation defaults
Community moderators review and process large volumes of member-generated content. Moderation is an important part of keeping a community a safe and engaging space for your members to participate. Depending on how you configure the moderation settings, content can also be auto-approved and skip the moderation process. The moderation process depends on the defaults you set for various boards. Admins can set these moderation defaults for forum discussions and replies, blog comments, ideas and their comments, event and event comments, media, and knowledge base comments at the community, category, and board levels. Auto-approved: The content is auto-approved and made public without going through moderation review unless flagged. Recommended for trusted areas that are self-regulated by a small group of members. Selective: The content is made public to the community without going through moderation. However, moderators can selectively review this content later, and based on the review, the content stays or is removed from the community. Required: The content must go through moderation for review, and based on the moderator's evaluation, the content is either published or removed from the community. By default, Selective moderation is set for all boards. Understanding the different moderation types Before configuring the content moderation defaults, you must understand the benefits and risks of each option: Auto-approved: Set Auto-approved for places that are designed for open discussions without any need for regulating the content posted by members. Use this option in places that are self-regulated by a small group of members who are accountable for their actions. However, we still recommend you implement the moderation process within the community to avoid spreading inappropriate information. Selective: Similar to Auto-approved, the Selective moderation process also encourages open communication among members in that they can publish content immediately without prior review. Moderators can still review the published content to ensure the posted content is appropriate and adheres to the community’s principles. Use this option in places where members expect fast-paced and live interaction without having to wait long for the moderation process to complete. However, when moderation is delayed, there is the potential risk of inappropriate content (abuse or spam) being posted that impacts readers and disrupts the community. Compared to the Required moderation process, this process is less effective in avoiding spam and abusive content. Required: Required moderation is the best way to combat spam and abusive content because the content is sent to the moderation before it’s made public in the community. This also protects your community’s reputation and creates a safe space for your members by ensuring the appropriate content is posted in the community. However, this process relies on additional resources to review the content, which may delay making the content public. This can disappoint members who want their content to be made public quickly. Set content moderation defaults at community level Sign in to the community as an Admin. Open the Account menu and go to Settings > Features. Select Moderation. The Moderation Types settings displays spam and content moderation settings. Here, you can set default moderation types for discussions, ideas, replies or comments on discussions, blog posts, knowledge base articles, events, and media. The screenshot below displays the Moderation Types, numbered for clarity. Select Edit for any of these options. A window to edit the moderation type opens. From here, you can: assign the moderation type for all members override this setting for specific roles with another moderation type value specify the roles that will bypass moderation The following is an example for moderating discussions and replies. The Community moderation type field for discussions and replies by all members fall under the Selective moderation type, and they are made public but go through moderation process. The Role-based Override field is set to Required for the roles selected in the Apply only to the following roles field. Discussions and replies by members with these roles are hidden until reviewed and approved by a moderator. The roles added to the Exclude Roles field automatically bypasses any moderation action. Similarly, you can set default statuses for other content types at the community level. Set content moderation defaults at category, group, or board levels The Moderation Types set at the community level are inherited to the category, group, and board levels. You can override these options at various levels as needed. Based on the inheritance, the settings applied at different levels are inherited to child places from their parent levels. For example, the content moderation defaults set at category or group levels are inherited to their child places. Learn more about setting inheritance. Let’s look at an example in which you want to set content moderation defaults at category level. To set content moderation defaults at category level: Open the Account menu and go to Settings > Community Structure. On the Community Structure page, select the category where you want to set the content moderation defaults. In the category settings, go to the Moderation section and set Content moderation types for content review as required. When you’ve adjusted a setting for a child place, a PARENT OVERRIDE indicator is displayed next to that setting for the child place to indicate that it overrides the settings of its parent. Similarly, you can set content moderation defaults at the group and board levels. Based on these board-level settings, when members post content on the community, the content is immediately routed to the Moderation for review. When a board is set to Required moderation and members post content on this board, a confirmation message is displayed on the post indicating that post will be published as soon as it is approved from moderators: From the Moderation tab, moderators can review content for appropriateness. They can then approve or reject it, and also message authors of the posts. Learn more about moderating content. Note: it is not possible to set different moderation levels for comments(or replies) and main posts Grant permissions to moderate content Moderation permissions should be granted only to roles assigned to trusted individuals. To manage this permission: Navigate to Admin > Settings > Users > Roles and Permissions. In the row of the role for which you want to manage this permission, select the Options menu and then Edit. In the Permissions area, below Moderation, locate Moderate Content. Select Grant or Deny as required.About Aurora Notifications
When you receive an in-app notification, a dot appears over the Notifications bell icon in the header anywhere in the community. Click this icon to see a list of your notifications. You receive notifications for a variety of reasons around the community: New activity on content you follow (including Category, Board, Content, and Tag follows) Activity and updates on your content: Likes Solutions Mentions (Members and Content) Ranks Badges Related topics: Manage Follow and Notifications preferences for your account About Email NotificationsAurora: View the history of published content
Over time, content posted to the community can change as different people edit the content. These changes can be subtle or complete rewrites of the original content. Sometimes, changes get made that are not correct or need to be reverted to an earlier iteration of the content. Aurora gives you the ability to track the changes in every version of a blog post or knowledge base article from its draft state up through its current published state. Each time you publish a KB article or blog post, the major version number is incremented (v1.0, v2.0, and so on). For example, in v1.0, 1 is the major version number and 0 is the minor version number. The minor version number is always zero for a published article. Each time you edit and save a published article, the major version number remains the same as the current version number and the minor version number is incremented (v2.1, 2.2, and so on). For every version, you can see who made the change and what was changed. Let's look at an example of the version history for a knowledge base article. To view the history of revisions: Go to the KB article page. Click History. The revision history of the article displays in a popup window: The published version gets an incremental version number (v1.0, V2.0, v3.0, …) From the Version History view, you can: view the revision notes that were added while editing the article. Compare the versions of the article. Edit and restore any older version of the article. Permissions View history of blog posts and knowledge base articles Set the permission View edit history under Settings > Roles and Permissions > Content to allow members to view and compare different versions of blog posts and knowledge base articles.
