Aurora Community site structure hierarchy and terminology
This quick reference guide lays out the hierarchy and meaning of some of the site structure terminology in Khoros Community Aurora. Hierarchy Glossary Term Definition Blog Board that houses blog posts Blog post Individual post on a Blog board Board General term for lower-level Place that holds content; encompasses Blog, Event board, Forum, Knowledge Base, and Ideas board Category Highest-level Container in your community; can contain Groups and Boards Comment A top-level response to a post on a Board Container General term for higher-level Place that houses Boards; encompasses Category and Group Content Collective term for posts (for example, “Our community contains a lot of content about our products.”) Content Type General term for the style of content that coincides with the Board types: Blogs, Events, Forums, Knowledge Bases, Ideas Discussion Individual post on a Forum Event board Board that houses events Event Individual post on an Event board Forum Board that houses discussions Group Higher-level Container that enables community members to engage around a common theme or purpose; can contain Boards of one content type Ideas board Board that houses ideas Idea Individual post on an Ideas board Knowledge base Board that houses knowledge base articles Knowledge base article Individual post in a knowledge base Place General term that encompasses Containers and Boards Post General term for an individual piece of content if type is irrelevant; encompasses blog post, event, forum discussion, knowledge base article, idea (for example, “If you want to make a post in our community, sign in first.”) Reply A response to a comment Related topics: About Community site structure Community Structure Best PracticesAbout 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 out-of-the-box community roles
At launch, new communities normally have several default roles. You can add more roles as needed as your community grows. Members who join the community are automatically given the permissions granted in the Community Permission Defaults (see Permission descriptions); the out-of-the-box roles defined here either grant a member permissions additional to (or different from) the default ones or offer a way to designate that a member belongs to a specific group. Note: Roles are still being researched and developed. These may change in future releases as we add more features. Role Permissions Administrator All permissions in the system as well as the ability to grant permissions to other users. Khoros This role is used to indicate that a member is a Khoros employee but does not give any permissions different from the default set. Moderator Permissions that enable moderators to manage members and posts, including updating, moving, and deleting posts in the community. Analytics Permissions to access the Community Analytics area for Aurora. Blog Author and Blog Moderator Permissions that enable the member to do the following: Update boards Start topics Publish, update, or delete posts Upload file attachments BlogAuthor Permissions that enable the member to do the following: Start new posts Manage comments on own posts Comment on posts KBAuthor Permissions that enable the member to do the following: Create, edit, publish, and manage articles Delete one's own articles Although these roles are intended for new communities, you can continue to use them as your community matures. For well-established and active communities, however, even the most restrictive roles have more access than you might want to give beginners. As a result, one of the most common roles that many communities create is one that limits access for brand new users (newbies). This role is typically assigned using a rank (coming in a later release) that new users automatically receive as soon as they join the community. It’s also a rank that users can grow out of quickly, so the requirements for the next higher rank, where users acquire additional permissions and drop the newbie role, are typically lenient. You can create your own roles with permission sets that fit the needs of your community. Related topics: Create a role Assign roles to members Permission descriptionsAurora: Move, reorder, or delete containers or boards
You can move, reorder, or delete containers or boards from the Settings > Community Structure page. Move or reorder a container or board On the container or board you want to move, click Settings(gear icon). Click Move. On the Select New Location window, click the new location of the container or board you’re moving. Note: If there are a lot of possible locations, you can search for the desired one in the search bar. Click Continue. Drag the container or board to the desired position within the location you chose. Delete a container or board On the container or board you want to delete, click the gear icon. Click Delete. On the window that opens, confirm the deletion. Permissions The following permissions are required for the above tasks. By default, these are set toDenyfor all community membersexcept for those with the Admin role. To move categories, a member must have theMove categoriespermission. To move boards, a member must have theMove boardspermission. To delete categories, a member must have theDelete categoriespermission. To delete boards, a member must have theDelete boardspermission. To move groups, a member must have theMove groupspermission. To delete groups, a member must have theDelete groupspermission.Aurora: Delete a group and sub-groups
Group Owners and Community Administrators can delete groups. Warning: Deleting a group permanently deletes all of the content, membership, and settings associated with the group. The action cannot be undone. No notification is sent when a group is deleted. Delete a group in Community UI Delete a group in Community Admin Delete a group in Community UI Sign in to the community and navigate to the Group 9age for the group you want to delete. From the Options menu, click Edit Info. In the Edit Grouppage, go to the bottom left of the page and click Delete Group. Click Delete Groupin the confirmation modal. The group is deleted and you are returned to the group parent page (the top-level Community page or the parent Category page). Delete a group in Community Admin Go to Community Admin > Community Structure. Navigate to the group you want to delete. Hover your cursor over the group and select Delete. Click Delete Place to confirm. The group is deleted. Note: You cannot delete the boards with in a sub-group.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, seeConfigure 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.Aurora: Change your community's name and SEO Information
If necessary, an admin can change the community’s name. Additionally, they can also SEO information. Open your account menu and go to Settings > Community Structure. In the structure tree, in the row of the community level, click the gear icon. On the Edit Community Info window, enter change the community name in the Community name field enter or change SEO related information in the SEO title and SEO description, ClickSave.Aurora: Using the Audit Log
The Audit Log enables admins to see who has taken what kinds of actions—and when—across the community. These are typically initiated by admins and other community members, but they may also come from the system itself. Some of the actions captured in the audit log are deleted or moved posts, added or changed roles, added or changed custom content, settings changes, and much more. Sign in to the community as an admin. Go to Settings > System > Audit Log. View the Date, User, Action/Comment, and IP of admin actions taken in the community. The number of entries is displayed at the top right above the table. Note: If the Switch Member feature was used to complete an action, the Audit Log gives the name of the member who switched to another member, the name of the member they switched to, and the actions they took while acting as another member. Note:If a Khoros Support user logs in, the Audit Log User column says SYSTEM, but the Action/Comment explains that a Khoros Support user logged in to review a case. (Optional) Use the arrow buttons at the bottom of the page or use the following filters to find specific actions: Date Range Last 24 Hours Last 7 Days Custom Date Range (enter a date range and click Set Date Range on the window that opens) User: Enter a username in the field. (Optional) Click Export to the Audit Log to CSV. If you’ve selected specific filters, these are applied in the export.
