Pull different Aurora community content into an RSS feed using URLs
You can pull different community content from different levels in the community in an RSS feed using URLs. To pull the most recent RSS results for the entire community, use: https://yourdomain.com/t5/s/[CommunityID]/rss/Community For example, for Atlas, you'd use: https://community.khoros.com/t5/s/lithosphere/rss/Community To pull content over the RSS for a category, use: https://yourdomain.com/t5/s/[CommunityID]/rss/Category?category.id=[CategoryID] For example, if Atlas had a category with the ID of "Social," you'd use: https://community.khoros.com/t5/s/lithosphere/rss/Category?category.id=Social Note: Category IDs are case sensitive. To pull content over the RSS for a KB, use: https://yourdomain.com/t5/s/[CommunityID]/rss/Community?interaction.style=tkb For example, for Atlas you'd use: https://community.khoros.com/t5/s/lithosphere/rss/Community?interaction.style=tkbAbout Aurora Community site structure
One of the most important aspects of setting up your community is choosing which content types to include and how to organize them. Communities are structured hierarchically—they’re broken down into Places, which are divided into Containers and Boards. Containers consist of Categories and Groups, while Boards consist of Forums, Knowledge Bases, Blogs, Ideas, and Events. Typically, Categories and Groups are made up of Boards—these boards are the areas where community members can post and reply or comment on what they read. Categories can also be broken down into other Categories as necessary. Containers Containers are higher-level Places like Categories and Groups. Categories are areas that can house several types of Boards that are broken out into different types of content. Groups are similar to Categories, but they are designed for specific groups of Community members who want to collaborate on a particular subject or project. Create a Category Create a Group Create a Category Go to the Community Structure page. Select Add (plus icon) at the level of the community where you want to add the category. On the window, enter a Name and ID. The ID displays in the URL for the category. Note: The ID must be a single word made of only letters, numbers, dashes, and underscores with no spaces. It cannot be changed later. Optionally, enter a Description and add an Avatar for the category. Select Create. For more information, see About Categories. Boards Create a Forum Create a Knowledge Base Create a Blog Create an Ideas board Create an Event board Boards are Places that are subsets of Containers. The types of boards available in your community are Forums, Knowledge Bases, Blogs, Ideas, and Events. Boards enable members to post content, write comments, and reply to other members’ comments. The process for creating a board is similar for all content types. To create a board: Go to the Community Structure page. Select Add (plus icon) at the level of the community where you want to add the board. On the window, enter a Name and ID. The ID displays in the URL for the board. Note: The ID must be a single word made of only letters, numbers, dashes, and underscores with no spaces. It cannot be changed later. Optionally, enter a Description and add an Avatar for the board. In the Tags area, specify the types of tags to use, add preset tags, and/or indicate whether you want to require tags for the board. Select Create. Related topics Community Structure Best Practices Community site structure hierarchy and terminology Manage Containers or Boards Container and Board permissionsAurora: Create community experience surveys
Admins can enable community experience surveys surveys, which prompt members to provide feedback about their experience in the community. Survey responses and scores can be collected via an export (see View community experience survey results). Create a survey Creating a survey requires several configuration steps, including designing the branding, designing its behavior, selecting its questions, and finally, turning it on for visitors. To access survey configuration options: Open the Account menu. Select Settings. Select Content Features. In the left column, select Community Experience Survey. Set up your survey: Design survey branding Design survey behaviors Select your questions Turn on the survey for visitors Design survey branding In the Branding area, select Edit. In the window, update the following as needed: Community name: The community name used in survey questions Brand name: The brand name used in survey questions Survey logo: Use a PNG or SVG logo; horizontal preferred. Text color Header background color: Used in the background of the survey header Select Submit. Design survey behaviors In the Survey Behaviors section, select Edit. Select whether you want to Present To: Signed-in members Anonymous users Both members and anonymous users (Optional) Select the role(s) you want to survey. (Optional) Select the role(s) you don’t want to survey. (Optional) Select the place(s) where you want the survey to be triggered. In the Frequency area, enter the number of Maximum responses to collect per month. This field sets the maximum number of surveys to collect for a given calendar month. After collecting this number of responses, no users will be prompted to take the survey until the first day of the following month. Enter a number of visits in the Present survey after this many visits field. This field sets the number of visits (0-500) to wait before prompting a viewer to take the survey. For example, if set to 3, the viewer isn’t prompted to take the survey until their fourth visit. Default = 0, which is the first visit. Enter a number of minutes in the Present the survey after this many minutes field. This field sets the number of minutes (1-60) to wait before prompting a viewer to take the survey after the defined number of visits have occurred. Default = 2. In the Conditions area, enter a number of days in the If declined/abandoned, repeat after this many days field. This field sets the number of days (1-365) to wait before prompting a viewer to take the survey after they’ve declined to take the survey. Default = 30. Enter a number of days in the If completed, repeat after this many days field. This field sets the number of days (1-365) to wait before prompting a viewer to take the survey again after they have already completed it. Default = 90. Select Save. Select your questions In the Questions and Answers section, select Edit. Use the toggles to turn on or off the questions you want to include or exclude on your survey, respectively. Some questions have follow-up questions based on the selected responses. Note: Because this survey is intended to gather important metrics and feedback, including CSAT (Customer Satisfaction Score), updating question titles and the order of questions is not permitted. Use the checkboxes by responses under your selected questions to designate which responses will be available for those taking the survey. Select Save. Turn on the survey for visitors After you have designed your survey the way you want it, you can enable it for your visitors by turning on the Community Experience Survey toggle at the top of the Community Experience Survey section.Aurora: Managing group members
Community Administrators and Group Owners can manage memberships from a group’s Manage Members page. From this page, you can: View group members Assign or edit group member's role Invite new members to the group Remove members from a group Manage pending invitations Manage requests to join Note: Group Inviters and Curators cannot access the Manage Members page. Inviters and Curators invite members using the Invite Members option in the Options menu. View group members Group members (who are not a group owner) can see a list of group members on the main Group page in the Members widget. To view group members in Manage Members page: Sign in to the community and go to a group. Open the Options menu and select Manage Members. The Manage Members page opens with the Members tab by default. Group members are listed along with their membership role and the date that they joined the group. You can sort this list by newest or oldest members or search for a specific member by typing a name in the filter. Change a group member's role Administrators and Owners can change a group member’s role. From the Manage Members page, click the Options icon > Edit Role next to their name in the list, select the role(s) to grant for the member, and click Apply. Invite a member to a group From the Manage Members page, members with the Send group invitations permission can invite other community members to join the group. To invite a community member to join a group: Go to the Manage Members page for a group. Click Send Invitation. Search for the member by entering their username in the To field. Select the Role to grant the person and enter a welcome note (optional). Click Send Invite. Remove a member from a group From the Manage Members page, Administrators and Owners can remove a member from a group. To remove a member in the Community UI: Go to the Manage Members page for a group. Click the Options icon > Remove next to the member you want to remove from the group. Click Remove to confirm. Manage pending invitations To manage pending invitations: Go to the Manage Members page for a group. Click the Pending Invites tab. For each member in the list, you can Resend or Cancel the invitation request. Manage requests to join For Closed groups, community members can request to join the group. You can manage these requests from the Manage Members page for the group. To manage invitation requests: Go to the Manage Members page for a group. Click the Requests tab. Accept or Deny each request in the list.Aurora: Configure Registration and Sign-In settings
The Account & Privacy page contains settings related to registration, sign-in, and sign-out. This article covers registration and sign-in settings. To learn about configuring SSO options, see Configure SSO settings for the community. Registration settings All anonymous users must register to participate in the community. To register, they must enter mandatory fields such as Username, Password, and so on. By default, the Registration window includes these fields: Admins and members with appropriate permissions can enable or disable these registration fields from the Settings page as needed. To edit registration settings: Sign in to the community as an Admin. Open the Account menu and click Settings. Go to System > Account & Privacy. Go to the Registration section and turn on/off these options: Enable member registration: Turns on or off the community member self-registration flow. By default, this option is enabled. This option is turned off for private and invite-only communities, where anonymous users are not allowed to register in the community. Add date of birth field to registration page: Controls whether the Date of Birth field appears on the Register window. Use Date of Birth to enforce the minimum age requirement: Toggle on this option to validate the date of birth provided by the user against the minimum age required for registration. Require users to confirm that they meet the minimum age requirement: Toggle on this option to add a field on the Registration window for the users to confirm whether they meet the minimum age required for registration. Set the Minimum age required for registration. As per the Children’s Online Privacy Protection (COPPA) rule, users must be at least 13 years old to register to the community. Auto-assign role upon registration: If you want to automatically assign a role to a new member when they register, click Edit by this option. In the field on the window, enter the role you want new members to be assigned. Terms of service acceptance required: Toggle on this option to add a field on the Registration window for the users to read and accept the Terms of Service (TOS). You can turn off this option if Single Sign-On (SSO) is used and you already have TOS acceptance as a requirement in the SSO configuration. Also, Admins can View/Edit Terms of Service in the required language. Learn more about editing the Terms of Service for the community. When all the options are turned on, the Register window looks like this: Sign-in Settings To edit sign-in settings: Sign in to the community as an Admin. Open the Account menu and click Settings. Go to System > Account & Privacy. Go to the Sign in section and turn on or off the Keep me signed in setting. When you turn on this setting, the Sign In window has the Keep me signed in checkbox selected by default for the member signing in.About Aurora roles and permissions
Your community uses permissions to determine the actions that your community members can take and which community areas and features they can access. Instead of setting each of these permissions manually, permission settings are grouped into roles and then you can assign these roles to members. Khoros provides a set of default roles. You can modify these roles (although we don’t recommend it) and create your own roles. You can also create a relationship between your community ranks and roles so that members get new roles and receive additional permissions as they advance through the ranks. Each role has a setting for each permission. When you define a role, you can set some permissions directly and leave the default settings for the rest. After you define your roles, you can set up the ranks in your community to assign (and remove) roles when members change ranks. The higher the rank, the more access it’s likely to grant the member. In addition to controlling member access within a community, you can also use roles to gather metrics on community usage or to establish criteria for gaining a rank. Although it’s more common to use a rank to grant a role, you can also use a role to assign users a rank. Some communities use this technique, for example, to assign a special rank to community moderators by using a role as the criteria for granting a rank. Similarly, you may want to create a role specifically for your employees. They might have the same permission settings as other community members, but you can use a special employee role as the requirement for a corresponding rank to identify them as employees to the rest of the community. Note: Groups use the default community roles as well as a set of roles specific to groups. Learn more in Group roles and permissions. Related topics: Create a role Default Community roles Permission descriptions Add members to roles Best practices: roles and permissions You can also receive self-paced training on roles and permissions in our Build Khoros Communities course.Aurora: Permission descriptions
Each Khoros community permission enables users to perform specific actions. These permissions are assigned (either by default or manually) to different community roles. Permissions are grouped by feature area on the node where you’re assigning them: Accepted Solutions Analytics Badges Blogs Boards Case Portal Categories Community Content Escalations Events Following Groups Ideas Inbox Knowledge Bases Likes Media Member Management Member Profiles Mentions Moderation SEO Tags Widgets A description and a recommendation as to the type of member who should be granted this permission are displayed by each of the permissions so you know exactly what you’re granting and to whom. You can set permissions globally or at the node level (category or board) in the community structure. For each permission, you can keep the out-of-the-box default setting or explicitly Grant or Deny permissions as needed. About permission levels Manage community permission defaults About permission levels Permissions can be set to Inherit, Deny, Grant, or Assign. Inherit – Person has the permission defined in the node or node-level role above the current level. Therefore, this level does not display when you’re managing community permissions defaults but does display for the category, group, and board levels. You can hover your cursor over the Inherit button to see whether the inherited value is Deny or Grant (the button is also displayed as red for Deny and green for Grant). Deny – Person does not have the ability to take action described by the permission. Grant – Person has the ability to take action described by the permission. Assign – Person has the ability to take action described by the permission and has the ability to grant the permission to other members. Typically, this should be given only to Administrator roles. If you look at the Administrator role, you'll notice that all permissions are set to Assign since Admins can grant permissions to other users. As a general rule, only Admins should be able to Assign permissions to others. There are a few use cases where this could change, but typically speaking, Administrators should be the only ones that have the ability to manage permissions in the community. The different permission levels cascade down to any nodes below them, but certain permissions at higher nodes will override lower-node permissions: Assign Overrides any other permissions given at lower-level nodes Explicit Grant Overrides Default Deny, Explicit Deny, and Default Grant at lower-level nodes Explicit Deny Overrides Default Grant and Default Deny but not Explicit Grant at lower-level notes Default Grant Overrides Default Deny but not Explicit Deny at lower-level nodes Default Deny Does not override anything at lower-level nodes Note: If there are conflicts within roles, the explicit exists to override the default. So for example, if you set a permission to Assign at a particular level, all levels below that for that permission will be overridden even if they are set to Deny (including if you manually/explicitly set it to Deny). Note: It is a community management best practice to modify permissions at a role level rather than at a user level to ensure consistency across the community. Manage community permission defaults Setting community permission defaults enables you to grant the base permissions for all members of the community. To manage community permission defaults: Go to Settings > Roles and Permissions. In the Community Permission Defaults section, click Edit. (Optional) To jump to a specific permission to manage, enter it in the Find a permission field. Set Deny or Grant access for the settings in each area. Each permission entry displays a description and recommended deny/grant status, as shown in this example:Aurora: Enable tags and set tag options
Many communities use tags to organize content that exists in different boards. Settings vary depending on where you are in the community. The tag options set for the community apply to all parts of the community, and you can later modify the settings at category or board levels based on your requirements.Aurora: Assign roles to members in bulk via CSV file import
To assign or remove a large number of roles for members at one time, you can use bulk import via a CSV file. Your CSV file needs to include the following for each member: “ADD” or “REMOVE” indicator Username or email address The roles you want added or removed To bulk assign or remove roles: Go to the Settings > Roles and Permissions page. In the Community Roles area, click Assign Roles in Bulk. On the Assign Roles in Bulk window, browse for the CSV file on your local machine. In the Charset drop-down menu, select the character encoding of the CSV file you’re importing. The default for Microsoft Windows operating systems is windows-1252 for most locales saved through Microsoft Excel. Click Start Assignment. Larger sets of member assignments may take longer to be imported. When the import is complete, you receive an email indicating whether it was a success or if there were any errors that need to be corrected. Related topics: Create a role Add members to roles
