> For the complete documentation index, see [llms.txt](https://codico-dispatch.gitbook.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://codico-dispatch.gitbook.io/documentation/getting-started/key-concepts-and-user-roles.md). # Key Concepts and User Roles The building blocks of CodiCo Dispatch and the people who work with them. CodiCo Dispatch connects four groups of people around one shared list of bookings: your own team, the transport companies and drivers who carry out rides, the customers who book them, and the partners and affiliates who bring you work. This page explains the terms used throughout the documentation. ## Core concepts | Term | What it means in CodiCo Dispatch | | ----------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Booking** | One ride ordered by a customer: pickup date and time, route, vehicle class, passengers and luggage, price and payment. A booking has a number such as `07324`. | | **Return booking** | The return leg of a round trip. It is created together with the outbound booking and gets the same number with the suffix `/B`, for example `07300/B`. | | **Vehicle class** | The type of vehicle the customer books, such as Saloon, Estate or Minibus. Prices, capacity and availability are configured per vehicle class in **Fleet & Pricing**. | | **Company** | A transport company that carries out rides: your own company or a subcontractor. Each company has its own drivers and a commission rate. | | **Driver** | A person who carries out rides with the driver mobile app. Each driver belongs to a company. | | **Assignment** | Giving a booking to a company and, optionally, to a specific driver. The company or driver then accepts or rejects it. | | **Booking status** | Where a booking is in its life cycle, from *Unconfirmed* to *Completed*. See [Booking and Payment Statuses](/documentation/bookings-and-dispatch/booking-and-payment-statuses.md). | | **Payment status** | Whether the booking has been paid, partly paid or refunded. It is tracked separately from the booking status. | | **Invoice** | The payment record for a booking or a payout. Every booking creates an invoice; companies, partners and affiliates also receive payout invoices. | | **Zone** | An area drawn on the map, used for zone pricing and booking rules. See **Locations & Rules**. | | **Marketplace booking** | A booking received through the Partner Network or a connected marketplace such as GNet, Bókun, HQ Travel, AirportTaxis.com, Transferz or Booking.com. The source logo appears in the **Partner** column of the bookings list. | ## User roles | Role | Who it is | What they do | | -------------------- | ------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **System manager** | You and your office staff | Work in the admin console: configure the system, take and dispatch bookings, manage companies, drivers, prices and payments. Managed in **System Settings → Users & Access → System Managers**. | | **Company** | Your transport company or a subcontractor | Receives booking assignments, accepts or rejects them, assigns its own drivers and gets paid out for completed rides minus the commission. | | **Driver** | Chauffeurs and taxi drivers | Receive their rides in the driver mobile app and update the ride status during the trip. | | **Customer** | Passengers and business clients | Book through the website booking form or their passenger profile, pay and receive notifications. | | **Referral partner** | Hotels, bars, restaurants, travel agencies, insurance companies and other businesses | Send their guests and clients to you through a QR code, a referral link or a partner booking form on their own website, and earn a partner commission on every completed booking. Managed in **People & Companies → Partners**. | | **Affiliate** | Business customers | Book through their own account, can pay later on invoice and receive an affiliate commission on their bookings. Managed in **People & Companies → Affiliates**. | {% hint style="info" %} Referral partners and affiliates are ordinary customer accounts with an extra role. You turn the role on in the customer's profile with **Make this user partner** or **Make this user affiliate** and set the commission there. {% endhint %} ## How money flows Each booking has a total amount that the customer pays. CodiCo Dispatch splits this amount into commissions, so you always know how much stays with you and how much goes to the company, driver, referral partner or affiliate: ```mermaid flowchart LR C["Customer pays
total booking amount"] --> A["Admin commission
(your share)"] C --> D["Driver commission"] C --> P["Partner commission"] C --> F["Affiliate commission"] C --> K["Company payout"] ``` You can see and edit these amounts on every booking. See [Creating and Editing Bookings](/documentation/bookings-and-dispatch/creating-and-editing-bookings.md#amounts). ## Watch the overview This video explains the different user types and how they work together: {% embed url="" %} User Types — Detailed Overview {% endembed %} {% hint style="warning" %} This video was recorded for an earlier version of the interface. Menu names may differ from the current version; the concepts are unchanged. {% endhint %} Learn more about how CodiCo Dispatch works with partners on the [Partner Network](https://codico.io/taxi-dispatch-software/partner-network/) feature page. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://codico-dispatch.gitbook.io/documentation/getting-started/key-concepts-and-user-roles.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.