Create a driver record | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/create-a-driver-record Publisher: Pixie Technologies LLC Driver onboarding, pay and compliance Create a driver record Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on. Onboard an employed or self-employed driver with contact, pay and compliance details. Audience: Courier operations staff; Permission: Courier: Create; Module v2.0.0; Where to goAdmin Area → Courier & Logistics → Drivers → Add Driver Before you start - Have the driver’s verified identity, contact, right-to-work, driving-licence, pay and emergency information. What this guide helps you do Onboard an employed or self-employed driver with contact, pay and compliance details. The instructions below follow the supplied module’s controller, form and model rules, including server-side validation and downstream effects. Follow these steps - Go to Drivers and select Add Driver. - Enter identity and contact details. - Select employed or self-employed. - Set employment and availability states. - Select a supported payment method and enter its matching rates. - Add licence, right-to-work, bank and emergency details. - Save the record. - Go to the new driver and upload required evidence. Fields and options IdentityName, email, phone, address and identifying details. Employmentdriver_type: employed or self_employed; employment_status: active, onboarding, suspended or left. Availabilityavailable, busy, offline or unavailable. Paymentfixed_job, percentage, per_mile, hourly, day_rate, hybrid or salary. Sensitive valuesNational Insurance and bank details are encrypted before storage. ComplianceDriving licence and right-to-work dates plus supporting documents. Rules and limits - New drivers receive a DRV code. - The initial compliance state is pending and onboarding progress starts at 20%. - Use a valid email when dispatch notifications are required. Check it worked - The driver becomes available to the active list only when saved active and not deleted; dispatch still checks availability and compliance. Security, audit and operational checks - Use the exact record and least-privilege role before changing any state. - Verify the saved record after every action; a browser message alone is not evidence that every downstream step completed. - Use protected document and image routes rather than exposing server filesystem paths. - Keep customer, driver, provider, financial and credential data within the authorised workflow. - For provider, finance, employment, transport and compliance decisions, follow the organisation’s authorised professional process. Do not bypass the code flowDo not force database values, invent a status, mark a job completed without signed POD evidence, or expose encrypted credentials to make a screen appear successful. Related guides Edit a driver safely (https://pixiecrm.com/help-centre/edit-a-driver-safely)Understand driver employment statuses (https://pixiecrm.com/help-centre/understand-driver-employment-statuses)Understand driver availability states (https://pixiecrm.com/help-centre/understand-driver-availability-states)Configure fixed-job driver pay (https://pixiecrm.com/help-centre/configure-fixed-job-driver-pay)