How do I push new post notifications (e.g. via webhook) to third party services?
Good morning team, My goal is to make Khoros a "single source of truth" for several different discussion spaces at my company. Not all of them support RSS... but many of them support REST webhooks. How could I configure Khoros to send REST POSTs (aka webhooks) to specific listener URLs when topics are created? How could I filter that to specific labels, groups or admin tags? Thanks in advance for your help.About Aurora Groups
Groups deliver an enhanced experience for Community members to engage around a common theme or purpose. Each group has its own configurable set of content types (forum, blog, knowledge base, ideas, and events) to organize content and communication. This guide provides overview information about: Group membership types Search within groups Group management Group flood controls You can imagine groups for everything from special interests within the community to focus groups to product launches and more. Groups can be visible and open to anyone in the Community, closed (requiring a request to join), or hidden (invisible to the public and accessible by invitation only). Community Administrators can share group management with Community members by giving a member the Owner role, which enables the member to edit group details, manage membership requests and invitations, and assign and change group roles for members. Members can discover and browse groups on the Group landing page: The Group page provides quick access to the hub's info, contents, recent activity, and members. Administrators and group Owners can perform most group management tasks directly in the Community UI without needing access to Community Settings. On the Create Group page, here is a quick look at group configuration options. Note: The Boards section of the page appears to Community Administrators only. The ability to add group child places is dependent on the Add any community-supported boards permission, which is denied by default to the Owner, Curator, Inviter, and Member group roles. Member management is performed in the Manage Members page. An Owner or Administrator can see a list of current members, edit a member's role, remove members from the group, view pending invitations, and accept and deny requests to join. Other important group capabilities include fully-functional search and group subscriptions. Group membership types Every group has a membership type that controls access. A group can be: Open Closed Hidden Important: Membership type and access are managed through Community permissions. There are no other Community Settings to control access. For example, a hidden group is hidden because non-members of that group have the See groups permission set to Deny. Open groups All community members can browse and like all content, reply to posts, and comment on posts of the group. Group members can create new content and browse, reply, and comment on the post. The ability to see and join a group is governed by the access allowed to the container node. For example, an open group placed in a category with the See categories permission set to Deny cannot be joined by a member unless the member is assigned a role with See categories set to Grant. Ways to join: Join Group button on the Group page By invitation from a group Owner, Inviter, or an Administrator Closed groups As with open groups, a closed group is visible only to community members with access to the category in the group lives. Group visibility is governed by the access set on the container node. Non-members do not have read or reply permissions for closed groups. Content in closed groups appears in search results to group members only. Non-members who try to access a closed group are directed to a page explaining that the group is closed and that the user must request access. The request to join is sent to group Owners via email. Members can create new content as well as browse and reply to existing content Ways to join: Join Group button on the Group page. By invitation from a group Owner, Curator, Inviter, or an Administrator. Hidden groups Community members access Hidden groups either by invitation (by group Owner, Inviter, or an Administrator, or by being added to the group directly in Community Admin. Hidden groups are hidden from non-members in the Community UI and cannot be searched. Non-members attempting to access the URL to a hidden group’s page or child places are directed to an error page. Search within groups Content search within a group is fully-functional. All visitors can see content in open groups in community and place-level searches. Open group content is accessible to all. Content in closed groups is accessible only to group members. Hidden group content is searchable and accessible only by group members. Any relevant results in the community-wide search bar also surfaces content inside of groups to users who have permission to access it. Open and closed group nodes and child nodes appear in places search results to group members and non-members. Hidden group nodes appear in places search results to group members only. Group management in the Community UI The Community UI provides basic group management features: Create a group Delete a group Edit group details including group type, child board titles, and avatar Invite new members to the group Remove members from a group Manage group invitations and requests to join Manage group role assignments Group management in Community Admin Community Administrators can define Community Settings at the group container level, just as they can with other containers. In the Manage Members page, Community Administrators can remove a member from a group, edit a member’s role within the group, and manage any pending invitations. Group management by community members with Admin Permissions A community member with the Edit groups and Edit groups in Community Settings permissions can access Community Settings from the Group page in the Community UI and perform group administration actions. The permission adds the Edit Group Settings option to the Group page Options menu. These permissions are denied by default. Important! Be very careful when granting these permissions. It is intended to enable trusted employees to perform group actions that cannot be performed in the Community UI. For example, you may grant this permission to a product manager who is running an Early Access program through a group so that the product manager can quickly add customers to the group. We strongly recommend against granting this permission to your customers. Group flood controls Group members can send up to 50 invitations in an hour and up to 100 invitations per day.Group Role vs. Regular Roles
Hi, I'm trying to do something like this, but with group roles: <#assign is_gm = false /> <#list restadmin("/users/id/${user.id?c}/roles").roles.role as role> <#if role.name?? && (role.name == "GroupMember")> <#assign is_gm = true /> Then if it's true or false, I can make the page display accordingly. Apparently this doesn't work for Group Roles though, because it's doesn't recognize GroupMember as a role. So how do I modify it to check whether or not a person has a group role, as opposed to a regular role? ThanksUse Message body
Hi everyone! I'm currently trying to create a custom component, the goal is to display specific messages using a condition. I have the correct QUERY but I don´t know how to use/render the response. This is my code: <#assign apiVersion = "2.0" /> <#assign QUERY = "SELECT * FROM messages WHERE tags.text = 'F5 XC'" /> <#assign messageList = rest(apiVersion, "/search?q=" + QUERY?url).data.items /> <section> <h1 style="color: red;">Message List Component</h1> <#list messageList as messageItem> <h2 style="color: green;">${messageItem.subject}</h2> <p>${messageItem.body}</p> </#list> </section> This is the result: I'm getting in the body html tags as strings, so my question is how can I use the response or how can I render the message body properly?
Aurora Group roles and permissions
This article describes the roles and permissions used with Groups. Group roles Custom Group roles Mapping Group roles to content workflow capabilities Group permissions Add members to Group roles Permissions for Group role hierarchy Group roles Community includes out-of-the-box Group roles: Owner, Curator, Inviter, and Member. Community Administrators can create custom group roles at community, category, board, and group levels. You can add members to these Group roles only at the Group level. Note that you cannot add members to the Group roles at community or category level. A group can have multiple Owners. Only Community Administrators can assign the Owner role to group members. (Owners cannot assign the Owner role to other members.) Members with the Administrator role can perform all Owner actions. Owners and Administrators can assign group members the Curator and Inviter roles. This enables other group members the ability to create and manage place content and to invite other community members to the group. Having both a group Owner and one or more Curators helps distribute the task load for node content. An Owner can: Delete groups that they create Modify group settings Invite members Approve or deny requests to join Assign and change member roles Manage all content Perform all Member actions Manage featured content and places widgets on a page A Curator can: Manage all content Invite members Perform all Member actions Manage featured content and places widgets on a page Note: By default, the Edit items in list widgets permission is enabled for Group Owners and Curators to manage featured content and places widgets on any page. An Inviter can: Invite users Perform all Member actions A Member can: Create content Reply to content Edit their own content Delete their own content Tag content (if tagging content is permitted in the group's parent node) Mapping Group roles to content workflow capabilities You can map the Group roles to the capabilities in the KB and Blog content publishing workflow: Owner has all 3 capabilities: Authoring, editing, and publishing Curator has all 3 capabilities: Authoring, editing, and publishing Member has only authoring capabilities It is recommended to assign permissions to the roles instead of the users. Custom group roles Community Administrators can create custom group roles in Settings > Roles and Permissions at the community, category, board, and group node level. Group roles are created for a specific group; custom group roles are not shared across groups and custom group roles are not inherited from parent nodes. Learn more about Custom group roles. Group permissions Groups are backed by the standard Community permission system. Each membership type has default permissions that are applied when a group is created. Important! We strongly recommend against altering permissions on a per-group basis. Doing so could inadvertently override certain key permissions, such as making a Hidden group visible to non-members. At the Community and Category node level, Community includes these group permissions: See groups: See the group node type Edit groups: Edit group properties Delete groups: Delete a group and all its content Create groups: Create a group. Note: The Create groups permission enables a member to create a group with a forum. To enable all discussion styles in a group, a member must have Add any community-supported boards set to Grant. Move groups: Move a group to another location in the community structure. A group cannot be moved into another group. Edit groups in Community Settings: Enables a member to edit group info at community admin level. Add any community-supported boards: If granted, members can add any supported boards (Forum, Blog, KB, Ideas, Event) within the group. At the group node level, Community includes these group permissions: See group: See group nodes Edit group: Edit group node properties Delete group: Delete a group and all its content Add any community-supported boards: If granted, members can add any supported boards (Forum, Blog, KB, and Ideas) within the group. Edit groups in Community Settings permission enables a member to edit group info at community admin level. Send group invitations: Send invitations to join groups. Bypass group invitation flood control: Members with this permission can bypass the flooding control set in place when sending membership invites. Add members to Group roles At Group level, Admins can add members to Group roles to perform certain tasks in the Group based on the Group role. Note that members must be a part of the Group to perform these role-based tasks. To add members to a group role: From the Account menu, go to Settings > Community Structure. From the structure, click the name of the Group. From the Settings page, click Group Permissions. The Settings page is displayed with Group Permissions Defaults and Group Roles sections. Under Group Roles, click any of the roles. For example, Curator. The Group permissions page is displayed with default Curator permissions and Members of the role. To add members to this role, click Add Members next to the Members section. In Add Members window, find and add members. Click Save. Note that you can add up to 10 members at a time. Permissions for Group role hierarchy A tab called Group Roles is available under Community Settings > USERS. All the group related roles (Curator, Inviter, Member, and Owner) are available on this tab. These roles are available at the community and category levels. The roles hierarchy for Groups enables global management of group role permissions. You can change the membership role permissions either at the community level or at the category level. The permissions for the roles cascade down to all the groups within the community or the category, respectively. Learn more about Group roles hierarchy and how Group role permissions are determined.Can we show the event calendar component only on group hubs with event discussion style enabled?
Can we scope the calendar event component ONLY on those group hubs that have Event discussion style enabled? For Example: Group Hub1 (with all four discussion styles enabled) forum Article Suggestion Event Group Hub2 (with only Article discussion style enabled) Article So, when the even calendar component is added on group hub page, the component is displayed on all the group hubs on community (in above case it's added on both group hubs with and without event discussion style enabled). Can we scope it to only group hubs with Event discussion style enabled ? In the above example we would want it to be displayed only on Group Hub1. Is there a parameter that can be configured to toggle this setting on this component? <component id="occasions.widget.calendar" />Aurora: Invite members to a group
Group Owners and Community Administrators can start the invitation flow in the Manage Members page or from the Options menu of the Group page. Group Curators and Inviters can start the invitation flow from the Group page Options menu. Group users can send 50 invitations in an hour and up to 100 invitations in a day. Note that if you want to change these default configuration values, you must open a Support ticket. For the community members, you can send the invitation via private message by specifying their usernames. To invite external users, you can send the invitation via email by specifying their email addresses. From the group settings, you can configure the mode of group invitations. Note: The community member receiving the invitation and receiving the approval notification must have a verified email address. To send an invitation: Select Invite New Members from the Group page Options menu or click Send Invite in the Manage Members page. Groups Page Options menu Manage Members Page (Click Options menu > Manage Members in the Group page) Send Invitation dialog box opens. In Send Invitation dialog box, specify the following fields: To: Specify the recipient Username or email address. Role: Select the group role from the drop-down that you want to assign to the recipient. Message (optional): Enter the invitation message. This field is optional. Click Send Invite. Community members or external users receive a private message or email with the invitation and a link to join the group. When the external users click Accept the invitation link, they are redirected to the Registration page to register themselves to the community before joining the group. When the member clicks Accept the invitation link, they are redirected to the group page with a confirmation message that they are now a member of the group.Aurora: Edit Group settings
In the Community UI, group Owners and Community Administrators can edit group settings. Administrators can also edit a group in Community Admin. Edit a Group in the Community UI Edit a Group in Community Admin Edit a Group in the Community UI Sign in to Community and go to a Group page. From the Options menu, click Edit Info. The Edit Group page is displayed. From here, you can edit the Name, Description, Avatar, Membership Type, and the Names of the child boards in the group. Community Administrators can add or remove boards in the group. Note: By default, group Owners cannot edit child places in a group. To enable this ability, you can clone the Owner role and set the Add any community-supported boards permission to Grant. See Create a custom group role for instructions. Click Save. Edit a Group in Community Admin To edit a Group in Community Admin: From the Account menu, go to Settings > Community Structure. Find the group in the structure, open the Options menu, and click Edit. Click Edit Info. From here, you can change the Name, Description, Group Avatar, Group Type, and boards included in the group. Note: Board titles within groups must be added and edited in the Community UI. Click Save. Additionally, you can change the group’s content-related settings: Content workflow: Enable this option to use the content workflow features for blogs and knowledge bases. File attachments: Define the filename extensions, maximum file size, and maximum number of attachments per for file attachments. Media: Enable this option to allow members to add images to their content. Tags: Enable this option and set tag options to add tags to the content within the group. Learn more about configuring tag options. Invitations: Configure Send invitations via option that allows members to send group invitations either via community inbox (for members only) or email (for both members and non-members). Moderation: Configure moderation settings such as spam management and content moderation defaults at the group level.
