Understand and Support the User Profile - Article
Summary
A user profile brings related information into one support view, but it does not own every record it displays. Some values belong to the account; others come from organizations, SSO, integrations, questionnaires, activities, Transactions, Certificates, Skills, or Communities.
Use this article to:
- Route a request to the correct profile area and canonical Help Center article.
- Identify the authoritative source before changing information.
- Investigate sign-in, preferences, relationships, and learning evidence safely.
- Verify the outcome and use account change history within its proper boundary.
Choose the correct support route
| The person needs help with | Start here | Continue with |
|---|---|---|
| Their own profile, biography, password, 2FA, preferences, or connected accounts | Open the relevant profile tab. | Use Your Profile and Account Settings |
| A persistent field or its editability | Check the Profile form and source ownership. | Maintain User Profiles and Information and Forms |
| An imported or SSO-managed value | Identify the source and its most recent update. | Users Managed Through SSO and Integrations or Import and Update Users in Bulk |
| Training, completion, Certificates, Skills, or transcript | Check the underlying participation or credential record. | Review a User’s Learning Records |
| Organization or manager scope | Verify the actual relationship between accounts. | Roles, Responsibilities, and Management Scope and the relevant Organizations guidance |
| Billing or enrollment information | Open the order or enrollment record. | Transactions |
Use the profile as a support hub
The profile connects identity and contact information with business relationships, preferences, authentication settings, learning records, credentials, and optional services. Use it to understand the person’s context, then move to the record that owns the issue.
Preserve privacy, consent, source ownership, and organizational scope when acting on behalf of another person. A limited profile view can show only supported identity information even when the underlying record contains more data.
Open the intended account
- Open Users and search for the account.
- Confirm the User ID and other dependable identifiers.
- Check organization membership, role, status, and sign-in context when relevant.
- Open the profile and the tab required for the request.
Do not create a second account as a shortcut for an identity or sign-in problem. Duplicate accounts divide learning history and create additional matching risk.
Understand the profile areas
| Area or tab | What it represents | Support boundary |
|---|---|---|
| Personal information | Identity, contact details, configured Profile fields, and supported relationships. | Determine whether each value is maintained locally, by import, SSO, integration, questionnaire, or another process. |
| Password | Local credential maintenance. | Use the external provider’s recovery process for externally authenticated accounts; never ask for or attempt to view a user’s password. |
| Two-factor authentication | Native second-factor settings where enabled. | The user manages their own factor. The tab is unavailable while editing another account or masquerading. |
| Connected accounts | Supported personal connections to calendars, files, meetings, social login, or other configured services. | A connection is not automatically the source of profile data or the person’s login identity. |
| Preferences | Language, time zone, notification scheme, interests, and other supported choices. | Available options still depend on platform and organization configuration. |
| Supplemental questionnaire | Structured business information submitted in the profile context. | Confirm audience, permissions, last submission, and whether any questions also update profile fields. |
| Skills | Supported competence evidence earned through Certificates or maintained manually. | Verify source, level, and expiry before using a Skill for a decision. |
| Legal permissions | Supported privacy-policy and questionnaire-consent records. | Do not provide or change another person’s consent. |
Identify the authoritative source
| Possible source | Typical use | What to verify |
|---|---|---|
| User or authorized profile edit | Information maintained directly. | Correct account, field-level editability, and scope. |
| Import | Controlled updates for a defined population. | Matching identifier, template version, overwrite behavior, and last import. |
| SSO or integration | External identity, employment, organization, or other agreed data. | Source of truth, mapping, synchronization timing, and offboarding behavior. |
| Questionnaire | Authenticated profile updates or supplemental business context. | Submission identity, target field, overwrite behavior, and permissions. |
| Organization or Immediate Manager | Membership, administrative scope, and staff oversight. | The relationship itself, not only a descriptive Company or manager-name field. |
If a correction is later reversed, find the process that wrote the subsequent value instead of repeating the local edit.
Support identity and access safely
First determine whether the account uses regular local login, SSO, social login, or a combination.
- For a local account, the person can change their own password. Authorized access to another user’s Password tab depends on the dedicated administrator setting, and only a new password can be set.
- For an externally authenticated account, recovery and MFA can belong to the external identity provider.
- Native 2FA is configured by the person for their own account. It cannot be configured through masquerade or while editing another user.
- Connected accounts can support calendars, files, or meetings and should not automatically be treated as authentication connections.
If repeated 2FA or password attempts trigger Too many failed attempts. Try again later, five failed attempts have occurred within the three-hour protection window. Do not keep retrying or weaken the person’s authentication as routine troubleshooting.
Investigate learning and achievement evidence
| Record | Use it for | Important boundary |
|---|---|---|
| My Trainings | A convenient view of available learning, status, progress, and completion. | Use the activity participant record when the profile card does not explain the case. |
| Transcript | A downloadable PDF learning-history report within its supported date and status scope. | It is not a complete record of every cancelled or expired participation state. |
| Certificates | Issued credentials and supported validity information. | Completion alone does not prove that a Certificate was issued or remains valid. |
| Skills | Configured competence evidence from certificate-based and manual sources. | Interpret method, level, and expiry before using the result for eligibility. |
| Historic learning | Approved evidence brought forward from another process or system. | A user-account import alone does not prove that learning history was imported. |
Also confirm that the evidence belongs to the intended User ID. An apparent missing completion can be stored on a duplicate or incorrectly matched account.
Review connected commercial and community information
Where enabled, the profile can link to Balance, Orders, Incentives, Communities, and supplemental questionnaire information.
- Balance and Orders support reward and fulfilment questions. Use the underlying order or accounting record before drawing a financial conclusion.
- Communities show participation in collaborative spaces. Community membership is not organization membership.
- Supplemental questionnaire responses provide submitted business context. They do not all become standard profile fields.
Review preferences, biography, and legal choices
Preferences can include language, time zone, notifications, interests, and newsletter choice. Verify the user experience after a change; a saved value does not create translations, content, or notification rules that have not been configured.
A Biography can provide a public professional introduction. Files included in it can be accessible through direct public links, so they must not contain confidential documents or private learner information.
Legal permissions require particular care. Access to the tab does not authorize a support user to make another person’s consent choice. Use the designated privacy or consent process when a record requires correction.
Use account change history within its boundary
Authorized roles can select More → Account change history where the action is available. It provides a field-level history of relevant account and profile changes and can establish when a value changed.
It is not a complete learning, enrollment, Certificate, Skill, integration, consent, or commercial audit trail. Use the corresponding source record for those questions.
Verify the support outcome
| Support task | Evidence of a dependable result |
|---|---|
| Identity correction | The intended User ID is unchanged, the correct account was updated, and the authoritative source agrees. |
| Sign-in support | The person can use the intended authentication route and no duplicate account was created. |
| Preference update | The saved value produces the intended experience within the available configuration. |
| Achievement question | The relevant activity, Certificate, Skill, transcript, or historic-learning record confirms the conclusion. |
| Organization or manager change | The relationship appears in its dedicated management view, including My staff where applicable. |
Troubleshooting
| Issue | What to check |
|---|---|
| A corrected field returns to its earlier value | Identify whether an import, SSO mapping, integration, or questionnaire owns the field and when it next updates. |
| Expected training or achievement evidence is missing | Check account identity, activity participation, completion criteria, Certificate or Skill source, and expiry. |
| A field is visible but cannot be edited | Confirm role, organizational scope, Profile-form configuration, and source ownership. |
| The user is not visible | Check organization scope, limited-profile rules, filters, status, and the intended User ID. |
| Password or 2FA controls are unavailable | Confirm the sign-in model, relevant feature and setting, and whether you are editing or masquerading rather than viewing your own account. |
| An organization or Immediate Manager change is not reflected | Verify the relationship in its dedicated management view, including My staff where applicable. |
FAQ
-
Why is a profile field visible but not editable?
Visibility does not always include permission to change the value. Check the support role, organizational scope, field configuration, account context, and whether an import, SSO mapping, integration, questionnaire, or another process owns the field.
-
Is Account change history a complete audit trail for everything connected to a user?
No. Account change history helps investigate relevant account and profile-field changes. Use the corresponding Training Activity, progress, certificate, Skill, Transaction, integration, or source-system record when the question concerns learning, credentials, commercial activity, or connected-system updates.
-
Which profile record should I use to verify a learning achievement?
Use the record that proves the specific outcome. Training Activity participation and progress show the learning journey, a certificate shows the issued credential and its validity, Skills show configured competence evidence, and historic learning records approved evidence brought forward from another process. These records are related but not interchangeable.