Sign in as a driver
Driver App can present a password form for an email address or cellphone, depending on the current project configuration. Use only a method shown in the app and credentials for an account that has the Driver role.
:::warning A Login tap does not prove a request started
The app can enter a loading state before local form validation finishes. A validation message can stop submission before any authentication request is sent. Loading also does not prove that credentials were accepted, that the account passed the Driver role check, or that the signed-in area is ready. Do not tap Login repeatedly while the result is unresolved.
:::
Availability
When a password method is enabled, it is available after Driver App finishes its startup checks and opens Login. The exact form is configuration-dependent; some projects can show only an alternate method:
| Visible form | Required information |
|---|---|
| Email password | Email and Password |
| Cellphone password | Country code, cellphone number, and Password |
Some projects can also require Verify reCAPTCHA before accepting a password request. One-time-code and provider-specific methods have separate controls and results. Use only the method currently shown for your Driver account.
Before you start
- Confirm that the app shows the expected project and sign-in method.
- Use the email address or cellphone registered to your Driver account.
- Have the correct password available. Do not share passwords or verification codes with another person.
- If another request is still loading, wait for its visible result before trying again.
Complete the task
- On Login, choose the password method associated with your Driver account when more than one method is shown.
- Enter your email address, or select the country code and enter your cellphone number.
- Enter your password. Use the eye control only if you need to check the characters on a private screen.
- If Verify reCAPTCHA appears, complete that control before continuing.
- Review the identifier and select Login once.
- Keep Driver App open while the button shows a loading state. Follow the next screen or the error shown by the app.
After local validation passes, selecting Login submits the entered credentials. The returned account must also pass Driver App's Driver-role check before the app stores the session as the current signed-in state.
Verify the result
Treat the visible result as a sequence, not as one event:
| Observable state | What it establishes |
|---|---|
| Login is loading | The app began handling the submission locally; a request and acceptance are not yet established |
| A validation message appears | The current form needs correction before a new request |
| An authentication or wait message appears | The request returned an error or limit state; no signed-in state is shown |
| A permission message says the session was closed | The returned account did not pass the Driver-role check in the standard password flow; the message alone is not a server logout receipt |
| Driver App leaves Login and presents the signed-in journey | The client accepted the returned Driver session locally; later permissions, schedule, connectivity, and loading gates can still apply |
Navigation alone is not proof that every account, notification, location, or schedule-related operation has finished.
States and variations
- Email input is normalized to lowercase and rejects spaces and several unsupported characters before submission.
- Missing or invalid required values produce a validation message without a valid request.
- When reCAPTCHA is configured, missing configuration or an expired/failed challenge can prevent the request from continuing.
- A project can show a one-time-code tab or cellphone verification control. Those are alternate authentication journeys, not extra steps in this password procedure.
- After a locally accepted session, Driver App can still show permission, schedule, connectivity, or loading states before the operating area is available.
Troubleshooting
The expected password method is missing
Use one of the methods currently displayed. Availability is controlled by the current project configuration. If the method for your Driver account remains missing, contact the operator that manages your Driver access.
Login shows a credentials error
Check the email address or cellphone, country code, and password. Correct the visible field once and submit once. If the password is not known, use Forgot your password? instead of making repeated attempts.
Login shows a wait or attempt-limit message
Do not keep submitting. Wait for the period shown by Driver App, then try once with verified credentials. Your project operator owns account access and can help when the message does not clear.
Driver App shows a session-closed permission message
The standard password flow accepts only the Driver role for entry to Driver App. Confirm that you used the correct Driver account. The operator that provisioned the account owns role assignment; Driver App cannot change it from the Login screen.
Login completes but another gate appears
Permissions, schedule eligibility, connectivity, and signed-in loading are separate from credential submission. Follow the gate currently shown rather than submitting the password again.
Related guides: Driver App overview · Understand startup and loading