Recent Content
GraphQL Mutation for Creating a blog | No author parameter
Hi all, Unless I am going made, there is no option in graphQL to create a blog on behalf of another user is there? i.e. in the input field something like "Author": { "user" : {"id": "user:1234"}} This would be incredibly helpful as we use the APIv1 / v2 calls today to create a draft blog on behalf of a user so we can send those draft links to another user to enable Ghost writing. Example: A team needs to public a blog, however for consistency the team publishes all its public announcements from the director of engineering. The assistant (or another delegated user) needs to write a blog and make it appear as though it was from the directory himself.Aurora: Salesforce connector v4.4
Salesforce connector upgrade With many customers upgrading to Salesforce Hyperforce, where Salesforce IPs change dynamically, there is a risk of frequent integration failure. To mitigate this risk, we have upgraded the Salesforce connector to version 4.4 . Now, the authorization request originates from Salesforce to authorize the Salesforce Integration API App configured in the community. After the authorization is successful, the access and refresh tokens are verified and stored in Salesforce. This ensures a stable and seamless integration. Notes: Contact support to add the required configs in the configuration file. The authorization needs to be performed by a member with elevated permissions, for example, an Admin. This article guides you through: Steps to follow in the community Steps to follow in the Salesforce App Steps to follow in the community Note: The member who performs these steps should have elevated permissions like those of an Admin. Contact support to add the required value to the configuration file. The new setting automatically appears in Aurora Admin as shown below. Open the drop-down menu for this app (three dots) and select Edit web app. The Edit Web App window opens. In the Authorization redirect URL field, enter the redirect URL (or the callback URL). Select Edit. The entries are saved. Steps to follow in Salesforce This section walks you through installing and configuring the Salesforce connector. Navigate to the provided release package URL. Sign in to the Salesforce organization where you will install the connector package. Install the package. Select Install for all users and then select Done. Wait for the success message indicating successful installation. Confirm the package is installed by going to Setup > Installed Packages. Configure remote site settings. Go to Setup > Remote Site Settings. Create a remote site setting for the community integrating with Salesforce. Read more on how to configure Remote Site Settings. Set profile permissions. Go to Setup > Manage Users > Profile. Select the profile used for integration. Ensure appropriate Field Level Security Permissions are granted for Standard and custom objects (Account, Case, Contact, Postback Comment, Community Users, Private Message). From the App Launcher, select Khoros Salesforce Integration. Go to Custom Settings > Community Settings > Create. Enter community settings details. Community ID: The ID of the integrated application. Find this in the "Community" config in the config file. Client ID: The Client ID of the SalesforceIntegration API App on the community (Admin > Dev Tools > API Apps). Secret: The Secret corresponding to the Client ID. Redirect URL: The URL of the VisualForce page for Custom Settings. Base URL: The community base URL. For subpath-enabled communities, append the subpath. Is Proxy Enabled?: Always select this for Aurora applications. Context Name: Tapestry Context name/Webserver char path. Example: t5/s. Authorize the connection. After saving, the connection status shows "Not Active". Select Authorize. You are redirected to the Aurora application authorization page. Select Authorize. You are redirected to the authentication window. Note: Authorize with an Administrator or a member with admin-like permissions to prevent API call failures. After successful authentication, you are redirected to the custom settings page with the message "TenantId: is successfully authorized." The Connection Status updates to Active. The Username field displays the username used for authorization. This generates Access and Refresh tokens and they are stored in a Salesforce object. Note: When the access token expires, the Connection status changes to Halted. A "RefreshAuthToken" link appears. You can always re-authorize by selecting the Authorize link. By default, the refresh token expiry of the salesforceIntegrationApp is set to 5 years. 10. Configure feature settings. Select the Feature Settings tab. Select Create. Enable the required settings and select Save. Read more about configuring feature settings. 11. (Optional) Enable email notifications. To enable Salesforce email notifications for Case Create/Update/Comments, configure email services by going to Setup > Develop > Email Services. Read more on enabling email notifications.Aurora: Media Moderation Bypass
The Bypass moderation permission allows trusted members to post media (including images, videos, and attachments) without requiring moderation. This ensures a smoother experience for verified members while maintaining content control for the broader community. You can find this permission under Settings > Moderation > Users > Media.Aurora: Media moderation
If you want to moderate content with media, (images, videos, and attachment files), you can configure it via Default Media status setting. You can find this setting under Settings > Moderation > General > Default Media Status. The screenshot below shows this setting at the community level. Media moderation can be configured at both the category and board levels, with board-level settings taking precedence over the parent category. When you try to publish a post that contains media, the moderation settings for both content and media are checked. The post’s visibility depends on the moderation rules applied. For example, in the forum (called Pet Lovers) settings shown below, moderation for text content is set to Auto-approve and media status is set to Required. Any post with media is published only after moderators approve the media content. When members add specific bypass permissions along with non-admins try to publish a discussion in the forum, they receive a notification that the post requires approval and is not visible in the community. Moderators can approve or reject the post from the Moderation tab in the Manage Content dashboard. Note: Media moderation is available for: Discussions and their replies Blog comments Knowledge base comments Ideas and Idea comments Event comments To facilitate faster search results while moderating content, a filter for media is available on the Moderation tab in the Mange Content dashboard.Aurora: Activity limits
The Activity Limits settings limits rapid actions like publishing, commenting, or private messaging within short intervals in your community. For example, if a user attempts to publish or send private messages or post images too frequently, they will be temporarily restricted, ensuring the community remains focused on meaningful engagement rather than automated or disruptive behavior. You can find this setting under Settings > Moderation > Activity Limits. Below is a screenshot of Activity Limits feature options: There are three sections under Activity Limits: Default Limits: These limits are set at the community level and apply to all members. Select Edit for Default Limits to enter activity limit values. Role-Based Overrides: Here, you can specify specific roles from your community and set different activity limits. For members with these roles, the limits defined in this section will override the default limits. Select Edit for Role-Based Overrides to enter activity limit values. In the Apply only to following roles field, add the roles that should have different limits from the default. Role Exclusion: Here, you can specify community roles whose members should be exempt from activity limits. These are trusted members or most often Admins and Moderators. Also, when added, all members with these roles will automatically be granted the Bypass activity limits permission. Select Edit for Role Exclusion to add roles. Note: The Bypass flood control permission that was introduced in Aurora version 24.12 is now renamed to Bypass activity limits.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.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.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.
