The Profile element lets creators collect or update key profile information directly from learners when completing a topic. Depending on admin configuration, this includes default fields like first name, last name, email address, and custom fields.
This element is especially useful when learners have been added to the platform without complete profile data, for example, when they gain access through tokens/self-registration or are imported via a third-party integration.
Important!
This feature must firstly be enabled in your portal. Click here to learn more.
Be cautious when allowing learners to edit their profile details as their changes will replace any existing details on their profile. Be especially mindful of details such as name or email address as these may impact login and communication.
Expand the sections below to learn more.
Steps to add a Profile element to a topic
Steps to add a Profile element to a topic
Add the element to your topic by selecting the 'Profile' option from the Content box, then follow these steps:
Note: If the Profile element is not available, in the Content box, it means the feature has not been enabled in your portal. This feature requires a Super admin to firstly enable the feature, including specifying which default fields can be used, and secondly, enable 'Creator visibility' for any custom fields that should be available for use in the element.
Add instructions to explain why you're collecting this information and how learners should complete each field.
Select which fields the learner can populate:
Note: Only default and custom fields that have been made available for use in this element will be visible. See the next section for more information.First name
Last name
Email address
Custom fields
Optionally make completing all selected fields mandatory before learners can continue by enabling the 'Explorers must complete all fields before progressing' setting.
Click Save.
Tip: For 'list type' custom fields, learners will see all available options. If this isn’t appropriate, ask one of your portal admins to create a new list with only the needed options.
Which fields can be updated using the Profile element?
Which fields can be updated using the Profile element?
Creators can use the Profile element to request that learners fill in or update specific default and custom fields.
Default fields: If enabled by an admin, creators can request learners to update their first name, last name, and email. Learn how to enable the Profile element and configure default fields.
Custom fields: Creators can request learners to update any custom fields with 'Creator visibility'. Learn how to create custom fields and manage their visibility.
Why is the Profile element not available in the Content box?
Why is the Profile element not available in the Content box?
Before the Profile element can be used in your topics, a Super admin must activate the Profile element feature for your portal and select which default fields (first name, last name and email) can be used to populate or update profile data.
When creating custom fields, admins can also specify whether each field is or isn't available for use in the Profile element (by enabling 'Creator visibility').
Based on these initial admin settings, creators can then choose which fields learners can edit, and whether they must complete all selected fields to proceed.
How the Profile element works for learners
How the Profile element works for learners
When learners reach a Profile element in a topic, they’ll be prompted to complete or update the fields you’ve enabled.
They’ll see a form-style interface that may include text boxes (e.g. for name or email) and dropdowns (for 'list type' custom fields). Once they click 'Confirm profile', their profile will be updated immediately with the details they provide.
If you set the fields as required, learners won’t be able to continue until they’ve filled in all the requested information. If you leave this setting unchecked, learners will be able to proceed after completing just some or even none of the fields.
Important! This element is for updating profile data only. It should not be used as a general survey or opinion poll. Information provided will be used to populate or update fields on the user's profile.
Examples
Examples
The Profile element is typically used early in the learner journey to ensure accurate profile information is captured. Here are a few examples:
New user onboarding - Add the Profile element to the first topic a learner sees as part of their onboarding to capture their name, email, department, or location, especially if they joined through a third-party integration, purchase or self-registration.
Role-based training - If custom fields are used to define job titles, business units, or certification needs, use the Profile element to have learners select the option that best matches their current status.
Platform data clean-up - For organisations with incomplete user records, you can include this element to ask learners to update their profile directly, reducing manual admin effort.
Best practices
Best practices
Here are our recommended best practices for using this element:
Explain why you’re collecting this information to encourage completion and build trust.
Avoid overuse. This element is typically only needed once, usually at the beginning of a learner’s journey or to update incomplete profiles.
Coordinate with admins if you need custom fields to be editable in this element.