Your first week: a setup order that works

The sequence to configure a new organization in, so nothing has to be redone later.

Written for
Administrators
Reading time
1 min
Last reviewed
August 1, 2026

The order below exists because several parts of the platform depend on earlier ones. Trips reference vehicles and service types; claims reference payers and rate tables; scheduling depends on having active vehicles with capabilities set. Setting up out of order usually means revisiting records later.

  1. Set the organization profile: legal name, address, and — critically — the operating time zone. Scheduling, reporting and claim date boundaries all read it.
  2. Add vehicles and set each one's service capabilities and active status. Scheduling only considers active vehicles.
  3. Add drivers and link each to a user account so they can sign into the driver app.
  4. Configure payers and their rate tables before you run any billing.
  5. Set operational policy: cancellation rules, completion rules, and the no-show waiting window.
  6. Invite the rest of your staff with the narrowest role that fits their work.
  7. Import or create a first day of trips and run scheduling against it as a rehearsal before go-live.

Related

Still stuck?

Technical documentation

API references, data model, webhook payloads and integration guides — the detail behind the workflows described here. Available to signed-in Naveera customers.

Open documentation

Ask your team

Support requests are raised from inside Naveera Console, where your organization and your role are already known — which means the answer can be about your configuration rather than the general case.

Settings → Support, or ask your organization’s administrator