Review and update your profile

Use Profile to review the details returned for your signed-in account and change fields that are available for the current project. A profile update can change the account used across Business App. Confirm the intended account and review every edited value before you select Update.

Before you start

• Sign in to the intended project with an existing Business App account.
• Confirm that Profile shows the intended operator before editing.
• Keep a stable connection until the result is clear.
• Treat names, email addresses, phone numbers, profile photos, and other configured fields as private account data.
• If you plan to change a password, be prepared for other sessions for this account to close after the service accepts the change.

The fields shown in Profile depend on project configuration. A visible field is not proof of a commercial role, plan, entitlement, or permission to edit another account.

Review the current profile

1. Select Profile in the bottom navigation.
2. Wait for the loading placeholders to clear.
3. Review the configured fields, the masked Password row, and Phone.
4. If the profile cannot load its field configuration, select Refresh profile once. If the error remains, verify the project and connection, then contact the project administrator with only the visible error text.

The read-only view can show configured checkout-profile fields. Their labels, order, availability, and required status can vary by project. Do not assume that a field available in one project is available in another.

Update text, contact, or password details

1. Select Edit.
2. Change only the intended fields. Required configured fields cannot be left empty. Enter a valid email format when editing email, and correct any phone validation message before continuing.
3. To change the password, complete both Password and Confirm Password with matching values. Preview the effect: an accepted password change can close other sessions for the same account.
4. Review the values again. Select Update only when the account effect is correct. Select Cancel to discard unsaved form changes.
5. Wait until Updating clears. Do not navigate away or submit the same change again while the result is pending.

An Update successfully message is the source-intended success signal. A visible error means the update was not confirmed. Screen closure, a disabled button, or locally changed text alone does not prove that the service accepted the update.

Change the profile photo

Selecting the profile image opens the device photo library. The current source does not offer a camera action from this control.

1. Before selecting the image, confirm that it contains no customer, order, payment, location, credential, or other sensitive information.
2. Select the current profile image and choose one photo from the device photo library.
3. Preview the effect: choosing the photo starts a profile update immediately; there is no separate Update confirmation for the image.
4. Wait for Update successfully or a visible error. Do not select the image again while the outcome is unknown.

The app requests a photo from the library and prepares image data for remote upload. Device permission behavior, provider completion, upload cleanup, and the deployed result have not been verified. In the current implementation, the callback selects the first returned asset before it checks cancellation or picker errors. A top-level cancel or error can therefore appear as Image not found. Without a usable photo URI, no profile update is started. A usable URI and its requested photo data start the update immediately.

Verify the result

After a source-intended successful text or photo update:

1. Leave edit mode and review the returned profile values.
2. Reopen Profile before relying on a security-sensitive change such as email, phone, or password.
3. If a value still shows the earlier content, treat the result as stale or unknown. Do not repeat the update until the project administrator confirms the current account state.

No Business App message proves role, entitlement, upload-provider completion, or deployed App/API equivalence. A successful profile response also does not prove that every other session, device, or cached screen has refreshed.

Recover safely

What you observe	What it means	Safe next action
Loading placeholders remain	Profile or session data is still pending	Restore connectivity and reopen Profile once. Do not edit while the current account is unclear.
Network Error or a profile configuration error	The configured fields could not be established	Select Refresh profile once, verify the project, and escalate if the error remains.
A required-field, email, phone, or password-match message	The form did not pass local validation	Correct the named field. Do not work around a required or validation rule.
Updating remains visible or the app closes before a result	The remote outcome is unknown	Reopen Profile and compare the visible value. Do not resubmit until the account state is confirmed.
An update error appears	The service did not provide a confirmed success response	Keep the error text, leave the changes unsubmitted, and ask the project administrator to verify the account if it persists.
The photo library is cancelled or returns a top-level error	The current callback can show Image not found because it checks the first asset before top-level cancel/error fields	Keep the existing image. No update starts without a usable photo URI. Retry only after the library is available; do not use a camera workaround from this guidance.
Image not found	The callback did not receive a usable first-asset URI; this can represent cancellation, a top-level picker error, or a missing asset	Keep the existing image and choose a different non-sensitive photo later.
A distinct picker error appears	An error was present on the selected first asset	Keep the existing image and preserve the visible error text if escalation is needed.
A new photo or value appears without a clear success result	Local and remote state may be stale or partial	Reopen Profile, avoid another write, and escalate the unknown result.
A previously accepted value must be restored	The service has already received a change	Verify the current value, then use Edit for one deliberate corrective update. There is no documented automatic rollback.

Availability and account boundaries

• Current Business App source admits technical access levels 0 and 2. These numbers are technical gates, not commercial role names or entitlement guarantees.
• Profile operates on the signed-in session account. Selected-business visibility does not grant permission to edit another account.
• Configured fields determine which profile inputs are shown and required. Password and phone have additional validation and service-side checks.
• The source includes a separate driver-profile edit configuration, but that does not establish a supported Business App role or workflow beyond the admitted technical levels.
• The profile-photo control uses the device photo library only. Photo-library permissions and provider behavior vary by platform and remain unverified.
• The documented App and API source relationship to the deployed service is not attested. This procedure describes safe source-intended boundaries, not a deployment guarantee.

Related articles

• Understand technical access levels and business scope
• Recognize loading, connection, and error states

:::note Visual status Visual guidance is deferred. Reopen trigger: authorized synthetic capture program with accepted exact asset allowlist and independent visual QA :::