Appreciation Days
Wikipedia saysCommunity Manager Appreciation Day takes place every 4th Monday of January. When I Google Moderator Appreciation Day I get different results, but if it's there, I couldn't find one day everyone has agreed to. And Super User Appreciation Day shows me the day for Sys Admins. My point: I am grateful every day to our team of moderators, who are the ones who really keep our community going, and usable. And our Stars, who keep coming back to help us out, and help so many of our users. Are there official days for these two groups of amazing human beings? And if not, where would be a good, visible, central, community-focused place to bring this up, get a vote going and make these official?Aurora: Hide places and content from lists, menus, and search
In the community, you can hide any place (board or category) or posts related to a board (Forum, Blog, Knowledge Base, Event, and Ideas) from lists, menus, and search. Doing so hides the places and content from appearing in your community structure but still keeps them available to members via direct link to the content. To prevent search results from boards being directly accessible, you’d need to make the board private. Hide a place from appearing in lists, menus, and search Let’s take an example where you want to hide a category from appearing in the community place widgets, place picker menus, and search results. To hide a category: Open the Account menu and go to Settings > Community Structure. In Community Structure, click the category you want to hide. Go to Display Settings and toggle on Hide category in place widgets, place picker menus, and search. Similarly, to hide a board, you can go to the specific board and toggle on this setting: Hide content from appearing in a category, community content widgets, and search results Let’s take an example where you want to hide discussions in a specific forum from appearing in a category, community content widgets, and search results. To hide forum content: Open the Account menu and go to Settings > Community Structure. In Community Structure, click the forum you want to hide. Go to Display Settings and toggle on the Hide forum posts in content widgets and search. Similarly, you can hide Blog posts, Knowledge Base articles, individual events, and individual ideas of the respective boards from appearing in the category, community content widgets, and search results.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 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 PracticesAurora: Replace community tags
Over time, tags associated with community content may become irrelevant, misspelled, or redundant. You can replace these tags to make more sense and make it easier to find relevant content. From the Tags tab in the Manage Content dashboard, Admins and members with theManage Tags permission can replace the tags. After you replace a tag, the new tag is reflected in posts that used the previous tag. Key points to understand before replacing a tag: If the tag is associated with posts that are part of boards supporting preset-only tags and the replacement tag is part of the preset tags list, the tag is replaced in these posts.If the replacement tag is not part of the preset tags list, only admins can replace the tags in these posts by selecting Replace tag in the posts from the above boards option: When you replace the tag, the new tag is added to the preset tag list in the respective preset-only boards. Non-admin members (with theManage Tags permission) cannot replace the tag and can only view a list of these preset-only boards: After replacing the tag in posts that are part of preset-only boards, admins can remove the old tag from the preset tag list of these boards by selecting the checkbox: A preset tag in a post can be replaced by a freeform tag if the board supports both preset and freeform tags. To replace a tag: Sign in to your community as an Admin or a member with Manage Tags permission. Open the Account menu and click Manage > Tags. In the row of the tag you want to replace, open the Options menu and click Replace. On the Replace Tag window, either enter the replacement tag name or select an existing tag. Click Replace. The new tag is reflected in the associated posts across the community.Aurora: Configure File Attachment settings for the community
You can configure settings that define how members can upload file attachments to different areas of the community. These settings apply to all content types. Note: These settings can also be adjusted at the board level. To configure the file attachment settings: Go to Admin Settings > Features > Content Features. Scroll down to File Attachments. Click Edit to configure the following settings: Maximum number of attachments per post – Enter a number or use the arrows to indicate the maximum number of attachments members of the community can upload. File extensions for attachments – Enter the file extensions to be accepted in the community. Separate file types with a comma. If you do not enter anything here, default file types (JPG, GIF, and PNG) will be used. Maximum attachment file size for upload (MB) – Enter a number or use the arrows to indicate the maximum file size members of the community can upload. Click Save.About the Brightcove video hosting service used with Aurora
Videos uploaded to a Khoros community are hosted by Brightcove. Note: Video upload is a paid feature. To learn whether Video Upload is included in your package or costs extra as well as request to have it enabled for your community, contact your Khoros Account Executive. To learn more about Brightcove video hosting capabilities and usage restrictions, refer to your Brightcove usage contract. This article answers some of the most common questions we get about the Brightcove integration. What video formats are supported? When you upload a video to Brightcove, Brightcove automatically transcodes it using the settings specified for your account and makes the videos available for playback through your player. We recommend that you upload videos to Brightcove in H.264. However, you can also use these commonly used file formats: Video Codecs: MPEG-1, MPEG-2, MPEG-4, VP6, VP5, H.264, H.263, WMV/WMA, and MJPEG. Audio Codecs: AAC, MP3, WMA, MPEG-1, MPEG-2, WAV, ADPCM. Learn more about supported formats on Brightcove's FAQ. What format are the videos served in? Videos are served in HTML5 format. Is there any limit to the number of videos that can be uploaded? With regard to the total number of videos that can be uploaded to your community, there is no limit. Is it possible to pre-moderate videos members upload? Yes, for members whom you trust will not upload inappropriate content, you can grant them the Bypass video moderation permission under Settings > Users > Roles and Permissions. By default, this permission is denied. Is there a concurrent views limit? No; however, there is a limit to the total number of streams/views per month. How many streams/views are allowed per month? Our standard package includes 120,000 streams per year. If you expect to regularly go over this threshold, contact your customer account manager to discuss options/costs for increasing this limit. What happens if I exceed more than 10K video views per month? If you exceed your monthly views limit, videos will still play for your members; however, your account will be charged for the additional views (similar to going over your data plan on your cell phone monthly plan). If you expect to regularly go over this threshold, contact your customer account manager to discuss options/costs for increasing this limit. What is the size limit for any single video? The largest file size (the maximum is 10,000,000 KB) that users can upload at any one time. As the Community Admin, you can set the maximum size under in your video options, described here. Learn more about Brightcove's video size limits. Is mobile supported? Yes, video playback is supported on mobile. Brightcove says I can use "up to 2 video encodes." What does that mean? With the Khoros/Brightcove integration, you can upload virtually any kind of video to Brightcove. The first thing Brightcove does is convert/encode that video to a suitable format for streaming. This means that that they might take your video and save multiple versions of it: one that’s small and highly compressed for viewing on phones one that’s larger but still compressed for viewing on desktop computers one that’s very large and only lightly compressed for HD viewing on high-bandwidth connections When visitors view your video, Brightcove determines which of these is optimal to stream to them based on what kind of device and connection the viewer has. In this example, there would be “3 encodes.” It’s about how many optimized copies of each video Brightcove stores so that each visitor gets the best video experience for the device they're using, not about the number of videos you can upload. Your Brightcove-Community integration supports up to 2 video encodes per video.Aurora: Best practices: roles and permissions
When you first launch a community, permissions and roles are fairly easy to manage because there are a limited number of roles, ranks, and members. As your community grows, you will need to add new ranks and roles to further segment your membership and reward the most active participants. Although you can set individual member permissions one at a time (not recommended), Khoros Communities are designed to help you manage permissions through a hierarchy of roles at the community, category, and board levels. The advantage to this approach, aside from the obvious reduction in the sheer number of moving parts, is a more predictable and manageable permissions structure. The cornerstone of this structure is a link the system creates between roles that have the same name, but that exist at different levels in the community. When you assign roles to members at the community level, they automatically inherit membership in roles that have the same name at the category and board levels. The settings for the new board-level role are stored with those of the higher-level role. Best practices for working with permissions and roles Keep it simple, especially when first launching your community. In the early days of the community, before your active members emerge, you can get by with just a few default roles (Administrator, Moderator, and Khoros or community defaults). At this stage, you want to encourage participation by making it easy for new members to sign in and start posting. You can add roles later as you need them. Set your community-level defaults to the lowest common denominator in terms of access. These defaults apply to all new community members at all levels of the community and are typically the most restrictive settings. As members gain experience in the community and advance up through the ranks, you can give them additional permissions through roles that explicitly grant access. You can always override these defaults with role-based settings at the category or board level. Create roles at the community level, and then create category- or board-level versions of the same roles if you need them. The purpose of a category- or board-level role is to override the community-level settings for a specific category or board. Members who have the community-level role also get the permission settings from the lower-level roles. The names of the roles at all three levels must be exactly the same—including capitalization and spacing—for the connection between roles to work. For example, “Vip” and “VIP” are not the same. The lower-level settings apply only when members are at that level. For example, a category-level permission applies only to members in that category. Elsewhere in the community, community-level permissions are in effect. Always assign roles at the community level rather than at lower levels. This enables you to manage roles and permissions from a single location rather than having to go to each category, for example, and listing the members who have a role assigned to them. Members get the access allowed by the community-wide settings as well as the category-level or board-level override settings for specific categories or boards. The category- or board-level roles typically give members access to areas or features that are off-limits to the rest of the community. Always use roles to assign permissions. The system is designed to track membership in a role, not individual permission settings. As a result, you can easily determine which roles a member has or which members are assigned to the same role. While you cannot assign permissions to individual members, you can look up which roles & permissions are assigned to a particular member (see Look up a member's roles and permissions.) Observe these general tips: Configure permissions and roles to the Principle of Least Privilege. (Apply only the minimum required permissions for a role.) Change permissions within roles only where the default, inherited permission doesn't suffice. For each role, fully document the function of each role, its included permissions, and its purpose and location (for example, if it exists at child levels of community). Provide these details in the role description. Use an informative and consistent naming convention when creating roles. Clear and concise role names make roles much easier to scan and manage and enable new admins to intuit the meaning/purpose of a role.
