About Aurora community languages
Reaching all your customers and enabling them to connect with each other is important regardless of the languages they speak. That’s why we offer the ability to translate your Aurora communities and email notifications into many different languages. The following languages are currently supported: Chinese (Simplified) zh-CN Danish da-DK Dutch (Netherlands) nl-NL English (Great Britain) en-GB English (United States) en-US French fr-FR German de-DE Italian it-IT Japanese ja-JP Korean ko-KR Latvian lv-LV Polish pl-PL Portuguese (Brazil) pt-BR Portuguese (Portugal) pt-PT Romanian ro-RO Russian ru-RU Spanish (Spain) es-ES To make any of these languages available to your members, refer to Enable languages in your community. Note: More languages will be available in future releases. Community members can update their Community language in standard communities or their Email language in localized communities in their member profile preferences. To learn more about the Localized Communities feature in which you can create segments of the community aimed at users of a particular language, refer to About Localized Communities, Create and map a localized category, and Configure localized category settings.Set community to offline mode
If you are performing maintenance on your community, you may want to prevent activity from taking place as you resolve issues. With offline mode, you can present a notice to visitors so they know maintenance is underway and that they cannot participate until the community comes back online. When the community is in offline mode, members cannot: sign in read content create new posts or reply to any content like posts, mark posts as solutions, tag posts, or edit posts reply to messages in their inbox or create new private messages follow or manage existing follows update their member settings Members can still receive email notifications if content is posted by admins during the time the community is offline. When the community is in offline mode, admins are still able to: sign in to the community post content modify site settings update the theme use back-end functionality such as APIs Enable offline mode Open the Account menu and go to Settings > System. Below General, toggle on Enable community offline mode. Confirm this action by selecting Take Community Offline. Customize your maintenance page You can customize the title and message on your maintenance page so that your visitors know what to expect when they reach your community while it is offline. To customize the message: On Settings > System > General, below Enable community offline mode, select Edit beside Title and Description. In the Edit Offline Text window, edit the Title and Description as desired. Select Save.Knowledge Base Article content widget configuration
The Knowledge Base Article template contains the Knowledge Base Article content widget that houses the body of an article. While you cannot delete this widget, you can modify some of its features to customize the community experience. Page item elements Date: Shows the date on which the article was published (September 3, 2024) or how long ago it was published (3 days ago) depending on your settings. Versions: A badge displays the version of the article. Helpfulness: Shows the “Was this article helpful?” section with sentiment emojis below the article. Guide navigation: In the left panel, shows the table of contents for the knowledge base guide where this article lives (see About KB Guides). Display contributors as None: No contributors are shown. Link: Select the View Contributors link to open contributors in another window. Detailed panel: The list of contributors shows below the article. Related topics: About Knowledge Bases About KB Guides Guides widget configurationAurora: Configure community guidelines
You can enable community guidelines for your community to ensure your members know what is expected of them in the community. These can be linked to an external URL or built within your Aurora community itself. You can designate your guidelines as required reading for registration or just provide a link on the registration window for new members. Depending on what you’re going for, building your guidelines within Aurora creates a seamless experience with consistent branding, while linking to an external URL enables you to use one central location where your document lives so you don’t have to update it in multiple places. For localized communities, you can provide guidelines in all your available community languages to ensure that all members of your community are aligned on expectations regardless of language. Provide link to guidelines on registration window Open the Account menu and select Settings. Go to System > Account > Registration. To add your guidelines to the registration window, turn on the Add community guidelines link to registration page toggle. (Optional) To require new members to select a checkbox indicating that they read and agree to the community guidelines, select Edit, and then select the Acceptance required checkbox. To designate whether you want to host the guidelines on your community or link to an existing page, select Edit, and then select Community or External. Set up guidelines on your community Whether your members reach your community guidelines from the registration window or elsewhere in your community, you can edit them from right within your community to ensure a seamless experience. After selecting Community, select Save. Select View/Edit Community Guidelines. On the Community Guidelines page that opens, select Edit Community Guidelines. Select a language from the drop-down menu. Select Continue. Enter your community guidelines. Repeat for your other community languages. Link to external community guidelines On the Edit Community Guidelines window, for all of your community languages, enter the URL to your community guidelines. Note: If you do not provide a URL for a particular language, members who select the community guidelines link while in that language are redirected to the community guidelines URL for your community’s default language. If the default language’s URL is also missing, members are redirected to the community-based guidelines page. Select Save.Aurora: Configure privacy policy
You can enable a privacy policy for your community to ensure your members know how your community collects, uses, and protects their personal data. Your privacy policy can be linked to an external URL or built within your Aurora community. You can designate your policy as required reading for registration or just provide a link on the registration window for new members. Depending on what you’re going for, building your privacy policy within Aurora creates a seamless experience with consistent branding, while linking to an external URL enables you to use one central location where your document lives so you don’t have to update it in multiple places. For localized communities, you can provide privacy policies in all your available community languages to ensure that all members of your community are aligned on security regardless of language. Provide link to privacy policy on registration window Open the Account menu and select Settings. Go to System > Account > Registration. To add your guidelines to the registration window, turn on the Add privacy policy link to registration page toggle. (Optional) To require new members to select a checkbox indicating that they read and agree to the privacy policy, select Edit, and then select the Acceptance required checkbox. To designate whether you want to host the guidelines on your community or link to an existing page, select Edit, and then select Community or External. Set up a privacy policy on your community Whether your members reach your privacy policy from the registration window or elsewhere in your community, you can edit them from right within your community to ensure a seamless experience. After selecting Community, select Save. Select View/Edit Privacy Policy. On the Privacy Policy page that opens, select Edit Privacy Policy. Select a language from the drop-down menu. Select Continue. Enter your privacy policy. Repeat for your other community languages. Link to an external privacy policy On the Edit Privacy Policy window, for all of your community languages, enter the URL to your privacy policy. Note: If you do not provide a URL for a particular language, members who select the privacy policy link while in that language are redirected to the privacy policy URL for your community’s default language. If the default language’s URL is also missing, members are redirected to the community-based privacy policy page. Select Save.Aurora: About Content Archive
Active communities, especially those of large enterprises, tend to have a lot of content. Over time, these communities can become cluttered with outdated, misleading, or obsolete content, making it more difficult for members to find the content they need. To keep content and conversations fresh and relevant, good content hygiene is important. Admins and moderators should regularly review site content and archive content that is no longer accurate, timely, or relevant. Aurora Communities include a Content Archive feature. When Content Archive is enabled, members with the appropriate permission can: Archive/unarchive knowledge base articles, blog posts, discussions, events, and ideas. Provide links to updated or related content in place of the archived content. Access all archived content from Manage Content dashboard . Note: You can archive only at the main thread. Individual replies or whole boards/categories cannot be archived. All user stats (likes, comments) achieved on archived content are retained. No notifications are sent to members when content is archived/unarchived. Admins and moderators can choose to send private messages to members as deemed necessary. Archival process Permissions Admins, moderators, or members with the Manage content archival permission can archive community content. Enable Content Archive feature To enable content archiving in your community, toggle on the Content archive option under Settings > Features > Moderation > Content Archive. Note: This feature is only set at the community level. Archiving content After the above mentioned roles or permission is granted and the Content Archive feature is enabled, members can see the Archive option from the Options menu on the content page. Select Archive to begin archiving the content. Below is an example from a discussion page. View archived content Admins and moderators or members with appropriate permissions can view all archived content from the Manage Content dashboard on the Archives tab. From here, they can unarchive, delete, or add a link to redirect users to related content.Aurora: Manage member account details
As your community grows, members may need help editing their usernames, email addresses, passwords, or SSO IDs, and admins may need to quickly adjust members’ assigned roles as requirements change across the community. With the Manage Members feature, admins and your company’s support team can edit these details within the admin area of Aurora. Note: To use this feature, your role must have the Manage roles and bans in admin & member profiles permission granted. Note: At this time, you cannot see a member's IP address until after they are banned. Refer to Review members banned from the community to learn how to view banned members' IP addresses. To edit existing member account details: Open the Account menu. Go to Settings > Users > Manage Users. In the Manage Members area, enter the Username or User ID (ID number or member profile URL) of an existing member. When you start typing a username, you can select the appropriate one from the list. On the Manage Member window, update the following as needed: Username Email address Note: If the existing email address has not been verified by the member, you can select the Mark email as verified checkbox to complete verification. If you change the email address here, it is automatically verified in the community. New password Roles (SSO members only) SSO ID Note: Be sure to update this field only when necessary, such as when SSO ID conflicts arise. Otherwise, the member may inadvertently create new accounts upon sign-in. Select Save.Preview published URL
Members who have access to the workflow page of an article, can preview the published URL (the final URL when published) on the workflow page of the draft. They can share this URL with others, who might need to link to this article when it’s published. To view the URL when the artilce or blog post is the in draft state: Open the draft of the article or blog post. Open the Options menu. Select Copy Published URL. The URL will be copied to your clipboard.Aurora: Create test accounts for troubleshooting
You may want to create test accounts to troubleshoot issues or test features in your community. Creating these accounts using the Add New Members feature gives you a secure way to quickly resolve issues your community members encounter without disrupting their experience. To create a test account: Open the Account menu. Go to Settings > Users > Manage Users. In the Add New Members area, click Add Member. On the Add Member window, enter the following information: Username Email address (automatically verified in the community) Password Roles (Optional) If you want to apply roles and settings from an existing account, turn on the Inherit roles and settings from existing member toggle and enter the Username or User ID of the account with the settings you want the new account to use. Select Create Member. Now you can use this account to sign in to the community.About 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 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 Types
