Welcome to Khoros’ community, Atlas

Recent Content

Aurora: Enable content moderation and set content moderation defaults
Community moderators review and process large volumes of member-generated content. Moderation is an important part of keeping a community a safe and engaging space for your members to participate. Depending on how you configure the moderation settings, content can also be auto-approved and skip the moderation process. The moderation process depends on the defaults you set for various boards. Admins can set these moderation defaults for forum discussions and replies, blog comments, ideas and their comments, event and event comments, media, and knowledge base comments at the community, category, and board levels. Auto-approved: The content is auto-approved and made public without going through moderation review unless flagged. Recommended for trusted areas that are self-regulated by a small group of members. Selective: The content is made public to the community without going through moderation. However, moderators can selectively review this content later, and based on the review, the content stays or is removed from the community. Required: The content must go through moderation for review, and based on the moderator's evaluation, the content is either published or removed from the community. By default, Selective moderation is set for all boards. Understanding the different moderation types Before configuring the content moderation defaults, you must understand the benefits and risks of each option: Auto-approved: Set Auto-approved for places that are designed for open discussions without any need for regulating the content posted by members. Use this option in places that are self-regulated by a small group of members who are accountable for their actions. However, we still recommend you implement the moderation process within the community to avoid spreading inappropriate information. Selective: Similar to Auto-approved, the Selective moderation process also encourages open communication among members in that they can publish content immediately without prior review. Moderators can still review the published content to ensure the posted content is appropriate and adheres to the community’s principles. Use this option in places where members expect fast-paced and live interaction without having to wait long for the moderation process to complete. However, when moderation is delayed, there is the potential risk of inappropriate content (abuse or spam) being posted that impacts readers and disrupts the community. Compared to the Required moderation process, this process is less effective in avoiding spam and abusive content. Required: Required moderation is the best way to combat spam and abusive content because the content is sent to the moderation before it’s made public in the community. This also protects your community’s reputation and creates a safe space for your members by ensuring the appropriate content is posted in the community. However, this process relies on additional resources to review the content, which may delay making the content public. This can disappoint members who want their content to be made public quickly. Set content moderation defaults at community level Sign in to the community as an Admin. Open the Account menu and go to Settings > Features. Select Moderation. The Moderation Types settings displays spam and content moderation settings. Here, you can set default moderation types for discussions, ideas, replies or comments on discussions, blog posts, knowledge base articles, events, and media. The screenshot below displays the Moderation Types, numbered for clarity. Select Edit for any of these options. A window to edit the moderation type opens. From here, you can: assign the moderation type for all members override this setting for specific roles with another moderation type value specify the roles that will bypass moderation The following is an example for moderating discussions and replies. The Community moderation type field for discussions and replies by all members falls under the Selective moderation type. Thier content is hidden until reviewed and approved. The Role-based Override field is set to Required for the roles selected in the Apply only to the following roles field. Discussions and replies by members with these roles are made public but go through moderation review. Roles added to the Exclude Roles field automatically bypass any moderation action. Similarly, you can set default statuses for other content types at the community level. Set content moderation defaults at category, group, or board levels The Moderation Types set at the community level are inherited to the category, group, and board levels. You can override these options at various levels as needed. Based on the inheritance, the settings applied at different levels are inherited to child places from their parent levels. For example, the content moderation defaults set at category or group levels are inherited to their child places. Learn more about setting inheritance. Let’s look at an example in which you want to set content moderation defaults at category level. To set content moderation defaults at category level: Open the Account menu and go to Settings > Community Structure. On the Community Structure page, select the category where you want to set the content moderation defaults. In the category settings, go to the Moderation section and set Content moderation types for content review as required. When you’ve adjusted a setting for a child place, a PARENT OVERRIDE indicator is displayed next to that setting for the child place to indicate that it overrides the settings of its parent. Similarly, you can set content moderation defaults at the group and board levels. Based on these board-level settings, when members post content on the community, the content is immediately routed to the Moderation for review. 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: From the Moderation tab, moderators can review content for appropriateness. They can then approve or reject it, and also message authors of the posts. Learn more about moderating content. Note: it is not possible to set different moderation levels for comments(or replies) and main posts Grant permissions to moderate content Moderation permissions should be granted only to roles assigned to trusted individuals. To manage this permission: Navigate to Admin > Settings > Users > Roles and Permissions. In the row of the role for which you want to manage this permission, select the Options menu and then Edit. In the Permissions area, below Moderation, locate Moderate Content. Select Grant or Deny as required.
BhuvanaM
Khoros Alumni (Retired)
60 minutes agoPlace Khoros Communities - Aurora Docs
communities aurora
general tasks
moderation
455Views
1like
0Comments
Khoros Communities: Aurora 25.03 Release Notes
7 MIN READ The Khoros Communities: Aurora v25.03 Release introduces performance improvements, several new permissions, the ability to download your case list, moderation enhancements, post activity limit updates, improvements to the developer experience, and many bug fixes to improve the member experience.
LauraV
Khoros Staff
2 hours agoPlace Release Notes & Updates
communities aurora
product updates
release notes
123Views
3likes
0Comments
Creating a blog on behalf of another user - GraphQL
Hi all, In classic we could create a blog on behalf of another user if the API user creating the blog had the permission to switch user. This was achieved using a APIv1 call the message endpoint and passing in the parameter message.author=id/<userid> in the api call. As far as I know this was not included in APIv2 and I can't find it in graphAPI and its a very crucial function for us until LarryI adds Ghost Writing to the platform! I have tried everything I can think of and it won't let me do this.
allensmith81
Boss
12 hours agoPlace Developer Discussion
6Views
0likes
0Comments
April 2025 Atlas Highlights
3 MIN READ Monthly digest to provide all users a reliable snapshot of product updates, as well as any other resources that can provide inspiration or guidance.
CoryD
Khoros Staff
17 hours agoPlace Release Notes & Updates
atlas highlights
34Views
2likes
1Comment
Launching on Khoros Communities Session #2: Preparing to launch | Instructor Led-Training
Recording from this live webinar can be found in Khoros Academy: https://academy.khoros.com?C=20754320 *Please log into Khoros Academy prior to accessing the recording link above. If you do not yet have access to Khoros Academy, you may access the recordings via the links below: https://videos.khoros.com/watch/RUGbG1PNGnoKnfVp652tPG? https://videos.khoros.com/watch/bvsjwpPsRQtutfYi8ZSqUj?%20 Q&As from the recorded session are attached below. Wednesday, Feb 19, 2025 1pm UTC and 9pm UTC In today’s ever-changing digital world, customer engagement tools—most importantly, engagement communities—must evolve to retain and keep customers satisfied. Khoros Communities Aurora delivers a sleek, modern, and high-performance system that adheres to community best practices while still giving brands complete flexibility to make changes or updates to address their ongoing needs. In this session, focussed on the Initiation and Planning phases of the launch/upgrade process, you will learn about: The Initiation and Planning phases and project timeline General tasks to complete prior to and during the Initiation and Planning phases Internal resources your team needs to launch on Khoros Communities Whether you are preparing for your upgrade to or launch on Khoros Communities Aurora or simply learning more about the process, we are here to help. Missed the first session in this series? Review the Q&A and access recording here.
LynnT
Khoros Staff
19 hours agoPlace Events & Webinars
Khoros Communities
337Views
1like
0Comments
Launching on Khoros Communities Session #3: Executing the Launch | Instructor-Led Training
Recording from this live webinar can be found in Khoros Academy: https://academy.khoros.com?C=21449269 *Please log into Khoros Academy prior to accessing the recording link above. If you do not yet have access to Khoros Academy, you may access the recordings via the links below: https://videos.khoros.com/watch/xGjLX1SWYPqdmBx7MBLPjg Tuesday, April 1, 2025, 1 pm UTC and 9pm UTC Engagement communities play a vital role in retaining and keeping your customers satisfied in an ever-changing digital world. Khoros Communities Aurora delivers a sleek, modern, and high-performance system that adheres to community best practices while still giving brands complete flexibility to make changes or updates to address their ongoing needs. In this session, focussed on the Execution and Launch phases of the launch/upgrade process, you will learn about: The 3 main tracks running concurrently through the Execution Phase The User Acceptance Testing (UAT) process and the final Launch Phase Internal resources needed and how best to prepare for the Execution and Launch Phases Whether you are preparing for your upgrade to or launch on Khoros Communities Aurora or simply learning more about the process, we are here to help. Missed the first two sessions in this series? Review the Q&A and access recordings through the following links. https://academy.khoros.com/?C=19907878 https://academy.khoros.com/?C=20754320
LynnT
Khoros Staff
19 hours agoPlace Events & Webinars
Khoros Communities
109Views
1like
0Comments
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. https://calendly.com/khoros-product-coaching-community-use-cases/khoros-communities-aurora-spam-management?utm_source=atlas👉Click here to Sign Up Related Resources Enable Spam Management Community Spam Management Review Posts Captured as Spam https://academy.khoros.com/course/15982303?r=False&ts=638687569316138078 https://academy.khoros.com/course/18989802?r=False&ts=638687568356867760
RishiA
Khoros Staff
19 hours agoPlace Khoros Communities - Aurora Docs
community management
content management
Getting Started
moderation
Product Coaching
164Views
1like
0Comments
Khoros Communities: Classic 25.03 Release Notes
1 MIN READ You Found It. We Fixed It. .jmppresets extension is an allowed attachment format in Community. The Blog comment moderation setting no longer interferes with blog post notifications, ensuring they are delivered as expected upon publication.
AshaC
Khoros Staff
2 days agoPlace Release Notes & Updates
communities classic
release notes
34Views
2likes
0Comments
json query syntax matches AND OR
Hello, I cannot find the full json query syntax documentation here. Thats wha I'm asking in this post: How does a json based query look like for AND matches in body text. I want to query all posts containing term1 AND term2 in their body. My query currently is this. How do I add the term2? [ { "messages":{ "fields":[ "id", "subject", "search_snippet", "body", "cover_image.view_href", "teaser", "view_href", "author", "conversation.last_post_time", "replies.count(*)", "kudos.sum(weight)", "metrics.views", "labels" ], "constraints":[ { "category.id":"DE", "conversation.style":"tkb", "body":{ "matches":"term1" }, "depth":0 } ], "sorts": [ "post_time desc" ], "limit":10, "subQueries":{ "labels":{ "fields":[ "text", "id" ] } } } } ]
anmi
Adept
2 days agoPlace Developer Discussion
Rest API
REST API v2 & LiQL
207Views
1like
6Comments
Aurora: 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.
AshaC
Khoros Staff
2 days agoPlace Khoros Communities - Aurora Docs
communities aurora
content management
general tasks
173Views
0likes
0Comments

Welcome to Khoros’ community, Atlas

Featured Content

April 2025 Atlas Highlights

Launching on Khoros Communities Session #3: Executing the Launch | Instructor-Led Training

Khoros Communities Spring Product Update Webinar

Atlas Community Guidelines

Recent Content

Aurora: Enable content moderation and set content moderation defaults

Khoros Communities: Aurora 25.03 Release Notes

Creating a blog on behalf of another user - GraphQL

April 2025 Atlas Highlights

Launching on Khoros Communities Session #2: Preparing to launch | Instructor Led-Training

Launching on Khoros Communities Session #3: Executing the Launch | Instructor-Led Training

Aurora Product Coaching Session: Spam Management Best Practices

Khoros Communities: Classic 25.03 Release Notes

json query syntax matches AND OR

Aurora: View the history of published content

Featured Places

Education & Training

Help & Support