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.ViewsSign in to react to this postCommentsAbout Content permissions
You can adjust permissions related to content at the community, container (category & group), and board level. Some permissions are set to Deny by default while others are set to Grant by default. At the container level and the board level, permission defaults and role permissions are inherited from the parent level. In those cases, the Inherit button is displayed in green to indicate that the permission was set to Grant at the parent level or red to indicate that the permission was set to Deny at the parent level. As an admin, you can manage these permissions. To manage content-related permission defaults at the community level: Note: To manage this permission at a lower level, go to the [Place] Permissions page and edit the permission defaults for that level. To manage this permission for a particular role, go to the [Place] Permissions page at the desired level of the community and edit the permissions of the individual roles. Go to the Roles and Permissions page for the community. Beside Community Permissions Defaults, select Edit. Review permissions in the following areas: Blogs Content Events Ideas Knowledge Bases Select Deny or Grant as required. Unless you have specified different permissions for certain roles or levels below the community level (a category, group, or board), these selections affect all members of the community. Content permissions While Forum permissions are granted by the Content permissions, Blogs, Event Boards, Ideas boards, and Knowledge Bases have distinct permission sections for content type-specific tasks. The Content permissions are provided for general content access and tasks and relate to all content types. Follow the links in the table below to learn more about the tasks granted by these permissions. Permission Default Related permissions in content type sections Read discussions and content Grant Blogs: Read posts and Read comments Ideas: Read ideas and comments Reply to discussions and content Grant Blogs: Comment on posts Events: Comment on events Ideas: Comment on ideas Knowledge Bases: Comment on articles Start discussions and new content Grant Blogs: Start new posts Events: Post new events Ideas: Post new ideas Knowledge Bases: Create, edit, publish, and manage articles Edit own posts Deny Blogs: Edit own published posts Events: Edit own events Ideas: Manage ideas and comments Knowledge Bases: Edit own published articles Edit any post Deny Blogs: Edit any published post Events: Edit all events Ideas: Manage ideas and comments Knowledge Bases: Edit any published article Move content Deny Blogs: Manage any posts and Manage own posts Delete own post Deny Blogs: Manage own posts Events: Delete own events Knowledge Bases: Delete own articles Delete any post Deny Blogs: Manage any posts Events: Delete all events Ideas: Manage ideas and comments Upload file attachments Deny Embed external content Grant Turn on link hyperlinking Grant Use simple HTML in posts Grant Use advanced HTML in posts Deny Use full HTML in posts Deny Make content read only Deny Post read-only content Deny Bypass moderation Deny Blogs: Bypass comment moderation Events: Bypass comment moderation Ideas: Bypass moderation Knowledge Bases: Bypass comment moderation Related topics: About Aurora Community site structure About Aurora Content TypesViewsSign in to react to this postCommentsAurora: 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 rolesViewsSign in to react to this postComment
Not receiving user email addresses from search endpoint
I have a script that queries the search endpoint for information about Khoros users. The API call looks roughly like /api/2.0/search?q=SELECT id, email FROM users LIMIT 10 When developing this script against one Khoros installation, I found that the Khoros user associated with the API request needed to have several "User Management" permissions granted to it in order to receive email addresses via this API call. (In particular, granting "View user reports in Admin Metrics", "Manage roles, user bans, and abuse notifications in admin and user profiles", and "Manage roles in user profiles" seemed to be sufficient.) However, when running this script against a second Khoros installation, I am not receiving back any email addresses. Every single user returned has the empty string as their email address, and I've tried querying several hundred (all of whom should have emails). For instance, a response may look similar to the below (redacted) sample: { "status": "success", "message": "", "http_code": 200, "data": { "type": "users", "list_item_type": "user", "size": 10, "items": [ { "type": "user", "id": "1000000", "email": "" }, ...additional users removed for brevity... ], "next_cursor": "AbCdEf" }, "metadata": {} } I have double-checked the roles and permissions for the Khoros user I'm using for this API request. What's the best way to debug? What are some other reasons that I may not be receiving any email addresses?ViewsSign in to react to this postCommentsAurora 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 descriptionsViewsSign in to react to this postCommentsAurora: Create a role
Aurora provides several out-of-the-box roles, but you can also create your own to fit your community's needs. Roles can be added and edited at the community level, the group or category level, and the board level. Create a new role at the community level Sign in to the community as an Admin user and go to Settings > Users > Roles and Permissions. Click Add Role. On the Add Role window, enter an ID. Note: The role ID cannot be changed later. (Recommended) Enter a Description of the role. Click Save. The Add Role window closes, and the newly created role is displayed in the list on the page. Open the Options menu for the role and click Edit to adjust the permissions (Inherit, Deny, Grant, or Assign) for the role as necessary. Note that choosing Inherit leaves the permission set to the community default as indicated on the tooltip for that permission. After creating a role, you can also clone or delete it as necessary. You can also add members to the role. Create a new role at the category level Sign in to the community as an Admin user and go to Settings > Users > Roles and Permissions. Open the desired category from the place picker. On the Category Permissions page, by Category Roles, click Add Role. Alternatively, if you want to create roles for group that will be contained in this category, click Add Group Roles, found by the Group Roles section. On the Add Role window, enter an ID. Note: The role ID cannot be changed later. (Recommended) Enter a Description of the role. Click Save. The Add Role window closes, and the newly created role is displayed in the list on the page. Open the Options menu for the role and click Edit to adjust the permissions (Inherit, Deny, Grant, or Assign) for the role as necessary. Note that choosing Inherit leaves the permission set to the community default as indicated on the tooltip for that permission. After creating a role, you can also clone or delete it as necessary. You can also add members to the role. Create a new role at the board level Sign in to the community as an Admin user and go to Settings > Users > Roles and Permissions. Open the desired knowledge base, blog, ideas, or forum from the place picker. On the Permissions page for the knowledge base, blog, ideas, or forum, click Add Role. On the Add Role window, enter an ID. Note: The role ID cannot be changed later. (Recommended) Enter a Description of the role. Click Save. The Add Role window closes, and the newly created role is displayed in the list on the page. Open the Options menu for the role and click Edit to adjust the permissions (Inherit, Deny, Grant, or Assign) for the role as necessary. Note that choosing Inherit leaves the permission set to the community default as indicated on the tooltip for that permission. After creating a role, you can also clone or delete it as necessary. You can also add members to the role. Related topics: Out-of-the-box community roles Add members to roles Permission descriptionsViewsSign in to react to this postCommentsAurora: Clone a role
If you want to create a role that is nearly identical to a previously created role, you can clone the previously created role and its permissions, then change it as desired. You can perform this task at the community, category, group, or board level. To clone a role: Sign in to the community as an Admin user and go to Settings > Users > Roles and Permissions. On the Roles and Permissions page for the community, a category, a group, or a board, hover your cursor over the role you want to clone, then click the Options icon (ellipsis). In the Options menu, select Clone. On the Clone Role window, enter an ID. Note: The ID cannot be changed later. (Recommended) Enter a Description for the role. To copy the members from the previously created role to the cloned role, turn on the Also copy members option. Click Save. The Clone Role window closes, and the newly cloned role is displayed in the list on the Community Roles page. You now have the ability to clone or delete the role.ViewsSign in to react to this postCommentsAurora: Delete a role
If you no longer need a particular role, you can delete it from your community, a category, a group, or a board. On the Roles and Permissions page for the community, a category, a group, or a board, hover your cursor over the role you want to delete, then click the Options icon (ellipsis). In the Options menu, click Delete. On the Confirm Delete window, click Delete. Click Save. The Confirm Delete window closes, and the role no longer displays in the list on the page. Related topics: Create a role Clone a roleViewsSign in to react to this postCommentsAurora: Add members to roles
You can add community members to any of the default community roles or the roles you've manually created. A member's assigned role determines what they can and cannot do in the community. You can also assign roles to members from the Member Permissions page as described in Look up a member's roles and permissions. To add members to roles: Note: To add members to a role at a lower level, go to the [Place] Permissions page at the desired level of the community and then add members to the role. Sign in to Aurora as an Admin user and go to Settings > Users > Roles and Permissions. On the Community Roles and Permissions page, click Options menu of the role to which you want to add members and click Edit. On the Edit Role page, click Add Members. On the Add Members window, in the Members field, enter the name or the username of the member to whom you want to assign the role. In the drop-down menu, select the member. Repeat steps 4 and 5 to continue adding members. Note: To remove a member, click the X icon next to their username. Click Save. Note: You can manage the roles assigned to individual members from their member profile page. Learn more about managing member roles. Related topics: Import members from a CSV fileViewsSign in to react to this postComments
348Views
0Comments
