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: View the history of published content
Over time, content posted to the community can change as different people edit the content. These changes can be subtle or complete rewrites of the original content. Sometimes, changes get made that are not correct or need to be reverted to an earlier iteration of the content. Aurora gives you the ability to track the changes in every version of a blog post or knowledge base article from its draft state up through its current published state. Each time you publish a KB article or blog post, the major version number is incremented (v1.0, v2.0, and so on). For example, in v1.0, 1 is the major version number and 0 is the minor version number. The minor version number is always zero for a published article. Each time you edit and save a published article, the major version number remains the same as the current version number and the minor version number is incremented (v2.1, 2.2, and so on). For every version, you can see who made the change and what was changed. Let's look at an example of the version history for a knowledge base article. To view the history of revisions: Go to the KB article page. Click History. The revision history of the article displays in a popup window: The published version gets an incremental version number (v1.0, V2.0, v3.0, …) From the Version History view, you can: view the revision notes that were added while editing the article. Compare the versions of the article. Edit and restore any older version of the article. Permissions View history of blog posts and knowledge base articles Set the permission View edit history under Settings > Roles and Permissions > Content to allow members to view and compare different versions of blog posts and knowledge base articles.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 TagsAurora: Integrate Zoom with Community Events
Integrating Zoom with your Community Events enables you to offer real-time user engagement from within the community. With Events, you can host both Zoom Meetings and Zoom Webinars. Zoom Meetings: All participants can share their screen, turn on their video and audio, and see who else is in attendance. Zoom Webinars: Webinars enable view-only attendance. The host and any designated panelists can share their video, audio, and screen. Participants have the ability to interact via Q&A, Chat, and answer polling questions. The host can also unmute attendees. Attendees in webinars cannot rename themselves. Participants can join a meeting on your website without having the Zoom app. Authorize Zoom To host Zoom calls within the Events feature, we use the Zoom App SDK. To integrate Zoom with Community Events, you must manually specify your organization's Client ID and Client Secret values in the Community Admin panel. These values are encrypted and stored in Khoros’ database. Prerequisites We recommend that you create an admin account in Zoom. During authorizing Zoom in the community, you must sign in with the same account to grant access to the Zoom event. Note that the Zoom app can be unpublished. Generate the Client ID and Client Secret from the Zoom SDK App. Learn more about how to generate Client ID and Client Secret from the Zoom SDK App. Add the follwoing to the Scope in the Zoom App Marketspace: Meeting scopes: meeting:read:meeting meeting:write:meeting Webinar scopes: (QandA and chat options also come up with just below scopes) webinar:read:webinar webinar:write:webinar In the Zoom SDK App, you must specify your community's redirect URL in Redirect URL for Oath and Oath Allow list fields. Sample redirect URL format: https://<community hostname>/t5/s/community name/api/2.1/zoom/oauth2callback Admins can manually enter and delete the Zoom Client ID and secret key values in the community’s Admin Settings, which are encrypted and stored in Khoros’ database. To authorize Zoom: Sign in as an Admin of the community. Open the Account menu. Select Settings. The Settings page opens. Select Content Features. Select Events. Beside Zoom integration, select Integrate. A window to enter Zoom's Client ID and Client secret opens. Enter the Client ID and Client secret. Select Configure. You may be asked to sign in to the Zoom app. After you sign in, you are redirected to the settings page. If the integration is successful, a success message appears. The Zoom integration is successful when you see the Remove button. To remove the Zoom Integration: Sign in as an Admin of the community. Open the Account menu. Select Settings. The Settings page opens. Select Content Features. Select Events. Beside Zoom integration, select Remove. The Zoom integration is removed and the button changes back to Integrate. Related topics: Events permissions and settings Create an event Event types Events with Zoom Meetings Events with Zoom WebinarAurora: About idea statuses
When working with ideas, statuses play a key role in organizing ideas and letting idea contributors know where an idea is in the approval and delivery process. Statuses communicate where an idea is in the workflow. By updating the status, your company publicly lets members know which ideas are being reviewed or are in the process of being implemented. The statuses you create depend on the purpose of the Ideas board. If you’re soliciting product ideas, for example, statuses should reflect a progression from new idea, through review, to eventual implementation, or to indicate that an idea has been declined. When an Ideas board is created, Khoros includes several statuses out-of-the-box. You can edit or delete these statuses and add new ones specific to your needs. You can create or edit statuses only at the Ideas board level. To provide better reporting and analytics, these statuses are grouped into various Status Sets. Each new Ideas board you create includes the following statuses: Status Set Statuses Description New Unspecified Idea has no status label visible to members. New Newly submitted idea awaiting team review. In Progress In Review Idea is being investigated and scoped by the team. Accepted Idea has been accepted by the team. On Hold Needs info More information is needed from the author of this idea. Future Consideration Idea has been not been immediately accepted by the team but is considered for future implementation. Completed Delivered Idea has been successfully completed and delivered to customers. Closed Declined Idea has been rejected by the team. Already Exists Similar idea has already been submitted or delivered. View Idea status sets and statuses From the Ideas Board Settings page, you can view the default idea statuses that are grouped into various Status Sets as shown below: You can drag and drop the statuses under required status sets or reorder them. This defines the order in which the statuses are displayed in the dropdown menus. Note: Only admins can view status sets, which cannot be created or deleted. Create a new status Sign in to the Community as an Admin. Open the Account menu and click Settings. Click Community Structure and go to the Ideas board where you want to create a status. The Ideas Board Settings page is displayed. Go to the Status Sets, and under the status set where you want to add a status, click Add Status. For example, under the In Progress status set, let’s add a status called “Planned." The Add Idea Status window opens. On the window, specify the following fields: Enter a Name for this status that members see in the Ideas board. Enter a status ID. Only alphanumeric characters, dashes, and hyphens are supported. This ID cannot be reused for other statuses. Optionally, enter the Description for this status. In the Visual Style, toggle on Show idea status label to have the label displayed members. If it is turned off, then only admin, moderators, and members with the Change idea status permission can view this label. Select the required label and label color you want to display. In the Preview, you can view the applied changes to the label. Click Add Status. The status has been successfully added. Set default status When a member submits an idea, the idea status is set to “New” by default. From the Ideas Board Settings page, you can change the default status to use when members submit ideas. To change the default status, go to the Ideas Board Settings page and click Set as Default next to the status. Edit status From the Ideas Board Settings page, you can edit the status to update any fields such as Name, Description, Idea Status Label, Label color, and so on. Note that you cannot edit the Status ID. To edit a status: Go to the Status Sets and click Edit next to the status. Update the required fields and click Save. Delete status From the Ideas Board Settings page, you can delete a status that’s no longer required. Note that you cannot delete the default status. To delete a status, go to the Status Sets and click Delete next to the status you want to delete.Aurora: Bypass flood control
If you want to allow trusted members to publish content without being blocked by flood limits, grant the Bypass flood control permission. To deny or grant this permission for a role Sign in to the community as an Admin. Go to Settings > Users > Roles and Permissions > Moderation. Select Grant or Deny for the Bypass activity limits permission. If this permission is denied for any role and a member with that role exceeds the flood control limit while attempting to publish content, an error message appears at the bottom of the page and the content is not published. Note: Members can be granted this permission from the Activity Limits setting.Aurora: Bypass content filters
If you want to allow trusted members to publish content without being blocked by any content filters, grant the Bypass content filters permission. To deny or grant this permission for a role Sign in to the community as an Admin. Go to Settings > Users > Roles and Permissions > Moderation. Select Grant or Deny for the Bypass content filters permission. If this permission is denied for any role and a member with that role attempts to publish content containing any words listed under Content Filters, they receive an error message at the bottom of the page. For example, below is a screenshot of the error message when a user without this permission cannot publish their content because the word “cannibalism” is listed under Content Filters.Aurora: Bypass automatic spam rejection
Aurora Communities are equipped with automatic spam detection. If you would like to allow trusted members to publish content without getting scanned by the spam detection engine, you can do so by using the Bypass automatic spam rejection permission. To deny or grant this permission for a role Sign in to the community as an Admin. Go to Settings > Users > Roles and Permissions > Moderation. Select Grant or Deny for the Bypass automatic spam rejection permission.Aurora: Add co-authors to blog posts
Recognizing co-authors along with the main author is a way to acknowledge everyone who contributes to a piece of content and enhance the overall quality and credibility of the content. It also encourages collaboration and fosters a sense of community among contributors and readers. If you have the BlogAuthor or Admin role, you can add members as co-authors for published blog posts or to drafts. All co-authors automatically receive editing permissions for the blog post they are added to. After you publish the blog post, the author and the list of co-authors is displayed. You can also view these actions in the history view of the blog post Related topic: Remove co-authors from blog posts
