> This page is for version Staging.
> For other versions, use one of these documentation indexes:
> - Prod (default): https://docs.chrt.com/prod/llms.txt
> - Staging: https://docs.chrt.com/staging/llms.txt
> - Dev: https://docs.chrt.com/dev/llms.txt

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.chrt.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.chrt.com/_mcp/server.

# Install the Driver App

> Install, sign in and confirm your organization and driver access.

Install chrt, sign in and check your active organization before accepting work.

## Before you start

* Ask your organization to invite the account you will use.
* For driving, ask dispatch to confirm your driver profile is linked to the active organization and that the organization supports driver workflows. An invitation alone does not guarantee driving access.
* Use the store version supported by your organization, or its approved test build. Store availability and device compatibility are shown by the store listing.

## iOS

Open the App Store, find **chrt** and install it. Open the installed app. Use your organization's approved distribution link if you are testing a prerelease build.

## Android

Open Google Play, find **chrt** and install it. Follow your organization's approved distribution instructions for a test build.

## Sign in

On the signed-out screen shown below, tap **Sign In** 1 and complete the hosted sign-in flow. Use the identity your organization invited; the available sign-in method depends on its configuration. You can later check or change the active organization from **Settings**: open the profile row at the top, then **Organization**.

![The signed-out chrt app screen on iPhone; number 1 points at the Sign In button.](/_fern-files/_img/fc111a588ebece88b26c4cb282ac945ff993e5383006143f5bd5b841a116e2a6.webp)

*The signed-out screen on iPhone, shown before an account is authenticated. **1** **Sign In** button.*

Permission prompts appear separately when needed.

## Permissions

Grant permissions when prompted for the feature you are using. You can review them in your phone's settings:

| Permission           | Used for                                                                                                   |
| -------------------- | ---------------------------------------------------------------------------------------------------------- |
| Notifications        | Receiving alerts. Check notification preferences as well as the phone's permission.                        |
| Location             | Location sharing you enable with dispatch. Background sharing needs the phone's background location grant. |
| Camera               | Photo capture and camera-based barcode/QR scanning. A drawn signature does not require the camera.         |
| NFC, where supported | Reading compatible tracker labels. Requires a supported physical phone and label.                          |

On iPhone, location permissions include **While Using the App** and **Always**; use precise location for sharing. On Android, review the app's location permission and background access in system settings. The wording and sequence depend on the OS version. Follow the displayed instructions rather than expecting all prompts at first launch.

See [Live location](/staging/app/location) for the sharing toggle and background prerequisites.

## Check access after sign-in

Eligible drivers see **Orders**; its filter menu (top right) switches between **Offers**, **In Progress**, **Completed** and **Cancelled**. Other accounts may land on **Settings** or **Trackers**. In **Settings**, the profile row at the top shows the active organization. If **Create driver profile** is offered, complete it; if profile loading fails, use **Retry driver profile** and contact dispatch if the issue persists.

An empty Offers list can be normal when nothing has been offered or assigned. Ask dispatch to confirm the assignment under the organization you selected.

## If sign-in fails

Check connectivity and retry. If the app reports missing sign-in configuration, contact your organization's test-build owner or support; installing another build is useful only when it is the approved replacement. Do not assume a configuration message identifies your role or driver eligibility.

See [Settings](/staging/app/settings) and [Troubleshooting](/staging/app/troubleshooting).