AshaC
Khoros Alumni (Retired)
Joined 6 years ago
User Profile
User Widgets
Contributions
Audit Read, Update, and Delete (CRUD) actions
Administrators can have a comprehensive audit logging for all Create, Read, Update, and Delete (CRUD) actions on KB Guides. The following actions will be recorded in the audit log: Guides: Added, moved, deleted, and reordered Chapters: Added, moved, deleted, and reordered within/to Guides Articles: Added, moved, deleted, and reordered within/to chapters or Guides Additionally, audit logs will cover actions taken on Manually-sorted articles, including: Adding Articles Clearing the List Reordering Articles You can access the audit logs from Settings > System > Audit logs Related topics: About KB Guides Adding KB Guides Guides widget configuration General actions on KB Guides, Chapters, and Articles431ViewsSign in to react to this post0CommentsAbout Aurora Analytics
To have a successful community, you need to know what’s working and what needs improvement. Aurora provides a robust set of analytics so you can get actionable insights to drive traffic and member engagement. You can determine what kinds of content needs improvement, what your members steer away from, and what they want more of from your community. These metrics help you learn where your members come from, what type of content they engage with, and where to focus on to reach new people. Having clear data enables you to plan towards community goals and make informed decisions to change course when things aren’t working. Aurora Analytics provides visual dashboards and interactive reports to provide you with high-level and detailed data on how your community is performing. Note: Currently, users can see the metrics up to the previous day in Aurora Analytics.. Data is reported in Coordinated Universal Time (UTC). Accessing Aurora Analytics To access Aurora Analytics, open your Account menu and click Analytics. Note: Members must have an Admin or Analytics role to access Aurora Analytics From the Analytics page, you can access Dashboard and Reports. The Dashboard provides you with an “at-a-glance” view of the activities that best indicate the overall health of your community and member engagement across your community. You can customize Dashboard settings to your requirements and get the most out of your data analysis. Reports present you with key metrics on content, boards, categories, and members in a tabular format. Related topics: Accessing Analytics Dashboard Dashboard Settings Aurora Analytics Metric Definitions Aurora Analytics Reports Refer to the Khoros Communities Analytics Essentials course for training on Communities Analytics.ViewsSign in to react to this postCommentsAurora: Getting started as a Community Analyst
Welcome to Aurora! This introduction guides you through the most commonly used features specific to various tasks you can perform as a community analyst, linking each of them to articles on how you can use the Aurora Analytics to achieve these tasks. Measuring the data, tracking your success, and using it to prove how your community is advancing the organization’s broader initiatives will give your community a strong strategic footing. Your primary task as a Community Analyst is to prove your online community’s engagement and value with strong data. Before you begin You need to work with the Community Managers to have a thorough understanding of your community requirements: What are your organization’s goals? What are your team’s goals? What are your community’s goals? Once you have answered these questions, you come up with the Key Performance Indicators (KPIs) to measure against these goals. KPIs represent how your community is performing against strategic goals. So, the KPIs must be relevant to the business and community goals. Choose only those few KPIs that will help move your business forward. For example, the KPIs to increase revenue or increase retention or increase loyalty, and so on. You track and measure these KPIs with benchmarks for each at launch, six months later, nine months after, one year, and so on. Tracking KPIs in this fashion helps you make changes, as necessary, to meet your company’s vision. While KPIs represent how you’re performing against strategic goals, metrics are your “business as usual” measures that still add value to your organization but aren’t the critical measure you need to achieve. Every KPI is a metric, but not every metric is a KPI. Example: Let's say Increase in Customer Engagement is one of the identified KPIs. To measure this, you need various metrics, like Monthly Active Users (MUA) that tracks the number of unique users who visit your community over some period of time and Daily Active Users (DAU) that tracks the total number of people who open and engage with your community in a given day. The DAU to MAU ratio is a useful metric to measure the stickiness of your community. Also, if you see that MUA has dropped since last month, you have something to investigate. Whatever is your goal in hand for business or for the organization, you’ll need to figure out a way in advance how you plan to calculate where you are standing now and how you will achieve the goal. Khoros Community Analytics helps you measure and improve the performance of your community by gaining insights into your community's health. Through a unique combination of performance metrics and web analytics, we offer the deepest insights into customer engagement across your community. Khoros Community Analytics The Khoros Community Analytics dashboard collects data and displays metrics for your community. Note: You must have the Access Reports in Community Analytics permission to access the Khoros Community Analytics dashboard. Getting Started Getting around Khoros Community Analytics to familiarize yourself with each section on the dashboard Enable and access Community Analytics on how to use the dashboard Accessing, downloading and scheduling different reports to understDownloadand the different community metrics you can view Community Analytics metric definitions Viewing data for specific dates Apply filters to Community Analytics reports Schedule Community Analytics reports to be emailed to you Manage scheduled reports Download or schedule member-related reports Engagement drilldown data for different content types Ideas specific reports Khoros Academy Khoros Communities Analytics Essentials courseViewsSign in to react to this postCommentsKhoros Communities: Aurora 25.04 Release Notes
Member Experience Performance optimizations In this release, members will notice the following performance improvements: GraphQL query optimization: We've improved the performance of GraphQL queries by optimizing how they are processed, resulting in faster load times and reduced overhead. Text key reusability: We've streamlined how text is managed across components, reducing duplication and improving consistency throughout the platform. Improved page stability: We've made changes to improve page stability and reduce layout shifts, ensuring a smoother and more visually stable experience. Faster load times: We've enhanced caching for commonly used data, making frequently accessed pages load faster. Better experience for guest users: We've optimized the experience for users who aren't signed in by ensuring only necessary data is loaded, improving performance and responsiveness. Muting conversations in the Inbox Community members can now mute conversations in their inboxes to avoid receiving notifications for them. This can be useful if there is an extensive conversation occurring and a member does not need to view every update but may still need to reference the conversation. In your Inbox, you can mute or unmute a conversation by opening the Options menu for the desired message. To learn more about muting conversations, see About Inbox privacy. Calendar Invitation Email on Event RSVP Previously, members had to manually add the ICS file to their calendars. With this release, when you RSVP an event with Attending or Interested, a calendar invitation is automatically added to the calendar associated with your registered email address. The following screenshot shows an event that is automatically added to the member’s calendar. Learn more about adding events to your calendar. Additional Embedly support We've enhanced Embedly integration in the community to support additional content types. You can now embed and preview the content from following platforms directly within posts and comments: Typeform Vidyard Loom For Vidyard and Loom videos, members can either play the video directly within the community, after accepting cookies, or choose to view it on the provider’s native platform. The following screenshot shows a banner that prompts members to accept cookies or continue to the external site. Note: To enable previews for these types of content, make sure both External Link Previews is turned on under Settings > Content Features > Links. Learn more about managing external link previews and warnings and adding rich text previews. View history option Previously, members could view edit history only for blog posts and knowledge base articles. With this release, this capability extends to all content types—including replies and comments. Members with the View edit history permission can now see changes made to any post, giving you greater control and transparency over content edits. The following screenshot shows the History option available for an idea. Learn more on how to view and compare different versions of published content. Tags autosuggest Previously, tag suggestions appeared only after you started typing in the tag field. Now, when you select + Add Tags, a list of relevant tags—both preset and freeform—immediately appears, relevant to the board you're posting on. Read more on tags. Admin Experience Community Experience Surveys Admins can enable community experience surveys, which prompt members to provide feedback about their experience in the community. Survey responses and scores can be collected via an export. Creating a survey requires several configuration steps, including: designing the branding: select naming, logos, and colors designing its behavior: select who to present the survey to, when, and how often selecting its questions: select which questions to present to your visitors turning it on for visitors: easily toggle your survey on when you’re ready to go live—and easily turn it off To access survey configuration options, go to Settings > Content Features > Community Experience Survey. To view specific setup steps for customer experience surveys, refer to Create community experience surveys. To export your survey result data, in Content Features > Community Experience Survey > Questions and Answers, select Export (refer to View community experience survey results). Designer: removal of page-load time option As of this release, the Optimize page-load time option previously available in More options on widgets is no longer available because enabling it had a negative impact on the CLS (Cumulative Layout Shift) Web Vitals metric. If you still want to use this option, a developer can modify the quilt directly in the plugin. Widgets that were set to use this option prior to this release will also continue to respect that selection. Designer: logo navigation menu In previous releases, we introduced the ability to add navigation text links and side menu navigation links. With this release, you can now add a drop-down navigation menu from the logo in your community. This is a prime location for adding links to your main categories to make it easy for your members to navigate to the most important areas of your community. Refer to Header and Footer configuration for steps on adding navigation links to your header. Move and merge content across content types Duplicate content and evolving conversations are common in the community. Sometimes, a discussion is better suited to a different content type.For example, a community Discussion might be valuable as a knowledge base article. Similarly, an active Discussion might align better with an existing Idea in development. To maintain continuity and preserve valuable conversations, it should be easy to move or merge content between content types without losing context.To support this, we've introduced the ability Move content from one content type to any other content type Merge a Discussion or Idea as a reply or comment to any other post Following is a screenshot of the options you receive when you try to move content to any other content type. By moving content from one content type to another, you have the flexibility to consolidate similar posts and reclassify content when its purpose changes - like turning a discussion into an idea. While moving content, prompts will inform you of any potential metadata loss during conversion. By merging posts, you can bring similar content or conversions to one place in the community. Merged posts retain all replies, and prompts will inform you of any potential metadata loss during conversion. Learn more about moving and merging content. Automatic spam detection for images Starting this release, all images along with the text content will be scanned for automatic spam detection. Hyperlinking content in private messages In Aurora Communities v25.03, we introduced the Turn on link hyperlinking permission. This allows members with the permission enabled to post URLs that automatically appear as clickable hyperlinks. For those with the permission set to Deny, URLs are displayed as plain text. With this release, we’ve extended the same functionality to Private messages, ensuring consistent behavior across public and private interactions. Learn more about Content permissions in About Content permissions. External link warning settings Previously, to generate previews for external URLs, you had to enable Rich text preview under Settings > Content Features > Rich Content. With the upcoming support for Embedly, we've updated how this works. You’ll now find two separate settings under Settings > Content Features > Links: External link previews – Toggle on to generate rich previews for external URLs, allowing members to see linked content directly within the community. External link warning – Toggle on to show a confirmation message when members select a link that leads them outside the community. These changes give you more control over how external content is handled and displayed. Developer Experience Previewing local changes on the SDK Staging site In this latest update, we are excited to introduce a new feature that allows users to preview the SDK staging site from the perspective of various user roles. This functionality is designed to help developers and stakeholders understand how the changes will appear to multiple user types before going live. Non-admin/Anonymous Admin Moderator Standard See Previewing Local Changes as Different User in the Staging Site for more information. Move Content across content types As discussed in Move and Merge content across content types, we also provide GQL support to move content across different content types or discussion styles. In Khoros Communities Aurora, members have already been able to move replies either to a new post or under an existing one. However, merging duplicate root posts — whether forums or ideas — was a missing piece. With the release of the Merge Root Posts feature, community managers and moderators can now easily consolidate similar or duplicate topics into a single root post. This enhancement simplifies content organization, improves community navigation, and reduces redundant discussions. See Merging Root Posts in Khoros Communities Aurora for more information. Migrating from REST API to GraphQL With Aurora, we are transitioning to a GraphQL framework for APIs. While REST APIs are still supported in Classic, we strongly recommend adopting GraphQL for all new components, endpoints, and integrations in Aurora. Our long-term strategy is to phase out REST APIs in favor of GraphQL. Although we have not announced a sunset date yet, GraphQL is where we are focusing all new development and enhancements. We encourage all customers upgrading to Aurora to begin transitioning as early as possible. Early adoption will help ensure a smoother and more efficient migration experience in the future. See Migrating from REST API to GraphQL for more information. Custom Field Access Control We've created a new guide detailing the ins and outs of controlling access to Custom Field data within your Community. This includes configuring custom fields for specific roles and node levels, including how to set up and scope custom field visibility. See Configuring Custom Field Visibility for more information. GraphQL Support for Page Scripts You can now add GraphQL Queries and Fragments to Page Scripts and run them via the Page Script Handlebars Templates. This is a huge advantage for use cases such as personalized survey popup that enables you to dynamically render the name of the user as part of the popup to encourage engagement among members. We've detailed this use case, including an example workflow in GraphQL Calls for Page Scripts. Handlebar Templates for Salesforce Integration Notification Emails In addition to the email notification fix in the 25.03 release, we added handlebar templates for the Salesforce integration notification email to let members know when the integration fails. You Found It. We Fixed It. Accessibility Added "Filter by" to the ARIA label for the tags filter on the search results page to improve screen reader accessibility. Spotlight Search results are now read out by screen readers. All buttons on an event page are announced successfully by screenreaders. Analytics The accuracy of visit-related metrics has been restored—communities no longer significantly underreport visits due to issues with different visitors sharing the same visitor ID. APIs Group invitations no longer require grouphub:example formatting in the nodeId field when sent via a GraphQL mutation. The node ID now behaves as it does for any other node. Admins can now perform an SQL update and rollback of a site of the report ID column. Members can now migrate any content or content with widgets from Community Classic to Community Aurora using GraphQL API. Members can now delete a forum, blog, or KB post via GraphQL API calls. When you retrieve the full number of net likes and the member’s likes count via GraphQL, they are now consistent and match correctly as per the member’s action. Badges The avatar_changed metrics for badge criteria now reflect “true” and “false” instead of a number of times. The badge requirement for the number of videos uploaded now increments as expected. Counts Hovering your cursor over a specific note in the Admin notes now shows the absolute date and time of creation of that note. The Places widget shows the correct count for unread posts. CWA The Schedule to publish button is visible when blog posts are turned off for comments. Designer The image upload maximum size settings in Designer are no longer tied to the max upload settings set in admin, so admins now experience an error when uploading a banner in Designer only if they attempt to upload an image of 20 MB or larger. If the Hide category in place widgets, place picker menus, and search setting (under the Display settings of a category)is enabled for a category or board, it still appears in the list for assigning custom page templates. Follow and notifications When you update the Advanced Settings in your Follow and Notification settings, they now save as expected. Ideas Anonymous or non-authenticated users can no longer vote for ideas. Languages and localization You can now remove English as an available language for your community so that your community is available in the language of your choice. Chinese localization text files no longer break custom components. Member profile The member profile page now shows the correct count for Likes received. All members, irrespective of their role, can now view their profile information. Navigation Anonymous users are redirected to the login page when they try to access the URL of a draft. Selecting Submit for Review for blog posts or knowledge base articles, correctly redirects to the preview page. When you select the browser’s back button when you are on the Notification feed page, you are redirected to the previous page you visited and not stay on the same page. On the Header & Footer template, in the Edit Navigation panel, the Show bottom border and Show bottom shadow options now save correctly and appear appropriately in preview mode. Topic links on the All Topics page now redirects you to the correct page. Private messages When an admin uses the Switch Member option and sends a private message, the message is now sent from the member they switched to instead of from the admin. Selecting an @mention in a private message redirects to the right content, place or member profile. All links added to private messages are now visible as links. RTE Anchor tags added in source code are now visible as links. Search and SEO Requests to community vanity URLs are now correctly redirected, resolving issues that may have impacted SEO traffic. URLs with .tsx extensions are no longer exposed to search engines, preventing 404 errors on Google search console and protecting SEO performance. The Show more links on search results page now load content correctly on mobile devices. Autosuggestions now work for search queries containing special characters in non-English languages. Tags The tag list populates automatically when you attempt to add a tag to content that was moved to a board requiring tags.ViewsSign in to react to this postCommentsKhoros Communities: Classic 25.04 Release Notes
You Found It. We Fixed It. A fix was backported to address a security vulnerability that previously allowed users to add dest_url as a URL parameter in their posts to redirect those who clicked the URL to any website. If you have any questions, contact Khoros Support. For posts with emojis, the emojis are now retained as expected even after the post is edited and published again.ViewsSign in to react to this postCommentsAurora: Merge content types
In active communities, it's common for standalone discussions to overlap with existing knowledge base content. Sometimes, a question or conversation in the forum is better positioned as a follow-up to an article that already addresses the topic. To streamline content and avoid duplication, you can merge a discussion into a knowledge base article as a reply. This keeps related information together, helps future readers find complete context in one place, and makes the knowledge base more dynamic and community-informed. This article covers how to merge content and metadata lost after the merge. Note: You can merge only discussions and ideas as a reply or comment to posts of any other content type post. Blog posts, knowledge base articles, and events cannot be merged as comments or replies to posts of another content type. Merge content Let’s see an example of how a discussion is merged as a comment on a knowledge base article. The following screenshot shows a discussion in a forum called “UX writers Forum” with 2 replies. The following screenshot shows an article in a knowledge base called “UX writer KB” with 2 comments. To merge the discussion to the knowledge base article: On the discussion page, open the Options menu. Select Move. A window opens where you can select to move or merge. Select Merge as a reply to an existing post of any content type. Select Continue. A window opens where you can choose the destination of this discussion. You receive a prompt informing you of the metadata lost after you merge this content. (Optional) If you want to notify the author of the discussion about moving it, select Author of this post checkbox. (Optional) If you want to notify the members who replied to this discussion about moving it, select Members who replied to this post checkbox. (Optional) If you want to notify the author of the destination post, select Author of the destination post checkbox. (Optional) If you want to notify all members who participated (replied or gave Likes) to the destination post, select All participants in the destination post checkbox. Select Move. The discussion has been added as comments under the article. There are now 5 comments in total—2 were already part of the article, and 3 come from the moved discussion, including 2 of its replies. Metadata loss after merge Below are the details of what metadata is lost when a content type is merged to a board of a different content type. Source Destination post Metadata lost Discussions Any content type Tags and SEO related details Ideas Any content type Tags, idea status, status comments, and SEO related detailsViewsSign in to react to this postCommentsAurora: Move post to different content types
Duplicate content and evolving conversations are common in the community. Sometimes, a discussion is better suited to a different content type. For example, a topic originally planned as an event might work better as a forum discussion if participants are spread across time zones. Likewise, an active discussion could evolve into an event for real-time engagement. To maintain continuity and preserve valuable conversations, you can move content between formats without losing context. This article covers how to move content and metadata lost after the move. Move content The following is an example of moving a discussion to an idea. The discussion is in a forum board called “UX writers Forum” and has 2 replies and 1 Like. On the discussion page, open the Options menu. Select Move. A window opens where you can select to move or merge the content. Select Move to a different board of any content type. Select Continue. A window opens where you can choose the destination of this discussion. In the Destination field, select a place in the community. In our example, we choose an idea board called “UX writer Ideas.” (Optional) If you want to notify the author of the discussion about moving it, select Author of this post checkbox. (Optional) If you want to notify the members who replied to this discussion about moving it, select Members who replied to this post checkbox. Select Move. You receive a success message. The discussion is now an idea on the selected idea board. Existing likes display as votes, and the two replies appear as comments on the idea. Similarly, you can move any content type to a board of any other content type. While moving, some of the metadata belonging to the original post is lost. This information is shown to you as a prompt before the content is moved. For example, as shown in the following screenshot, when you move an idea to a forum (or a board of another content type) the idea-specific details like status and status comments are lost. Meta data loss after move Below are the details of the metadata that is lost when a content type is moved to a board of a different content type. Source Destination board Metadata lost Blog posts Knowledge base board Cover image Blog posts Any content type board other than knowledge base board cover image, co-authors, introduction, blog post summary, and history Discussions Any content type board N/A Events Any content type board Type of event, start and end date, video URL, location, and featured guests Ideas Any content type board other than Ideas board Status and status comments KB article Blogs board Contributors KB article Any content type board other than Blogs board Contributors, introduction, article summary, and historyViewsSign in to react to this postCommentsAurora: 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 published content of any content type, including replies and comments. For example, 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. Select 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 Set the permission View edit history under Settings > Roles and Permissions > Content to allow members to view and compare different versions of posts any content type or replies or comments.ViewsSign in to react to this postCommentsAdd Rich Text Preview
You can generate previews for external URLs and preview content within the community itself using the Rich Text Preview option. These URLs must be from a supported Embedly provider. Here’s a short guide on how you can preview a CodePen URL (a supported Embedly provider) before you publish your content. Note: We have taken security measures to prevent the previewed content from generating pop-ups, downloading content, and uploading forms. We provide Embedly support in the Community to include the following content: Typeform Vidyard: You can play the videos either in the community by accepting cookies or play on the video provider’s native platform. As shown in the following screenshot, you receive a banner asking you to accept the use of cookies or play it on the provider’s platform. The screenshot below shows that the video can be played within the community after you grant the video provider permission to use your browser’s cookies. Loom: Similarly, you can add Loom videos. You can play the videos either in the community by accepting cookies or play on the video provider’s native platform. As shown in the following screenshot, you receive a banner asking you to accept the use of cookies or play it on the provider’s platform. After you accept to drop cookies you can play the video in the community. Note: To include the above mentioned videos, you must enable the External link previews and External link warning settings. Learn more about these settings.ViewsSign in to react to this postCommentsManaging external link previews and warnings
To improve content visibility and user build trust, you can configure how external links behave in your community using two dedicated settings: External link previews: Toggle on to generate rich previews for external URLs, allowing members to see linked content directly within the community. External link warning: Toggle on to show a confirmation message when members select a link that leads them outside the community. To enable Rich text preview: Open the Account menu. Go to Settings > Content Features > Links. Toggle on External link previews. Toggle on External link warning. Learn how to add Rich text previews.ViewsSign in to react to this postComments
431Views
0Comments
