Summary
Choose how learners register on your portal. For self-registering learners, set up a trustlist, aka a whitelist, of email domains. Let learners permanently delete their data to meet data privacy requirements.
Users' general settings are available to all customers. The support team enables a trustlist (whitelist) on request.
Let users register themselves
Self-registration is different from an admin creating accounts, or inviting users by email. LearnUpon provides options to support genuine registrations, and minimize spam.
If you enable self-registration, you can also require users to
- confirm their registration by email (recommended): LearnUpon emails a link to the account, which they need to select to access their account
- complete a profile with at least a first and last name
- use email domains you consider safe by applying a safelist, also called a whitelist
Optionally: you can let learners add an image of themselves, to appear in place of their initials in their profile.
Tip: to track learners who register themselves, use the daily users created report, available from Settings > Email. This report lists learner accounts you create manually and self-registered learners, every 24 hours.
The users created report doesn't list accounts you create with batch user upload.
See: Users created and course completion automated reports.
Manage potential duplicate accounts
By default, when you create a user account in one portal, you can't create another account in a related portal, like a sub-portal or main portal, with the same unique identifier: email address or username.
If someone creates a second account with the same identifiers, LearnUpon's default behaviour is to ask the admin for the second portal to invite the user to join the second portal.
If you enable Allow user creation if user already exists? LearnUpon no longer requires an invitation but allows 2 or more accounts in related portals, using the same unique identifier.
This option lets users create their own accounts more easily, even if they already have an account in a related portal.
Note: the user's existing password is shared across any of your portals where they have an account. Users can only self-register with their original password. Where the portal jumper is available, the user can move between those portals.
See: Sub-portals: adding users to more than 1 portal for advice about setting up users across a realm.
General settings: how-to
- From main navigation go to Settings > Users > General Settings.
- From User account settings, enable the options required for your organization:
- Allow users to self register: provides a "Don't have an account? Sign up now" option on the login page
- Allow user creation if user already exists: allows a user to have accounts in 2+ related portals
- Allow profile images: lets users personalize their account with a photo
- Profile completion on login/access is mandatory: this option requires users to complete their profile on first login, including a first name, last name and any mandatory custom data fields on the portal
- If you enable Allow users to self register, another option appears.
- Require account confirmation: this confirmation step by email minimizes spam traffic. LearnUpon recommends you keep the confirmation requirement.
- Save to finish.
Enable a trustlist
For self-registering users, you can limit registration to addresses from selected email domains, to minimize spam. This list applies to self-registering users only. It does not affect users created or invited by portal admins.
LearnUpon enables the trustlist (whitelist) feature on request: contact the Support team to request it.
When enabled, a free-text field with the instruction Create a whitelist of email domains appears on the page. The field has a maximum of 255 characters, including punctuation.
- Enter a comma-separated list of email domains for your portal: enter the domain and suffix only, no @ symbol required.
- Save to finish.
The following screenshot shows a trustlist with sample entries.
Request permanent account deletion
Enable users to delete their own accounts permanently, to meet data privacy requirements, like GDPR's right to erasure. See User privacy: request permanent account deletion.
See: