> 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. # Settings > How to configure your driver profile, location sharing, notification preferences, and account settings inside the chrt mobile driver app. The **Settings** tab is where you control your driver profile, location sharing, notifications, and account-level settings like org switching and sign-out. ## Sections in Settings | Section | What you control | | -------------------------------- | ----------------------------------------------------------------------------------------------- | | **User details** | Your name and account email (read-only from the app — change in the web app if needed). | | **Organization** | The org you're currently signed in under. Switch orgs here if you're a member of more than one. | | **Share Location with Dispatch** | The live-location toggle and permission status. | | **Driver availability** | Whether you're flagged available for new offers. | | **Push Notifications** | The OS-level permission state for chrt push notifications. | | **Notification Preferences** | Per-event opt-in for the kinds of notifications you want. | | **Driver Details** | Editable driver profile fields. | | **Privacy / Support / Terms** | Links out to chrt.com pages. | | **Build Information** | Version and build number, for support diagnostics. | | **Sign Out / Delete Account** | Account-level destructive actions. | ## 1. Switch organizations If you're a member of more than one org, the **Organization** switcher near the top of Settings lets you pick which one you're currently signed in under. * Switching reloads the app under the new org's data — your offers, in progress orders, and completed list all reflect the active org. * Each org has its own driver record; your profile in one org doesn't follow you to another. > **Note** > > If you only belong to one org, the switcher doesn't appear — there's > nothing to switch to. ## 2. Manage location sharing The **Share Location with Dispatch** card shows: * Current permission status (**Always**, **While Using App**, **Denied**, etc.) with a **Settings** button to jump to the OS Settings app. * Precise vs approximate accuracy state. The card flags you if accuracy is approximate and offers a fix. * The on/off toggle. * Last reported coordinate and time-since-last-seen. See [Live location](/app/location) for the full background on how this works, the difference between iOS and Android permission flows, and the Android offline buffering behavior. ## 3. Manage notification permissions Two cards control notifications: * **Push Notifications** — the OS-level permission. If denied, you won't receive any chrt push notifications at all, regardless of preferences. Tap the card's **Settings** action to re-grant in the OS Settings app. * **Notification Preferences** — once OS permission is granted, this card lets you opt into specific event types (new offer, message reply, billing update, etc.) per channel (push, email, in-app). > **Tip** > > If you never receive offer notifications, check both layers — the OS > permission and the per-event preference. Both need to be on. ## 4. Edit your driver profile The **Driver Details** card surfaces the editable fields on your driver record — name, contact info, and any org-specific fields your dispatcher configured. Changes save to the chrt API and are visible to your dispatcher immediately. ## 5. Driver availability Toggle whether you're available to receive new offers. When set to **unavailable**, dispatch sees this on their side and (depending on org policy) skips you in auto-assignment. This is per-driver and per-org — turning it off in one org doesn't affect another. ## Camera permission There's no dedicated **Camera** card in Settings because iOS and Android both prompt for camera permission only when you first try to use it (typically the first proof capture or tracker scan). If you denied it earlier, the next capture attempt prompts again or directs you to OS Settings. To re-grant camera permission directly: * **iOS** — open the iOS Settings app, scroll to **chrt**, tap **Camera**. * **Android** — long-press the chrt app icon, tap **App info** > **Permissions** > **Camera**. ## Privacy, Support, Terms These rows are direct links to chrt.com pages: * **Privacy Policy** — [chrt.com/privacy](https://chrt.com/privacy) * **Support** — [chrt.com/support](https://chrt.com/support) * **Terms of Service** — [chrt.com/terms](https://chrt.com/terms) They open in your default browser. ## Build information The **Build Information** section shows the app's version and build number. Include both when contacting support — it tells us which release you're running. ## Sign out and delete account > **Warning** > > **Sign Out** ends your session and clears local caches; you'll need to > sign in again to use the app. On Android, any unsynced offline > changes are lost on sign-out. Wait until your offline queue has > drained (the banner clears) before signing out if you've been working > offline. > **Warning** > > **Delete Account** is permanent and removes your driver record. > Contact your org's admin or [hi@chrt.com](mailto:hi@chrt.com) if > you're unsure — most cases want **Sign Out** or **switch orgs**, not > account deletion. ## Related guides * [Live location](/app/location) — the full background on the location toggle. * [Install the driver app](/app/install) — first-launch permission prompts. * [Accepting orders](/app/accepting-orders) — how notifications surface new offers. * [Troubleshooting](/app/troubleshooting) — when permissions, sign-in, or notifications misbehave.