Aurora: 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 TagsAbout 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 NotificationsAurora: 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.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 permissionsAbout the Aurora Case Portal
After you set up the Salesforce integration with your community, you can activate the Case Portal within the community. The Case Portal enables members to: Create Support Cases directly from the community. Correspond with Support agents on cases via case comments in the community. Cases can be discussed in public and private areas of the community. Access their open and resolved cases from a private community page regardless of where that case originated. For example, you might have created several support cases via different channels (phone, email, Facebook, and/or the community). The Case Portal enables you to access and respond to all of your cases regardless of how they were originally opened. In the Case Portal, all the interactions between the Support agent and the user are captured in threaded conversations. To enable Case Portal for your instance, open a Support ticket. After the Case Portal is enabled in your community, you can set it up by performing these tasks: Enable and configure the Case Portal in Community Admin Set up Case Portal permissionsAbout 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.About Aurora Moderation
It is important for your community to be a positive space where members feel welcome, safe, and engaged. To foster this environment, moderators constantly monitor community activity by reviewing content for appropriateness, based on the guidelines you’ve put in place for your community. Using the Moderation tab in the Manage Content dashboard, moderators can quickly review and process large volumes of member-generated content. Depending on how you’ve set up your moderation process, content can be reviewed either before or after it is published to the community. From the Moderation tab, you can moderate forum discussion posts and their replies, ideas and their comments, as well as comments on blogs, knowledge bases, and events. Also, you can view the posts or private messages that are rejected as spam, abuse, or for other reasons and take further action on these posts or private messages. Moderation process You can set the moderation mode at the board level. Required: Moderators must moderate content to make it available in the community. (This was previously known as pre-moderation in Communities Classic.) Selective: The content is published, but moderators can moderate it after publication. (This was previously known as post-moderation in Communities Classic.) Auto-approved: Content does not require moderation and is approved automatically. Learn more about configuring moderation modes for various content types. When members post content on the community, the content is immediately routed to the Moderation, based on the moderation settings for that board. Note: 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: View Moderation tab Members with elevated permissions (Admins and Moderators) can access the Moderation tab in the Manage Content dashboard. Note that you must enable content moderation at the community level to view the Moderation tab. Members will see the Spam, Abuse, and Moderation tabs. The Moderation tab is where you can review content. By default, the Moderation tab is displayed with the list of unmoderated posts, where the Moderation status is set to unmoderated. The Moderation tab lists: Title: title of the post, reply, or comment Author: authors of the posts and replies Date: the date on which the post or reply is sent for moderation. Status: the publication status (Published or Unpublished) of the posts and replies. Number of views, likes, and comments for each post, reply, or comment. Note: You can sort this list based on the Date. From the Moderation tab, moderators can evaluate the posts and replies. approve or reject posts and replies message authors about their content. ban members When approved, posts are published in the community or remain in the community based on the moderation settings at board level. They are then removed from the Moderation tab. When rejected, the posts are removed from the community. The posts that are rejected as spam can also be viewed in the Spam tab. Learn more about approving or rejecting posts sent for moderation. To view the rejected posts or private messages, go to Filters and set Moderation Status as Rejected. From the Moderation tab, you can: Open any post to view the content Search and filter posts Approve or reject posts Message members on moderation actions about their posts Review the posts or private messages that have been rejected as Spam, Abuse, or other reasons Ban members Refer to the Khoros Communities Moderation Essentials course for training on this feature.About Aurora roles and permissions
Your community uses permissions to determine the actions that your community members can take and which community areas and features they can access. Instead of setting each of these permissions manually, permission settings are grouped into roles and then you can assign these roles to members. Khoros provides a set of default roles. You can modify these roles (although we don’t recommend it) and create your own roles. You can also create a relationship between your community ranks and roles so that members get new roles and receive additional permissions as they advance through the ranks. Each role has a setting for each permission. When you define a role, you can set some permissions directly and leave the default settings for the rest. After you define your roles, you can set up the ranks in your community to assign (and remove) roles when members change ranks. The higher the rank, the more access it’s likely to grant the member. In addition to controlling member access within a community, you can also use roles to gather metrics on community usage or to establish criteria for gaining a rank. Although it’s more common to use a rank to grant a role, you can also use a role to assign users a rank. Some communities use this technique, for example, to assign a special rank to community moderators by using a role as the criteria for granting a rank. Similarly, you may want to create a role specifically for your employees. They might have the same permission settings as other community members, but you can use a special employee role as the requirement for a corresponding rank to identify them as employees to the rest of the community. Note: Groups use the default community roles as well as a set of roles specific to groups. Learn more in Group roles and permissions. Related topics: Create a role Default Community roles Permission descriptions Add members to roles Best practices: roles and permissions You can also receive self-paced training on roles and permissions in our Build Khoros Communities course.About the Aurora Theme editor
The Theme editor in Aurora Designer enables you to customize the appearance of your community site to match the look and feel of your brand. With Theme, you can configure the page layout, set the size and style of your fonts, manage colors, manage icons, configure buttons and text links, manage avatars, and manage UI elements for your community site content (Blogs, Forums, Knowledge Bases, Ideas, Events, and Groups). After you have customized your community theme, click Publish to make them live on your site instantly. The Theme editor is separated into the following categories: Basics Fonts Colors Buttons and Text Links Avatars UI Elements Refer to the Build Khoros Communities course for training on site design.
