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 flood control 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.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 underContent 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.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: Overview of Content Workflow and Approval feature for Knowledge Base articles and Blog posts
To enable people to create high-quality and engaging content quickly, you need a simple process for authors, editors, and publishers to follow. Different people have different responsibilities in the content creation workflow, and it’s important for teams to be able to collaborate on new and existing articles at scale and not get in each other’s way. Granular control over author, editor, and publisher permissions, enables you to clearly define who can perform each task in the publishing workflow. Each blog post or KB article moves through different states, and members can view the latest state of articles and blog posts via Manage Content Dashboard. This flowchart shows how an article moves through the publishing workflow and the tasks members with specific roles can perform. Feature Enablement Admins can enable content workflow in your community. To enable it, goto Account menu > Settings > Features > General and enable Content Workflow. Learn more on how to enable Content workflow in the community. Key features The default roles for content workflow include: BlogAuthor:Can start and edit blog articles BlogEditor:Can edit on articles that are in the Awaiting Review state. BlogEditors can send articles back to the BlogAuthor if there are changes required or can forward the article to the BlogPublisher for publication BlogPublisher:Can approve and publish articles that are in the Awaiting Publicationstate or send the article back to the BlogEditor if additional changes are needed. KBAuthor: Can start and edit KB articles KBEditor: Can edit articles that are in the Awaiting Review state. KBEditors can send articles back to the KBAuthor if there are changes required or can forward the article to the KBPublisher for publication KBPublisher: Can approve and publish articles that are in the Awaiting Publicationstate or send the article back to the KBEditor if additional changes are needed. You can find these roles when you go to Settings > Users > Community Permission Defaults. Learn more about enabling this feature and assigning roles to members 3-step workflow: Once you assign the above roles members, every draft will go through the process of publishing articles with a 3-step workflow that provides for authoring, editing and publishing. Below is an example of a blog post’s draft page that was written by a member with a BlogAuthor role and submitted for review. You can see the status of the draft, version number, and perform further actions depending on your role in the workflow process. When the drafts are in the 3-step workflow and yet to be published, you can Manage Content:Trackan article’s or blog post's journey in the publishing workflow and make it easier to take relevant actions using thecontent managementdashboard. Compare two revisions of a draft:Compareany two versions when the article or blog post is in the workflow process. The differences between the two versions are highlighted View Draft History:Track every action each member performs on an article or blog post until it is published. Note: As of today, email notifications are not sent to members with these roles. This feature will be available in a future release. Knowledge Base article and blog post states In this publishing workflow, knowledge base articles and blog posts can be in one of four states: Draft:Articles or blog post has been created or edited but isn't ready to be reviewed or published Awaiting Review:Article or blog post draft is ready for review Awaiting Publication:Article or blog post has been reviewed and is ready for approval and publication Published:Article or blog post has been published. If this article or blog post was a revision for an already-published article or blog post, respectively, this new version replaces the previous version in the community Related topics: 3-step workflow for Knowledge base articles and blog posts Return a Knowledge base article or blog post back to draft state Send a Knowledge Base article or blog post back for reviewAurora: 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 mustmanually specify your organization's Client ID and Client Secret values in theCommunity Adminpanel. 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. In the Zoom SDK App, you must specify your community's redirect URL inRedirect URL for OathandOath Allow listfields. Sample redirect URL format: https://<community hostname>/<community name>/api/2.0/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. SelectSettings. The Settings page opens. Select Content Features. Select Events. Beside Zoom integration, selectIntegrate. A window to enter Zoom's Client ID and Client secret opens. Enter theClient 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 integrationis successful when you see the Remove button. To remove the Zoom Integration: Sign in as an Admin of the community. Open the Account menu. SelectSettings. The Settings page opens. SelectContent Features. Select Events. Beside Zoom integration, selectRemove. 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: Create an event
Community members can create events in Event boards they have permission to access. Here's an example of an event creation page: Here's an example of a published event on an Events board: 26 STEPS 1. On the community board, click Create an Event 2. The page to create an event opens. Click + on the banner to add a banner. This banner will appear on the published view of the event. 3. You can either upload from your device or search and upload an image from the internet. 4. You can now see the image that you uploaded. Add a title for the event. 5. Enter text for the event 6. From the Event type dropdown menu, select the type of event. As we are creating an In-Person event, we select In-Person 7. Click on the textbox labeled Start and enter a start date and time for this event 8. The calendar menu appears. Choose a start date. 9. Choose a time and time zone 10. Click on the textbox labeled End. 11. The calendar menu appears Choose a end date. 12. Choose a time and time zone 13. You can optionally specify the location for this In-person event. You can opt to update this information even after publishing this event. Start enter the address of the location and choose from the suggestions. 14. Optionally, click Display map on event page 15. A google map loads that shows the location of the address you added. 16. You can opt to add Guests for your event. Click Add a member link to search and add a community member as a Featured Guest for this event. 17. A search box appears. 18. Enter a member name and choose from the suggestions. 19. The selected member is added as a Featured Guest. 20. To improve findability, you can tag this event. Click Add a Tag to add new tags. 21. Type the new tag 22. After you select the newly entered tag, you can see it listed under Tags section of the page 23. Scroll down and click Publish 24. The event is published. 25. To see how this event is listed in the board, click the board name on the breadcrumb. 26. You can see that the event under the Event board. That's it! You're done! Here's an interactive tutorial Note: The default number of featured guests and its limit its 10. This value is configurable. To change this limit, Contact Khoros Support. Related topics: About Events Creating an events node in community structure Events permissions and settings Event types Integrate Zoom with Community Events
Aurora Product Coaching Session: Spam Management Best Practise
Khoros Communities platform offers several settings and features that allow you to mitigate Spam in your community. Join ourSpam Management Best Practice 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: Redirect user to related content
When you archive content, you can provide a permanent redirect link to related content within the community or an external page. Members who attempt to access archived content (via permalink) see a notification indicating that the content has been archived and redirected to relevant information. Though this is optional, it is best practice to provide a related link to relevant content while archiving. For instance, if a Google search result suggests a piece of content that was archived in your community and members select that link, they are automatically redirected to the related content in your community. As the redirection occurs for several members, the Google crawlers understand that the old link is replaced and boost up the new link's ranking instead of the old link. If you didn’t do this when you archived the article, you can opt to add it later from the Archives page. Add a URL to related content Sign in to the community Select Archives on the Manage Content dashboard. Select the Options (...) menu and select Add Link to Related Content. A window to enter the URL opens. Enter a link to the relevant content in your community. Select Add. The entered link is added. After an article is archived: Members who are not admins or moderators are redirected to the page that was added as related content. If no redirect URL is provided, they land on an empty page as shown below. Community admins and moderators land on the original page and see a notification that the page was archived. A link to the related article is provided. Furthermore, you can edit the added link from the archived page by opening the Settings menu and selecting Edit Link to Related Content. Add a URL to an external page You can also redirect members to external pages outside the community. To achieve this, toggle on External URLs under Settings > Features > Moderation > Content Archive.Aurora: Unarchive Content
When content is unarchived, it returns to its original location in the community before it was archived. The position of the original board list is also retained. The article's publish/last updated date is retained. Also, you cannot unarchive content whose board has been deleted. Assume that topic B was archived from the board list with topics A, B, C, D, and E. If topic B is later unarchived, it returns to its original position, and the board list again shows topics A, B, C, D, and E and not A, C, D, E, and B. To unarchive content: Go to the Manage Content page. Select Archives. Select the Options menu (...) in the row of the content you want to unarchive. Select Unarchive. The original location of the archived post is selected by default: You can also choose to unarchive the content to another location in the community. 5. Select Unarchive. You receive confirmation that the post is unarchived to the selected location. As shown below, you can also unarchive the content from the content page by opening the Settings menu and selecting Unarchive.Aurora: Delete Archived content
To delete content: Go to the Manage Content page. Select Archives. Open the Options menu in the row of the content you want to unarchive. Select Delete. A window to confirm the delete action opens. 5. Select Delete. The archived content is permanently deleted from the community and cannot be retrieved.
