Maintain User Profiles and Information - Article
Summary
User information can support onboarding, audience selection, communication, reporting, and personalization. Dependable maintenance requires more than editing a visible field: administrators must know which source owns the value, who is permitted to change it, and which separate rule or record uses it.
Use this article to:
- Maintain persistent user information for a clear business purpose.
- Distinguish manual edits from imports, SSO, integrations, and questionnaires.
- Protect organization, role, manager, identity, and consent boundaries.
- Verify the result without confusing profile data with Transactions or learning evidence.
Treat profile information as governed business data
Profile fields can help identify users, select audiences, provide organizational context, prefill forms, and support reporting. The profile value alone does not perform every downstream action. Activity settings, organization rules, integrations, and other features determine how the information is used.
For example, changing Department can affect which audience rules match the person, but it is not proof that an enrollment occurred. Adding an organization relationship can change administrative scope without making every activity visible. Verify both the profile information and the business rule that consumes it.
Open and edit the intended profile
- Open Users and search for the person.
- Confirm the account using dependable identifiers, especially when names or email addresses are similar.
- Check organization membership, role, status, and sign-in context when they matter to the request.
- Select Edit and open the tab required for the task.
Visible fields and tabs depend on role, organizational scope, enabled features, the Profile form, and the account being reviewed. Permission to view a value is not automatically permission to edit it.
The Profile form is configured under Settings → Forms → Profile. That article is the canonical field catalogue and explains how Profile, Signup, Create user, Login, Enroll, Contact, and Activity tags differ.
Organize information by purpose
| Information area | Use it for | Important boundary |
|---|---|---|
| Identity and contact | Recognizing the account and communicating with the person. | Check account matching before changing Email or Username, especially for connected identities. |
| Business and employment | Segmentation, operational context, onboarding, and reporting. | A descriptive value is not automatically a verified relationship or permission. |
| Organization membership | Managed customer, partner, subsidiary, or business-unit relationships. | Membership is different from a free-text Company value and from learning enrollment. |
| Role and manager relationships | Administrative responsibility and staff oversight. | These values can change access or management scope; treat them as authorization decisions. |
| Preferences and interests | Language, time zone, notification level, and supported discovery preferences. | Available translations, schemes, and organization-specific tags still determine the result. |
| Learning and achievement links | A route to training, Skills, Certificates, and transcripts. | Use the activity, Certificate, Skill, or report as the evidence for the achievement itself. |
| Legal permissions | Recorded privacy-policy acceptance and supported questionnaire consent. | Visibility does not authorize someone to provide or change another person’s consent. |
For the user-facing purpose of each profile area, see Use Your Profile and Account Settings.
Decide which source owns each field
Before introducing a new update process, agree which source is authoritative for each important value.
| Source | Typical use | What to verify |
|---|---|---|
| User or authorized manual edit | Personal information or controlled corrections maintained directly. | Correct account, field editability, and organizational scope. |
| User import | Controlled creation or maintenance of a defined population. | Identifier, current template, overwrite behavior, and treatment of existing values. |
| SSO or integration | External identity, employment, membership, or other agreed business information. | Source of truth, mapping, synchronization timing, and departure handling. |
| Questionnaire | Authenticated collection of supported profile fields or contextual supplemental information. | Whether the question writes to a profile field, who submits it, and whether it can replace an existing value. |
| Organization or manager relationship | Administrative scope and staff oversight. | The actual relationship between accounts, not only a descriptive field. |
If a corrected value later returns to its earlier state, identify the next import, login mapping, integration update, or questionnaire submission before editing it again.
Control field editability and delegated maintenance
The Profile form can allow end users to edit supported fields. A separate role configuration can allow selected administrative roles to edit fields that are disabled for the user. Access still depends on the role, organizational scope, and source ownership, and it does not override SSO-locked values.
Use delegated editing where the operating model supports it, but protect:
- Role and Status.
- Organization and Immediate Manager relationships.
- Identity fields maintained by an external source.
- Employment or regulatory values that require verification.
- Consent choices that belong to the user.
Maintain preferences and interests
Use Preferences for the available language, time zone, notification scheme, interests, and newsletter preference. Confirm the effect in the user experience rather than treating a saved value as proof that every dependent translation, notification rule, or content option exists.
Interests use Category tags where configured. They can be maintained manually, supplied through import, or added through categories associated with activity enrollment. Organization-specific tag visibility can limit which choices are appropriate. Interests support discovery; they are not Certificates or validated Skills.
Use questionnaires for purposeful enrichment
Two related mechanisms should be kept distinct:
| Mechanism | What it does | What to watch |
|---|---|---|
| Supplemental questionnaire | Presents a configured questionnaire in the profile context and displays the submitted response. | Availability, audience, and who may view or edit the response depend on questionnaire configuration and permissions. |
| Profile-updating question | Writes an authenticated answer to a supported profile field. | A full submission can replace an existing value and can conflict with an import or integration that owns the same field. |
An authenticated questionnaire submission can update supported profile information when the question is configured to do so. Anonymous distribution does not provide the authenticated identity needed for that update. Explain overwrite behavior to the owner of any onboarding or profile-refresh questionnaire and collect only the information the process needs.
Keep Transaction information separate
Checkout can begin with values from the user’s profile, but edits made during checkout are stored with the resulting Transaction. They do not rewrite the profile.
This is intentional: a person can provide billing or contact details for one order without changing the persistent academy identity. When Finance and Support see different values, compare the historical Transaction with the current profile rather than silently copying one over the other.
Maintain biographies and Skills with the correct boundary
Where Biography is enabled, eligible users can maintain a professional introduction. Biography pages and included files can be accessible by direct public link. Do not add confidential documents or private learner information.
Authorized administrators can use the Skills tab to record verified competence gained outside platform training. If levels are enabled, enter the approved level. Manually maintained Skills remain until changed or removed, while certificate-based Skill contributions follow the Certificate’s validity. Record the evidence and approval process outside the free-text description when organizational governance requires it.
Treat password, 2FA, connected accounts, and consent as user-account controls
These tabs are part of the account experience, but they are not ordinary profile fields:
- Password applies to local credentials. Access to another user’s Password tab depends on a dedicated system setting; existing passwords are never visible.
- Two-factor authentication is configured by the user for their own account and is unavailable while editing another user or masquerading.
- Connected accounts are user-authorized service connections; they are not automatically SSO identities or role assignments.
- Legal permissions contains supported privacy and consent records. Optional consent is changed by the user, not by an administrator acting on the person’s behalf.
The complete user-facing behavior is documented in Use Your Profile and Account Settings. For a support investigation, use Understand and Support the User Profile.
Practical maintenance patterns
| Situation | Recommended approach | Evidence of success |
|---|---|---|
| An employee changes department | Update the authoritative source or approved local field, then check the dependent audience or workflow. | The source and profile agree, and the intended downstream rule produces the expected result. |
| A customer supplies order-specific billing details | Maintain the Transaction through the approved commercial process. | The order contains the correct historic billing data without repurposing the profile. |
| The academy refreshes contact information | Use an approved authenticated questionnaire, import, integration, or controlled profile process. | The same source continues to own the field and later updates do not unexpectedly reverse it. |
| A partner manager corrects a managed member | Edit only the permitted fields within the managed organizational scope. | Delegation succeeds without exposing or changing records outside scope. |
| Prior experience must be recognized as a Skill | Validate the evidence and use the Skills tab if manual maintenance is part of the organization’s process. | The Skill and level reflect the approved evidence and are distinguishable from certificate-earned contributions. |
Verify the outcome
For a meaningful profile change, verify:
- The intended User ID and account were updated.
- The saved value is correct.
- The intended viewer and editor permissions still apply.
- The authoritative source agrees with the result.
- One relevant downstream rule or view produces the expected outcome.
Do not assume that a successful profile save proves enrollment, access, certification, notification, or reporting behavior.
Troubleshooting
| Problem | What to check |
|---|---|
| A field is absent | Check the Profile form, the current edit/view context, enabled features, and supported field type. |
| A field is visible but cannot be edited | Check field editability, role configuration, organizational scope, and the authoritative source. |
| A questionnaire did not update the profile | Check the question’s update option, full submission, supported target field, and authenticated user context. |
| Profile and checkout information differ | Compare the current profile with the Transaction’s personal information; checkout edits do not rewrite the profile. |
| A value keeps changing back | Identify imports, SSO mappings, integrations, or questionnaires that write the same field. |
| A relationship is not reflected in the expected view | Verify Organization or Immediate Manager in its dedicated management context, including My staff where applicable. |
FAQ
-
Do changes made during checkout update the user's profile?
No. Edits to personal information during checkout are stored with the Transaction rather than written back to the current profile. Maintain the profile through its appropriate editing or source-system process.
-
Can a questionnaire replace existing profile information?
Yes. Supported questions configured to update a profile can overwrite the corresponding values when an authenticated user fully submits the questionnaire. Anonymous responses do not provide the authenticated identity required for this update.
-
Why does a corrected profile value change back later?
Another process may own or update the field, such as an import, SSO mapping, integration, questionnaire, or onboarding form. Identify the source of truth and its next update before editing the value again; otherwise a correct local change can be overwritten.