Select a project and sign in
Choose the intended project when the Business App asks for one, then use the normal password or one-time-code path on the Login screen. Use only an existing account confirmed by your Ordering administrator. Authentication can create a remote session before the app checks whether technical access level 0 or 2 may enter the Business App.
Before you start
- Obtain the project name and a confirmed existing account from your Ordering administrator. Do not try an unconfirmed email address or mobile number and do not reuse credentials from another project.
- Confirm that the device can reach the service before submitting credentials or requesting a verification code.
- Expect authentication to create a remote session. If a one-time code verifies an unknown identifier, the current source-intended service can create a general Ordering account and session; that is not a supported Business App signup path.
- After sign-in, configured notifications can ask for device permission and separately register the device for notifications. Permission, registration, and delivery are not guaranteed.
Complete the task
- Open the Business App.
- If Project Name appears, enter the project name supplied by your administrator. Spaces are removed from this value as you type.
- Continue from the opening screen:
- If Project Name is shown, select Set project.
- If Project Name is not shown, select Login.
- Wait for the Login screen, then use the normal configured method for the confirmed account:
- For password sign-in, enter the displayed Email or mobile-phone field and Password.
- For one-time-code sign-in, select the displayed OTP option, enter the requested email address or mobile number, and select Get verify code.
- Do not use the separate mobile-phone Get Verify Code action that can appear with phone/password sign-in. That alternate verification flow does not apply the documented Business App access-level check and is not a supported entry path for this procedure.
- If Verify reCAPTCHA appears, complete it before submitting the form.
- Select Login. For the OTP path, enter the code in Enter verification code after it arrives.
Do not repeatedly submit the form while it is loading. Verification-code delivery and reCAPTCHA are provider-backed steps and can be unavailable even when the app is online.
Verify the result
The task is complete when the authenticated Business App workspace opens for the intended project and account.
If the app reports that the session was closed, the returned account did not pass the current Business App check for technical access level 0 or 2. The visible close attempt does not prove that the remote session was closed. Ask the administrator to verify the account and revoke any residual session before another attempt.
After an accepted sign-in, a notification permission prompt may appear. Permission and device registration are separate follow-up effects; neither confirms notification delivery or additional workspace permission.
Recover safely
| What you observe | What it means | Safe next action |
|---|---|---|
| The field project name is required | Project selection is enabled, but no project name was submitted. | Enter the project name provided by your administrator, then select Set project once. |
| The expected project does not open | The project value may be incorrect or unavailable. | Return to the project screen and confirm the exact value with your administrator before trying again. |
| A required-field or invalid-email message appears | One or more visible fields failed local validation. | Correct only the indicated field and resubmit once. |
| The captcha validation is required or Please try again appears | The configured reCAPTCHA step is missing, expired, or was rejected. | Complete the displayed verification again. If it continues to fail, stop and contact the project administrator. |
| Invalid phone number appears | The mobile number or country code is incomplete or invalid. | Correct both values before requesting another code. |
| A verification code does not arrive | The configured email, SMS, or other available delivery channel may be delayed, rate-limited, or unavailable. | Wait for the resend control to become available, retry once, then ask the administrator to verify the configured method. |
| Time is up appears | The one-time-code window ended. | Select Resend code when enabled and use only the newest code. |
| A separate mobile Get Verify Code action appears outside the OTP tab | This alternate phone-verification path is not a supported Business App entry method in the current procedure. | Do not use it. Ask the administrator to confirm the normal password or OTP method for the existing account. |
| You requested or verified a code for an identifier that was not confirmed as an existing account | The source-intended service can create a general Ordering account and remote session for an unknown identifier. This is not supported Business App signup. | Stop. Do not request another code. Ask the administrator to review the identifier, account, and any created session. |
| The credentials are rejected or the account is disabled | The server did not accept the submitted account state. | Stop retrying and ask the administrator to verify the account and project. Never share the password or verification code. |
| The app reports that the session was closed after authentication | The account did not pass the current client check for technical access level 0 or 2; remote closure may still have failed. | Stop retrying. Ask the administrator to verify product access and revoke any residual session. |
| A notification permission prompt appears after sign-in | Notification permission is a separate post-authentication device effect. | Choose the intended permission state. Do not treat the prompt as proof of device registration or delivery. |
Availability and platform differences
- Project selection appears only when enabled for the app build. In fixed-project mode, select Login from the opening screen.
- Email/password, mobile-phone/password, the normal one-time-code tab, and reCAPTCHA depend on project configuration. The separate mobile Get Verify Code phone-verification path is excluded until its Business App access behavior is corrected and retraced.
- A one-time code can involve an external delivery provider. Use it only for a confirmed existing account. Requesting or validating a code does not guarantee Business App access and can create a general account/session for an unknown identifier.
- The normal password and OTP path applies the current access-level check after authentication. Server-side validation, rate limits, account state, project state, session closure, and task-specific authorization still apply.
- Configured notifications can prompt for device permission after authentication and can separately attempt device registration. Neither action guarantees registration, delivery, or access.
- The relationship between the reviewed API source and a deployed API environment has not been established. Verify only the result visible in your Business App environment.
Related articles
:::note Visual status Visual guidance is deferred pending an authorized synthetic capture program with an exact asset allowlist and independent visual QA. This procedure remains complete without images. :::