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: Provide a registration link in your community
In Aurora Communities, admins can either provide a registration link in the community or send email invitations directly to prospective members. You can use this setting whether you have a public community or a private community, although it is more commonly enabled for public communities (to make your community private, contact your account representative, as this cannot be managed in the application). To manage the Enable member registration setting: Go to Settings > System > Account & Privacy. In the Registrationsection, turn on or off the Enable member registration setting as desired. With this setting enabled, the Sign In window provides a Register Now link at the bottom that prospective members can click to begin the registration process: If the setting is not enabled, the Register Now link does not appear on the Sign In window. Instead, prospective members must be invited via email by an admin of the community in order to register.Aurora: Manage avatar permission settings (admin)
As an admin, you can manage the permissions for Avatars. The permission for a member to upload their own avatar is enabled by default to all community members. To manage the ability for community members to upload their own Avatars: Note: To manage this permission for a particular role, go to the Permissions page at the community level and edit the permissions of the individual roles. Go to the Roles and Permissions page for the community. Beside Community Permissions Defaults, click Edit. In the left column, click Member Profile. In the Member Profile section, to manage whether a member can upload their own avatar, beside Upload own avatar, click Deny or Grant as required. To manage whether a community member can select an avatar from your community collection, beside Choose avatar from collections, click Deny or Grant as required. Unless you have specified different permissions for certain roles, this selection affects all members of the community.Aurora: View and edit Terms of Service (TOS)
The Terms of Service (TOS) define the rules and guidelines that members must follow to participate in the community. When people register with the community, they must read and agree to the TOS. Your TOS may change due to updates in the community rules and guidelines. Admins and members with permissions can review and edit the TOS for the selected language from the Settings page as required. To review and edit Terms of Service: 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. Below the Terms of service acceptance required option, click the View/Edit Terms of Service link. The Terms of Service page is displayed, where you can review the existing terms and conditions. To edit the TOS, click Options menu > Edit. On the Edit Terms of Service window, select the language from the drop-down menu and click Continue. The editor window opens for the selected language. Update the content and click Save. The Terms of Service page for the selected language is updated successfully. Note: From the Register window, Admins can click the link and easily access the Terms of Service page by signing in to the community:Aurora: Enable read-only mode for community places
From time to time, you may need to lock down areas of your community for standard maintenance or updates. Or, you may want to temporarily restrict people from creating new content in specific categories, boards, or the entire community. By putting community places in read-only mode, you can enable members access to still view community content but restrict them on making any changes to this content. You can enable read-only mode at the community, category, or board level to restrict members from posting new content or editing existing content. Read-only mode does not apply to admins and moderators; they can perform their respective actions as normal. Read-only mode is commonly used for these reasons: Community:Standard site maintenance where site activity could interfere with the site updates or when a community is under a security threat. Category:For categories dedicated to broadcasting information and does not require members to post any content. It can also be used to temporarily or permanently make a category read-only. Board:For boards that are dedicated to broadcasting information and does not require members to post any content. It can also be used to temporarily or permanently make a board read-only In addition to the above scenarios, admins and moderators can enable read-only mode on a case-by-case basis based on their specific needs. Note: We recommend this setting only for specific cases as it highly impacts the member site engagement. You should also let your members know why a community place has been temporarily placed in read-only mode. What to expect in read-only mode In read-only mode, members can: View, like, or report inappropriate content Send private messages to other members Tag their own content In read-only mode, members cannot: Create new content Edit or delete existing content Add comments or replies to content Tag others’ content Move content to another location Note: Members are blocked from performing the above actions even if they have appropriate permissions. Enable read-only mode at the community level Open the Account menu and go to Settings > Content Features. In the General section, toggle on the Read-only mode option. Configure read-only mode at the category, group, or board level When read-only mode is enabled at community level, it is inherited at the category, group, and board levels. You can override the setting at lower levels as needed. Let’s look at an example where read-only mode is turned off at the community level and you want to enable it in a specific category. To enable read-only mode for a specific category: Open the Account menu and go to Settings > Community Structure. In theCommunity Structure, click the category where you want to enable read-only mode. Below Content Features, toggle on the Read-only mode option. Similarly, you can configure read-only mode at group and board levels.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.Edit the Aurora community email sender name and address
The Aurora Community sends emails for a variety of notifications (see About Email Notifications). You can specify the sender name and email address for these emails. For example, emails are sent from “Community Mailer” and “mailer@us.khoros-mail.com” by default. You can change this to something better tailored to your brand, such as “Acme Community” and “notifications@mailer.acme.com.” Before editing Khoros strongly recommends creating and using a new subdomain for community-related emails to host all relevant DNS records. This facilitates configuration of our recommended SPF (sender policy framework) records. An SPF is a type of DNS TXT record that lists all servers authorized to send emails from a particular domain. For more information on your SPF setup, contact your IT team. Since Khoros does not support sender addresses that share a domain with your community or with your company top-level domain, such as “something@acme.com,” we recommend you use a sender address like “@mailer.acme.com,” or even just “@m.acme.com.” The sender address must be able to accept reply and bounce emails. No-reply type addresses are acceptable as well, but to prevent undeliverable messages from creating further bounces and clogging up the Khoros mail systems, they must still have a valid MX record and accept all mail, then delete the reply afterwards. Edit community name and email address Go to Settings > Features > Inbox > Email. Click Edit. Enter the Mailer Sender Email Address and Mailer Sender Name to display in the “From” field on email messages. Click Save.
