Data separation
Each organization's data is separated at the database level; one organization's records never appear in another organization's queries. This separation is enforced in database rules, not in application code.
Permissions
Role-based access: owners and fleet managers can edit, drivers see their own records, and read-only users can only read. Unauthorized actions are rejected on the server side.
Audit trail
Field-level change history is kept: who changed which value to what, and when. Bulk updates are written to this log as well.
Transport security
All traffic is carried over HTTPS, and certificates renew automatically.
What does it cover?
- Data separation by organization
- Role-based authorization
- Change history
- Session management
- Per-record file archive
- Export
How does it work?
- 01
Your organization stays separate
Each organization's data is kept within its own scope.
- 02
Assign roles
Define user permissions by role.
- 03
Leave a trail
Field-level change history answers who changed what, and when.
- 04
Take your data
Lists can be exported as CSV; your data stays yours.
Frequently asked questions
Yes. All lists can be exported as CSV along with your column selection.
Can't find what you're looking for? Get in touch with us.
Let's prepare a demo for your fleet
We'll ask for a few details and get back to you within one business day.
Request a demo