Aurora: Use keyboard shortcuts and Markdown to work faster
While creating or editing community content, you can make use of keyboard shortcuts and keyboard navigation to work faster and more efficiently. The Content Editor also supports Markdown. Markdown is a plain text formatting syntax commonly used by writers and programmers to write quickly without having to take time using the RTE toolbar options. For example, to bold a word, like “Dishes," you can type **Dishes** instead of having to highlight the text and click the Bold icon in the editing toolbar. In other example, to insert an emoji, you can type colon (:) along with the emoji name and select the required emoji from the search results: While creating or editing any content, you can refer to the Editor Help for assistance using these tools. View the Editor Help by clicking the Options icon > Help in the toolbar. Note: The Editor Help recognizes if you are using a Mac or Windows machine and displays the appropriate keyboard shortcuts and commands. The Editor Help provides the information about these aspects: Shortcuts: Use keyboard shortcuts to quickly apply standard text and paragraph formatting (for example, bold, italics, paragraph headers) to your content. Keyboard Navigation: Describes how you can navigate community pages using the keyboard instead of a mouse to meet accessibility requirements. Markdown syntax: Lists the markdown syntaxes you can use while writing the content instead of formatting the text using toolbar options. For example, to apply Heading 1 while starting a paragraph to a word - “Content Editor” you can type # Content Editor instead of having to highlight the text and click the Heading 1 option in the editing toolbar. Similarly, you can use other markdown syntaxes to format the content. Let’s look at an example where you want to refer to the Editor Help while creating a discussion. To view the Editor Help, Check out the below walkthrough: 11 STEPS 1. Go to the board where you want to create a discussion and click Start a Discussion. 2. The editor window opens. 3. Enter the Title of the discussion. 4. Enter the content for your discussion. 5. To view the Editor Help, click the Options icon > Help. 6. By default, the Editor Help window is displayed with the Shortcuts tab. 7. To view accessibility information, click Keyboard Navigation. 8. To view the list of Markdown syntaxes, click Markdown Syntax. 9. Close this window. 10. Click Publish. 11. The discussion is successfully published. Here's an interactive tutorial ** Best experienced in Full Screen (click the icon in the top right corner before you begin) ** https://www.iorad.com/player/2173528/View-the-Editor-Help
Aurora Product Coaching Session: Spam Management Best Practices
Khoros Communities platform offers several settings and features that allow you to mitigate Spam in your community. Join our Spam Management Best Practices coaching session to identify, filter and deal with spam effectively. Our coaching session will guide you through the practical tips and techniques to help combat spam and help maintain the hygiene of your community. Topics covered in the coaching session Overview of Aurora spam settings and functionality Manage Content dashboard related to spam management and its features Using roles and ranks to configure permissions to check spammers Content Filters Best practice tips Notes - Admin permissions are required to conduct the call. 👉Click here to Sign Up Related Resources Enable Spam Management Community Spam Management Review Posts Captured as Spam Khoros Academy: Communities Moderation Essentials Khoros Academy Instructor Led Training: Spam Management for Communities AuroraAurora: Send reminder notifications for events
The Events reminder feature automatically sends an email reminder before the start of an event to all attendees' registered email addresses. This reminder is sent exclusively to those members who have responded that they will attend the event. To set this notification, go to Settings > Features > Event and edit the Send event reminder (minutes) option. By default, this is set to send reminder emails to all attendees 30 minutes before the event starts. This notification is sent to the attendee’s registered email address.Aurora: Configure custom Salesforce settings
The Khoros Community integration package leverages custom Salesforce settings, which are used by many components and relates to the Khoros Community configuration settings on Salesforce. To apply settings for your Khoros environment: Sign in to your Salesforce.com environment. From the dropdown on the top right of the page, select App as "Khoros Salesforce Integration." Select the Custom Settings tab. Go to the Feature Settings tab. Select Create. Enter the Feature Settings: Feature Setting Name: Default is "DefaultSetting." Do not change this setting, as it is non-editable in newer packages. Create New Contact record: Select this option to enable the creation of a new Contact during user sync if a Contact with the matching email ID is not present. During User Sync, Contact and Community users are linked together. The linkage is necessary for Case Portal functionality. (You must enable the Community User Trigger below for this setting to work.) Link Community User with Contacts: Select this option to allow linking of Community user and Contact during user synchronization, if a contact with same email ID already exists. The linkage is necessary for Case Portal functionality. (You must enable the Community User Trigger below for this setting to work.) Case closure: Select this option to allow automatic case closure when a comment on a post is accepted as solution on community. (You must enable the Case Trigger below for this setting to work.) Max Allowed Private Message Subject Length: Sets the maximum length the Private Message subject (up to 43 characters). Max Allowed Private Message Body Length: Sets the maximum length the Private Message body. No of Federated Search Results from Salesforce: Limits the number of Federated Search results (applies to Salesforce results only). Default value is 100 (Package 4.1 onwards). Enable Community User Trigger: Select this option to enable Community User Trigger. This trigger runs on community user creation/update and links community users with contacts. This linkage is necessary for Case Portal and User Sync functionality. Enable Case Trigger: Turns on or off triggers on cases, which synchronize case status changes with community and also mark a case as closed. Enable Case Comment Emails: Toggle Case Comment email on and off. (Package 3.7 onwards) (Optional) Fallback Community Username: Enter username of the Community user to which postbacks should fall back to when a Community user is not found corresponding to the email address of the user replying. This is also used in case of multiple users with the same email address. Entered Community user should be a valid value. (Package 4.0 onwards) Allow Case Comments for public Community Cases: Select this option to enable the creation of Case Comment on Public Community Cases in Salesforce. (Comment does not sync to community.) If not selected, it does not allow case comment creation for public community cases in Salesforce. (Upcoming, Package 4.2 onwards) Note: The Enable Knowledge and Lightning Knowledge options must be turned off as they are not supported in the community. These options allow knowledge base articles to be created, updated, deleted, and searched from the community. Select Save. Configure your remote site access. Set profile permissions: Go to Setup > Manage Users > Profile. Select the profile used for integration. Ensure the appropriate Field Level Security Permissions are granted for Standard and custom objects (Account, Case, Contact, Postback Comment, Community Users, Private Message). The recommendation is to grant the administrator role so that members can have read/write access to all fields for objects that are required for integration to work. Go to Custom Settings > Community Settings > Create. Enter community settings details (If you are using v4.3 connector version, go to step 12 instead). Community ID: The ID of the integrated application. Contact your CSM or Support to get this value for your community. Client ID: The Client ID of the SalesforceIntegration API App on the community (Admin > Dev Tools > API Apps). This is configured from <link to these instructions - https://docs.google.com/document/d/1MuDPjcuO2hPjFPzlXfktjO8tkWr3xhjysgsHZJSo-BI/edit?tab=t.0#heading=h.bfd4q6thij1w ) Secret: The Secret corresponding to the Client ID. Redirect URL: The URL of the VisualForce page for Custom Settings. Base URL: The community base URL. For subpath-enabled communities, append the subpath. Is Proxy Enabled?: Always select this for Aurora applications. Context Name: Tapestry Context name/Webserver char path. Example: t5/s. Authorize the connection. After saving, the connection status shows Not Active. Select Authorize. You are redirected to the authentication window. Select Authorize. You are redirected to the authentication window. Note: Authorize with an Administrator or a member with admin-like permissions to prevent API call failures. After successful authentication, you are redirected to the custom settings page with the message "TenantId: is successfully authorized." The Connection Status updates to Active. The Username field displays the username used for authorization. This generates Access and Refresh tokens, and they are stored in a Salesforce object. Note: When the access token expires, the Connection status changes to Halted. A "RefreshAuthToken" link appears. You can always re-authorize by selecting the Authorize link. By default, the refresh token expiry of the salesforceIntegrationApp is set to 5 years. If you are using v4.3, then enter the Community Settings as shown below (If you are using v4.4, skip this step): Community Id: Enter your community ID. (You can get your ID from your Customer Success Manager, if you don't have it. If you've already entered this information, select Edit.) Username: Enter the Khoros username to be used in Khoros API calls. Note: This user must be a non-SSO user with administrator permissions, and the email address for this user must be verified in the community. If an agent has an account on the target community that uses the same email address as their Salesforce account, their personal community user account is used as the author of the postback. We recommend that your brand's Salesforce agents create their own community accounts for this purpose. Password: Enter the Khoros password associated with the above username. Base URL: Enter the Base URL value according to your Khoros environment (see below). Note: Be sure to include the https:// and HT credentials. Use the following format: https://<HTUSER>:<HTPASSWORD>@<***Community URL> Example: https://test123:qwerty98765@community-stage.khoros.com/ Select the Is Proxy Enabled? checkbox. Context Name: Set Context Name to “t5" unless your Community has a Reverse Proxy implementation in place, in which case, contact your Customer Success Manager or Khoros Support and request the value of tapestry.context.name from your community config. Select Save. To set the maximum number of search results to be returned in the Federated Search component, go to the Feature Settings tab and set the No. of Federated Search value. Select Save. With HT-Access turned off in the Khoros community: Khoros Communities Stage Base URL Sandbox https:// [community_id].stage.lithium.com Production https:// [community_id].lithium.com Note: If you have a more descriptive CNAME/vanity address for your community, use that name when creating the URL (for example, https://community.mycwebaddress.com). With HT-Access turned on in the Khoros community: Note: Contact Support to get the ht-access credentials for your community. Contact your Customer Success Manager to get your Community ID. Khoros Community Stage Base URL (Example with community id as “abc”) Sandbox https://htusername:htpassword@abc.stage.lithium.com Production https://htusername:htpassword@abc.lithium.comAurora: Enable emojis
Aurora supports use of emojis in content by default. You can toggle emoji support on and off by going to Settings > Features > Emojis. Emojis can be turned on or off at the community level only. You can also choose which emoji character sets are available in the content editor. To add or remove different emoji character set categories, click Edit to the right of Emoji categories, select the categories you want to use, and click Save. Also, you can add or remove emojis of a specific category by expanding the category. Note: The Custom categories is not yet supported in Aurora. This will be available in a future release. The emoji picker updates to reflect your selections. Here, you can see the addition of the Travel & Places category in the emoji picker. Learn more about the Aurora Content Editor.About Aurora Content Types
Khoros Communities excel at connecting people, building relationships with product experts, and driving brand engagement. Of course, at the heart of any community is the content, and Khoros Community provides several Content Types your members can participate in. But which content type should you use? Each content type is designed for different types of content and drives different types of community engagement: Forums: Connect product experts and brand enthusiasts through peer-to-peer discussions. Blogs: Attract customers by publishing content from top experts. Blogs are one of the best ways to build your audience and keep your community informed. Knowledge bases: Empower customers and employees to turn peer-generated conversations and knowledge from Aurora Communities into polished, searchable articles. Events: Events are a collection of community-hosted activities (seminars, meet-ups, conferences). You can notify community members of online or in-person events by publishing them in the Events calendar. Ideas: Crowd-source innovation by enabling customers to submit ideas, vote, and provide comments. Generate thousands of prioritized ideas that help you build better products and deepen customer loyalty. Groups: Groups deliver an enhanced experience for community members to engage around a common theme or purpose. Each group has its own configurable set of content types (the content types shown in this article) to organize content and communication. Forums Khoros Forums enable you to connect product experts and brand enthusiasts through peer-to-peer discussions. Both newbies and experienced members can read, post, and easily respond. You can create forums that are as broad or as focused as you need for your products or services. For example, you could have a forum dedicated to an entire product line of printers or forums focused on a specific printer. It’s up to you. Check out Atlas Community’s Discussion Forum Learn more about forums. Blogs Blogs drive traffic to your community. Unlike standalone blog products, Khoros Blogs is integrated with our community platform, ensuring a cohesive experience as users explore and learn. Blogs are a great way to publish content pertaining to your brand, be it product announcements, industry expertise, or news and events. Check out Atlas Community’s Developer Blog where experts share information and recommendations based on products and labels. Learn more about blogs. Knowledge Bases With Khoros knowledge bases (or KBs), members can create trusted content focused on specific topics or themes. For example, you might have KBs focused on product documentation, support FAQs, best practices, or use cases. You can enable specific members to write and maintain these articles as well as enable trusted community members to contribute to these articles. Check out Atlas Community’s Support Information Knowledge Base articles shared and curated by Khoros experts in an efficient and organized way. Learn more about knowledge bases. Events Events provide a platform to schedule, announce, inform, and discuss everything from the smallest group gathering to the largest user conference. These community-hosted activities harness the enthusiasm generated by interactions between your customers, company, and brand ambassadors and foster deeper connections with your customers. With Khoros Events you can: host live Stream Video outside your community (for example, from YouTube, Facebook, or Vimeo) by providing a URL of the live video. You can also provide the URL of a pre-recorded video. integrate Zoom meetings and webinars within your community. Learn more about Events. Ideas From time to time, your customers might have ideas about how to make your products better. These ideas could be minor enhancements or a completely new feature. Khoros Ideas enables you to capture these customer ideas, let other members vote on these ideas, and share these ideas with your internal product teams. By enabling members to submit their own ideas, you are encouraging them to be thought partners with your company and stand out among their community peers. Submitted ideas are reviewed by your internal teams and assigned statuses (for example, Under consideration, Accepted, or Declined) so everyone in the community can track the idea’s progress, vote on ideas they like, and even discuss the ideas by posting comments. Learn more about Ideas. Groups Within a community, smaller communities form organically or out of necessity. Groups help you to create, organise and scope these conversations to the right audience so that the conversation remains relevant and insightful, enabling customers to say what they want to say, how they want to say. With Khoros' Groups you can have Open, Closed and Hidden Groups. With Open Groups, you provide access to all community members to read and comment on the content in the Group although only owners of the Group can create content . Closed and Hidden Groups take privacy a step further. Non-members of Closed Group can see that a Group exits but only members can read, comment or reply. Hidden Groups are completely invisible to the community except for its members. Use Hidden Groups when you need confidentiality, security and privileged access to information is need, yet you need right members to easily access right content. Learn more about Groups Related topics: About Community site structure Set permissions at the board level
