Tenant scoping
Organisation identity comes from the authenticated principal, not from a request parameter a client could change. Cross-tenant reads are structurally unavailable rather than filtered late.
A fleet platform knows where your staff were at 6:45am. That obliges us to be specific about where the data lives, who can reach it, how tenants are separated and what we do when we find a weakness, not to publish a badge and hope nobody asks.
Development fixture figures, not approved for publication.
Vectis is multi-tenant by design. Every query is scoped to the calling organisation at the data-access layer, and gated actions are refused by the API even when a client asks nicely.
Organisation identity comes from the authenticated principal, not from a request parameter a client could change. Cross-tenant reads are structurally unavailable rather than filtered late.
System admin, organisation admin, fleet administrator, finance administrator, pool officer, approver and driver, each with a defined surface. Pool officers see only their own pools.
Plan limits and feature gates are evaluated server-side on every mutation. Hiding a control in the UI is treated as presentation, not security.
Turning on enforced SSO for a fleet of two hundred drivers is a change-management exercise. Vectis gives you enforcement modes, email-domain routing, role mapping from group claims, just-in-time provisioning and audited break-glass accounts, so the rollout can be gradual and reversible.
Optional, SSO preferred or SSO required, set for your organisation, so the switch can be staged.
Joiners, movers and leavers flow from your directory over SCIM, so access follows employment.
A small number of local accounts survive an identity-provider outage, and every use is recorded.
The platform is built so you can implement the policy you have agreed with your people, rather than collecting everything by default and negotiating afterwards.
Journeys classified as private can be recorded without exposing route detail to fleet administrators. The distance and classification are kept for FBT; the map is not published to a manager's screen.
Telematics data is used for the fleet functions it was collected for. Retention windows are configurable, and expired detail is aged out rather than accumulating indefinitely.
Drivers can see their own journey history and classifications in the app. A logbook staff cannot inspect is a logbook staff will not trust.
Administrative access to tenant data is logged. Support staff working a self-service ticket cannot perform enterprise-only actions on your organisation.
In your own region, including backups: New Zealand organisations in New Zealand, Australian organisations in Australia. Residency is the default for every organisation, not an upgrade.
No. Fleet records are not used to train models, and AI retrieval is scoped to your organisation.
Yes. Vehicles, bookings, journeys and trips export as CSV and PDF reports, and are available through the API.
Audited break-glass accounts keep administrative access available, and enforcement can be relaxed while the provider recovers.
Findings from automated and manual testing are recorded on a single register, triaged by severity and tracked to remediation with evidence.
Yes. Send the questionnaire and we will answer it, with architecture and data-handling detail supplied on request.
Technical detail and data-handling answers go out on request, before you spend a procurement cycle on us.