Organization profile and time zone

The settings that everything else derives from — especially the operating time zone.

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

The organization profile holds your legal and operating details, and one setting that has more downstream consequences than any other: the operating time zone.

Why the time zone matters so much

An operating day is a local concept. Scheduling boundaries, day filters on the trip list, claim periods and reporting all resolve against the organization's zone, not the browser's. A user working from a different zone still sees the operation's day, which is what makes a distributed dispatch team possible.

Operational policy

  • Cancellation policy — whether drivers may cancel their own trips, and what they must record.
  • Completion rules — who may mark a trip complete, and under what conditions.
  • No-show waiting window — how long a driver waits before a no-show can be recorded.

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