Update your profile and password
Keep your own profile and password current without changing company-level access Follow a safe workflow, verify the customer-facing result, and isolate common problems.
Keep your own profile and password current without changing company-level access This guide keeps the work focused on personal account settings and provides a repeatable path that a new Humind user can follow without changing unrelated configuration.
Workspace access combines personal account settings with company roles and permissions. Each teammate should use their own account, receive only the access needed for their responsibilities, and keep sign-in details current. Security review is an ongoing operating habit, not a one-time setup task.
Before you begin
Access: Every signed-in teammate can manage the personal settings exposed for their own account. Sign-in method can affect whether password controls are available.
- Sign in with your own account.
- Know whether your account uses a password or an external identity provider.
- Use a secure device and current recovery details.
Work in the smallest owning area described below and keep the current customer-facing state available while you prepare the change. Before clicking any final action, confirm the active company, Agent, store, language, and market shown in Humind. A missing control can indicate read-only access or a capability that is not configured for this company. In that case, record the intended task and ask an administrator to review the exact permission or dependency. Do not bypass the boundary by sharing an account, copying data into another area, or promising a capability that the workspace does not expose.
Step-by-step workflow
Confirm the scope and current state
Open your personal profile or account settings and confirm the email and company context before editing.
- Confirm the active company and Agent before editing.
- Record the current state so the result can be compared after the change.
- Stop if the screen or permission does not match the intended task.
Prepare the change
Update only the personal fields exposed for your account and save them before leaving the page.
- Use the smallest change that completes the customer task.
- Keep authoritative information in its owning source.
- Review labels, dates, language, and customer-visible wording before saving.
Save and allow required processing to finish
If password management is available, use a unique strong password and complete any current-password or confirmation step. External sign-in users should follow their identity provider.
- Wait for the interface to confirm that the change is saved.
- If synchronization, indexing, or publication is required, wait for its final state.
- Reload the area and confirm the saved values persist.
Test the complete customer journey
Sign out and sign in through the expected method, then confirm your profile changed without altering roles or company membership.
- Use a fresh session and a realistic customer scenario.
- Check desktop and mobile when the result appears on a storefront.
- Capture the exact failing step if the outcome differs from the expectation.
Important limits and operating notes
- A successful save confirms persistence, not every downstream synchronization or public update.
- Workspace permissions can hide an area or allow reading without allowing changes.
- Do not copy volatile catalog, account, or customer facts into narrative content as a workaround.
- Test only supported capabilities that are visible and configured for the current company.
- Keep changes in personal account settings separate from unrelated Agent, Knowledge, catalog, Inbox, or Helpdesk work.
Verify the result
- The updated profile persists after reload.
- The expected sign-in method still works.
- No teammate role or company setting changed.
- Recovery and identity-provider details remain current where managed.
Keep a short record of what you tested, which customer scenario you used, and what changed. This makes later troubleshooting more precise and helps another teammate reproduce the result without relying on memory.
Troubleshooting
No password option is shown
The account may use external or passwordless sign-in. Review the visible sign-in method and use the identity provider or administrator-supported recovery path rather than creating a second account.
The profile update is rejected
Check required formats, current session, and whether the field is controlled by an external identity provider. Record the visible error without sharing credentials.