Sign out of Business App
Sign out when you have finished using Business App on the current device. This action immediately starts closing the current session; it does not show a confirmation step and does not close sessions on your other devices.
Before you start
- Finish or record any in-progress order work before leaving the authenticated workspace.
- Keep the app connected and wait for any earlier action to settle.
- Open Profile and confirm that you intend to end the session on this device.
- Select Logout only once. Repeated requests can be rejected, and an uncertain first result must not be treated as permission to try again.
Sign out
- In the bottom navigation, select Profile.
- Move to Logout near the bottom of the profile page.
- Before selecting it, confirm the effect: the app will request revocation of the current session, then remove local signed-in state and return to a signed-out entry screen only if that request is accepted.
- Select Logout once.
- Wait for the authenticated workspace to disappear. If no signed-out transition occurs, stop; do not select Logout again or perform another app, session, or provider action.
Verify the result
| Visible result | What it establishes | Safe next action |
|---|---|---|
| A signed-out project or sign-in screen replaces the authenticated workspace | The app changed to a signed-out state on this device | Confirm that Profile, orders, and messages are no longer available without signing in. |
| The authenticated workspace does not change after one selection | No signed-out transition was confirmed; the server or local cleanup may still have changed part of the session | Stop. Do not restart the app or perform another account, session, or provider action. Record the time and unchanged workspace, then ask your administrator or Ordering Support to verify the session and provide access-restoration evidence. |
| The app is signed out but account data, notifications, or authenticated updates remain visible | Some device or provider state may remain after the main session closes | Do not clear storage or sign in again as a test. Record what remains, the platform, and the time, then escalate. |
| The sign-in screen appears but the former session still appears active elsewhere | Sign-out here does not establish closure of other sessions | Stop. Ask your administrator or Ordering Support to verify the account and session state; do not inspect or change sessions yourself. |
Successful sign-out is established by the signed-out entry state and loss of access to the authenticated workspace. It is not established by a button press, a loading state, or a message alone.
Recover safely
| What you observe | What it means | Safe next action |
|---|---|---|
| The authenticated workspace remains unchanged after one selection | There is no confirmed transition, and the remote or local result is unknown | Stop after that one attempt. Do not restart, sign in, inspect sessions, use provider controls, clear storage, reinstall, or retry. Ask your administrator or Ordering Support to verify the session and restore access safely. |
| The app returns to sign-in but later restores the former workspace | Local session data may not have been cleared consistently | Stop, record the sequence, and escalate; do not clear app storage, reinstall, or repeatedly sign out. |
| Notifications continue after sign-out | Notification registration or the external push provider may not be fully disconnected | Do not open sensitive notification content on a shared device. Record the notification time and platform and contact support. |
| Authenticated realtime updates continue | A connection can outlive the visible navigation change | Stop using the app. Do not restart it or change provider or session state; record the observation and ask your administrator or Ordering Support to verify the residual connection. |
Availability and limits
- Logout is available from Profile after the authenticated profile state finishes loading.
- The source-intended flow requests closure of only the current session associated with this sign-in. It does not prove that every session on the account is closed.
- When a notification registration is available locally, the app asks the service to remove that registration during logout. This does not prove immediate removal of every external push identity, subscription, or already-delivered notification.
- Local cleanup intends to remove signed-in and app data while retaining the tutorial and language preferences. Current source evidence does not prove that every device-code, socket, push-provider, or cached value is cleared atomically.
- A server acceptance can be followed by incomplete local cleanup, and a lost, rejected, or partial result can leave the final state uncertain. After the single allowed selection, stop without restarting, signing in, inspecting sessions, changing provider state, clearing storage, reinstalling, or retrying. Administrator or Ordering Support verification and access-restoration evidence are required.
- The same source path is used on iOS and Android, but installed-build behavior, provider cleanup, and deployed API equivalence remain unverified.
Related articles
- Review and update your profile
- Select a project and sign in
- Recognize loading, connection, and error states
:::note Visual status authorized synthetic capture program with accepted exact asset allowlist and independent visual QA :::