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: Assign roles to members in bulk via CSV file import
To assign or remove a large number of roles for members at one time, you can use bulk import via a CSV file. Your CSV file needs to include the following for each member: “ADD” or “REMOVE” indicator Username or email address The roles you want added or removed To bulk assign or remove roles: Go to the Settings > Roles and Permissions page. In the Community Roles area, click Assign Roles in Bulk. On the Assign Roles in Bulk window, browse for the CSV file on your local machine. In the Charset drop-down menu, select the character encoding of the CSV file you’re importing. The default for Microsoft Windows operating systems is windows-1252 for most locales saved through Microsoft Excel. Click Start Assignment. Larger sets of member assignments may take longer to be imported. When the import is complete, you receive an email indicating whether it was a success or if there were any errors that need to be corrected. Related topics: Create a role Add members to roles
Aurora Product Coaching Session: Approaching Analytics in Aurora
Join our Classic to Aurora Analytics migratory coaching session to unlock the full potential of your community data. This session will guide you through practical applications of Aurora Analytics, from high-level overviews to detailed report analysis. Our coaching session will provide you with the knowledge and skills to effectively leverage Aurora Analytics for informed decision-making and community growth. Topics covered in the coaching session A detailed walkthrough of Aurora Analytics, based on real-world insights. A comparison of Aurora Analytics versus Classic Analytics, highlighting key changes and new features. Practical use cases demonstrating how to apply Aurora Analytics to your day-to-day work. Notes - Admin or analyst-level access to Aurora Analytics is recommended to conduct the call. 👉Click here to Sign Up Resources:- About Aurora Analytics Filter the Analytics Dashboard Aurora Analytics Dashboard Use Cases Khoros Academy Learning Path: Communities (Aurora) Analyst Level 1 Khoros Academy Learning Path: Communities (Aurora) Analyst Level 2Aurora: Manage image and video settings and permissions
Manage image settings Permissions Members must have the Add images to post permission to upload images. Members with this permission can add images to community content. To enable this permission for specific roles: Go to Settings > Users > Roles and permissions. Open the options menu (3 dots menu) for the role you want to grant this permission to. Select Media. Select the type of permission for the Add images to post permission as needed. To enable this permission for all members in the community: Go to Settings > Users > Roles and permissions. Scroll up the page and Edit for Community Permission Defaults. Select Media. Select the type of permission for the Add images to post permission as needed. Note: We recommend that you grant this permission only to trusted members to combat spam. Configure video settings To enable and configure image-related settings for your community: Go to Settings > Content Features. Select Media. Turn on Image uploads to enable members to add images to their content. In the Additional image settings section, select Edit to set the maximum file size (in MB) for uploaded images. Select Save. To override the setting to upload images lower-level categories or boards: Navigate to the desired place in the place picker. Scroll to the Media section under Content Features. Turn on or off Image uploads as needed. Supported file formats For Ranks, Aurora supports these image formats: .png and .svg For all other images, Aurora supports these image formats: .png, .jpg, .jpeg, .gif Manage video settings Note: Videos uploaded to a Khoros community are hosted by Brightcove. Learn more about the Brightcove video hosting service. Permissions Members must have the following permission to upload videos. Members with this permission can add videos to community content and messages. To enable this permission for specific roles: Go to Settings > Users > Roles and permissions. Open the options menu (3 dots menu) for the role you want to grant this permission to. Select Media. Select the type of permission for the Add videos permission as needed. To enable this permission for all members in the community: Go to Settings > Users > Roles and permissions. Scroll up the page and Edit for Community Permission Defaults. Select Media. Select the type of permission for the Add videos permission as needed. Note: We recommend that you grant this permission only to trusted members to combat spam. Configure video settings To enable and configure video-related settings for your community: Go to Settings > Content Features. Select Media. Turn on Video uploads to enable members to add images to their content. Select Edit to set the maximum file size (in MB) for uploaded videos. Turn on or off the ability to embed externally-hosted video content. Select Save. To override the setting to upload videos at lower-level categories or boards: Navigate to the desired place in the place picker. Scroll to the Media section under Content Features. Turn Video uploads and Embed external videos on or off as needed. Bypass media moderation You can grant trusted members or roles with trusted members the permission to bypass moderation for the media content they publish in the community. Learn more on how to grant this permission.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. To configure these activity limits, contact the Support team.About Aurora badge rules and supported criteria
For each community badge you want to create, you must define the rule that determines how a member achieves or receives the badge. For simpler rules, you can use the built-in tool that enables you to select a criterion and additional qualifiers. However, if you want a more complex rule for a badge, you can use the Advanced Editor to enter badge formulas. Badge formulas include a combination of a formula clause type, a keyword, an operator, and a value. When the calculation of a value in a formula returns a true result, the member achieves the badge. The badge achievement is then reflected in their profile and badges page. To create more complex badge rule expressions that require multiple rules be met before awarding a badge, you can use the “AND” operator. Common use cases for badges with multiple rule criteria include profile completion tasks and more complex engagement options. For example, you may want to award a “VIP Contributor” badge to members who: Have received at least 100 likes Have had at least 25 answers marked as Accepted Solutions Have posted at least 10 blog articles Tip: You can also use community roles as an additional requirement for any badges based on activity. By taking advantage of the “unlocking” game dynamic, you can set certain badges to be earnable only after a community member has reached a rank that grants them the required role. Create a complex badge rule Go to Settings > Users > Badges. To add a rule to a badge in an existing badge set, click the name of the badge set that contains the desired badge and then click Add Badge. Otherwise, create a new badge set where you want the badge with complex rules to live (see Create badge sets and badges). After entering the badge Name, Description, and Icon, in the Criteria drop-down menu, select Advanced Editor. In the Advanced Editor field, enter your custom badge rules. Enter each rule you want met (making sure that each rule has an identifier, operator, and value). Enter AND between each rule. Select the Hide from member profile until earned checkbox to ensure that the badge is displayed on member profiles only when the rules are met. Click Add Badge. Let’s say you want to create a badge for new members to encourage them to begin participating in the community. You might create a rule like this: metric.net_overall_threads >= 5 AND metric.net_kudos_weight_received >= 20 AND metric.net_accepted_solutions >= 3 This complex rule may be great for a badge that rewards users for creating new content with great quality. Feel free to use this example for your own community! Note: You cannot create complex rules with OR or NOT. Supported badge clauses and badge criteria A badge formula can include one of five types of clauses depending on the type of behavior you want to reward. You can chain rules together to create complex criteria using these clause types: Metric: Assigns a badge based on the value of a specific community activity recorded for each member. Member in role: Assigns a badge to a set of members based on community-level roles. User ID in set: Assigns a badge to a manually specified set of members based on their numeric user ID. This should be reserved for awarding rare badges to a small group of members. Non-Default profile setting value: Assigns badges based on members changing the default state of a specific setting or profile field on their member profiles. Specific profile setting value: Assigns badges based on the member changing a setting in their profile to a specific value. (For example, you could award a badge when a member sets their profile language to French.) Clause Type Clause Format (variables in bold) Metric metric.name_of_metric >= number Example: metric.net_accepted_solutions >= 1 Roles user.role.name in ['role'] Example: user.role.name in ['Administrator', 'Khoros'] User ID user.id in [id] Example: user.id in [10, 2, 5] Non-default profile setting setting.setting_key != 'default' Example: setting.profile.location != 'default' Profile setting value setting.setting_key = '[value]' Example: setting.profile.location = 'Argentina' Rewarding user activity using metrics For definitions of exactly what these metrics are, refer to these Aurora Analytics Metrics Definitions. The following member activity metrics are supported for use in a badge formula using the format: metric.name_of_metric >= [number] Accepted Solutions metric.net_accepted_solutions All Content Types metric.net_overall_posts metric.net_overall_replies metric.net_overall_threads Blogs metric.net_blog_articles metric.net_blog_comments metric.net_blog_posts Forums metric.net_posts metric.net_threads metric.net_replies Ideas metric.net_idea_threads metric.net_idea_comments metric.net_idea_posts Images and video metric.image_upload_count metric.video_upload_complete_count Likes metric.net_kudos_weight_given metric.net_kudos_weight_received Message views metric.message_views Sign-ins metric.logins KBs metric.net_published_tkb_articles metric.net_tkb_comments Rewarding specific members You can award badges to a specific group of members based on their role or user ID. Since you can’t edit a rule after you create the badge, we recommend using roles as the basis of your rule criteria. That way, if you need to add or remove members later, you can modify the member list for the role independent of the badge rule criteria. Important: If you want members to be notified (via email or real-time notifications) of a role-based badge, you must roll out the badge first and then add the role for that member. If the member already has the role before the badge is published, the member will not be notified. Keep in mind: Newly created badges are automatically applied to all members who already match the criteria, resulting in email notifications being sent out to community members depending on your badge notification settings. You need to coordinate such badge releases with Khoros to avoid a surge of emails being sent out to the community members, which can impact your community performance. Use single quotes around the role name. Use commas if you enter more than one. For example, to award a badge to all members with the “Admin” or “Moderator” role, enter this rule criterion: user.role.name in [‘Admin’, ‘Moderator’] You should use "user ID in set" in badge criteria only if you have a static, unchanging list of specific members. This clause type should be used only in special cases to award badges for one-time achievements. Otherwise, you’ll need to delete and recreate the badge each time you want to add another member’s user ID to the rule. Use commas if you enter more than one. For this case, use this format: user.id in [10,2,5] Rewarding profile completion You can use the profile setting below to create badges that reward members for filling out more information about themselves in their profile. These settings can all be used with the "Non-default profile settings" clause. Profile setting identifier Setting name Setting location setting.profile.name_first First Name My Settings > Personal setting.profile.name_last Last Name My Settings > Personal setting.profile.location Location My Settings > Personal setting.profile.biography Bio My Settings > Personal > Bio setting.profile.url_homepage Personal Site My Settings > Personal avatar_changed Note: To award a badge when a member changes their default avatar image, use this syntax: avatar_changed = true Avatar My Settings > Personal > Edit Rewarding date-based activity You can award badges based on date-based activities. Setting identifier Setting options Examples consecutive sign-ins number setting.user.max_consecutive_logins >= 2 registration_date date registration_date > "2015-01-01" (see supported syntax options below) time_since_registration time value in days, months, or years time_since_registration >= "1 years" signin_date date signin_date > "2015-01-01" (see supported syntax options below) About sign-in related activity We store a counter of the number of days in a row and the last sign-in time. When someone signs in, we get the date of the last increment and the date of today, and we count the days between. If < 1, we ignore it (so no gaming the system). If == 1, we increment the day counter. If > 1, we set the day counter to 0. About entering dates You can enter dates (which must be in quotes) in all formats supported by ISO 8061: Year: YYYY (eg 1997) Year and month: YYYY-MM (eg 1997-07) Complete date: YYYY-MM-DD (eg 1997-07-16) Complete date plus hours and minutes: YYYY-MM-DDThh:mmTZD (eg 1997-07-16T19:20+01:00) Complete date plus hours, minutes and seconds: YYYY-MM-DDThh:mm:ssTZD (eg 1997-07-16T19:20:30+01:00) Complete date plus hours, minutes, seconds and a decimal fraction of a second YYYY-MM-DDThh:mm:ss.sTZD (eg 1997-07-16T19:20:30.45+01:00) where: YYYY = four-digit year MM = two-digit month (01=January, etc.) DD = two-digit day of month (01 through 31) hh = two digits of hour (00 through 23) (am/pm NOT allowed) mm = two digits of minute (00 through 59) ss = two digits of second (00 through 59) s = one or more digits representing a decimal fraction of a second TZD = time zone designator (Z or +hh:mm or -hh:mm) Note: When an ISO 8601 date doesn't specify a time zone, it is considered to represent local time. We do not override the local time zone for this purpose, so the date is parsed from the badge clause based on the server's local time zone. So that will differ depending on the AWS region: US-West-2 (PST) EU-West-1 (CET) To prevent confusion on the Internet, date strings (for example, in badge clauses) may specify a time zone. Related topics: About Badges and Badge sets Create badge sets and badges Feature badge sets on the member profile Delete badge sets and badges Example badge sets and badges View badges from the member profileAbout 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: Ban members from the community
Each member plays a crucial role in the community's growth and is responsible to behave appropriately to create a positive space where other members feel welcome, safe, and engaged. But in some cases, members act maliciously, violate the community guidelines, or are abusive in nature. To avoid such malicious behaviors in the community, Moderators and members with appropriate permissions can ban these members and prevent them from accessing the community. Before banning a member, consider their member history, not just a single action or post. You can temporarily or permanently ban members based on the impact caused. You can ban members using their profile information (username, user ID, and email address) and IP addresses. Use IP address bans as a last resort. IP addresses tend to be dynamic and if a banned member restarts their router, they can get out of the ban and another member may receive the ban. In the community, you can ban members in several ways: Create ban rule from the Manage Users dashboard Ban members from the Content Management dashboard Ban members from the members’ profile page Ban members from the content page Create Ban rule from the Manage Users dashboard Using a ban rule, you can ban single or multiple members from the community. From the Manage Users dashboard, you can create and view the list of ban rules in the community as shown below: To create a ban rule: Sign in to the community as an Admin or Moderator. Open the Account menu and go to Manage > Users. The Banned tab on the Manage Users page is displayed. Click Create Ban Rule. Specify any of the following fields: Username: Enter a member’s username. The entry can include * and ? wildcard characters to ban all members whose usernames match all or part of the username. Example 1: If you enter the username as “Jess*,” any member whose username begins with “Jess” followed by any character will be banned. Example 2: If you enter the username as “Je?s,” the "? " replaces only the single character. The usernames like "Jess," "Jeos," and other matching usernames will be banned. User ID: Enter member’s unique User ID. Email Address: Enter member’s email address. The entry can include * and ? wildcard characters to ban members whose email addresses match all or part of the email address. Example 1: Entering “*@test.com” bans members whose email address begins with any character followed by test.com. Example 2: Entering “Je?s@test.com” bans members with email addresses like “Jess@test.com,” “Jeos@test.com,” and other matching email addresses. IP Address: Enter member’s IP address. Note that other members who use the same IP address will also be banned. Match any of the above criteria: Select this checkbox to ban a member who meets any of the criteria listed above. Otherwise, the ban is in effect only if all criteria are met. In the Ban Actions drop-down menu, select the ban Duration. The duration can be temporary or permanent as required. To set a custom duration, select Custom from the drop-down menu and set the duration. (Optional) In Ban Reasons, specify the following reasons for the ban: Internal reason for ban: Only Admins and Moderators can see this reason. They can see this reason when they edit the ban rule. Public reason for ban: Enter the reason that the banned member can see when they fail to sign in to the community. Click Ban. The impacted members are banned and signed out from the community. Ban members from the Content Management dashboard On the Content Management dashboard, you can ban members from the Spam, Abuse, and Moderation tabs using the Options menu > Ban Member. Note that you can only ban one member at a time from the Content Management dashboard. Let’s say you saw malicious content on the Abuse tab and you want to ban the member who created the content. To ban the member: Sign in to your community as an Admin or Moderator. Open the Account menu and go to Manage > Moderation. Go to the Moderation tab where you can view the list of content reported as abuse. To ban a member, open the Options menu and click Ban Member. The Ban Member window opens where the member details are auto-populated: Add information to the fields and click Ban. The Member is banned and signed out from the community. Similarly, you can ban members from the Spam and Moderation tabs. Ban members from the member profile page To ban a member from the member’s profile page: Sign in to the community as an Admin. Go to the member’s profile page by clicking the member account you want to ban on the community. Open the Options menu and click Ban Member. The Ban Member window opens where the member details are auto-populated. Specify the fields and click Ban. The Member is banned and signed out from the community. To modify ban, open the Options menu and click Edit Ban. Ban members from the content page From the content page (forum discussions, blog posts, ideas, and knowledge base articles), you can ban the member who created the content as well as members who posted replies/comments to the content. To ban an author, go to the respective post, open the Options menu, and click Ban member. To ban a member from comments or replies section, go to the comment or reply posted by the member, open the Options menu, and click Ban Member.Aurora: Configure remote site access for your Salesforce integration
The Aurora/Salesforce integration must be able to access your Khoros community. Part of this integration involves mentioning community APIs in the allowed list so Salesforce doesn't block them. To configure remote site access: In your Salesforce.com environment, go to Setup. Go to Administration Setup > Security Controls > Remote Site Settings. By default, two Remote Site Settings with the NameSpace prefix "LiSFintegration" appear. For the Khoros (Lithium) setting, click Edit. Enter the Base URL value according to your Khoros environment. 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/ Khoros Community Stage Base URL Sandbox https:// [community_id].stage.lithium.com Production https:// [community_id].lithium.com Note: Your Khoros Community Success Manager (CSM) can provide you with your Community ID. 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). (Optional) For debugging purposes, you can turn-off the requirement for HTTP communication. While this is not recommended in any production-like environment due to security risks, it may assist in diagnosing connectivity issues. After your diagnostics are complete, we strongly advise re-enabling HTTPS and maintaining it for security reasons. Click Save. Click Edit for the SFSelf setting and provide the Remote Site URL as your existing signed-in Salesforce URL (for example, https://na16.salesforce.com). Click Save. Repeat steps 3 – 9 for your production community, replacing the name with something descriptive such as “Khoros community – Production” and the URL with the final URL for your production community (for example, https://community.mywebaddress.com). Note: You can also repeat this process to connect multiple Khoros communities to your Salesforce instance. For custom domains (Salesforce 3.9 or later): Click New Remote Site. Enter SFSelfInstance for the Remote Site Name. Enter your Remote Site URL (for example, "yourinstance.salesforce.com"). Enter a Description for this site. Select the Active checkbox. Click Save.Aurora: Create a blog post
Community members can create posts in blog boards they have permission to access. When authoring posts, you have the option to publish immediately or save your progress and edit or publish at a later time. Published blog posts are available immediately on the community. When other members find and read this content, they can like or comment on it. Members with appropriate permissions can view the author's profile, and add more Tags. As an author, you can always come back and edit this content later to add more info or make any corrections. https://www.iorad.com/player/2053665/intermitted-save---blogs Notes: You can use markdown syntaxes while writing the content instead of formatting the text using toolbar options. Also, you can use other keyboard shortcuts to work quickly and efficiently. Learn more about keyboard shortcuts. While creating a blog post, the content is auto-saved. Upon reloading the page, the content is auto-recovered and you can continue to edit. Admins and members who started the post or have edit access to the post can add or remove tags. Learn more about tags. By default, members who comment on an article automatically follow the post. Permissions Permission Purpose Additional permissions required Start new posts To create your own blog posts. Content > Start discussions and new content View draft posts View drafts of blog posts Managing published posts Members with elevated permissions (like admins and moderators) can perform a variety of content management tasks on published blog posts. These tasks include: Move the post to another location on the community View the revision history of a blog post Edit and restore older versions of a post Delete the blog post Reject Report Content Block further edits to the blog post Block comments Most of these tasks are available from the Options menu: Note: If you don’t see any of these menu options, you do not have the required permissions to complete these tasks. Related topics: Create a Blog board Commenting on blogs Edit posts Publish posts Report inappropriate Follow Content Tags
