Every request
Kept apart, every time
The database itself decides what each request may return, so one company's records are never reachable from another company's session, whatever a screen asks for.
Every plan
One company cannot reach another's records.
Separation between companies is applied by the database on every request, not by the application remembering to ask correctly. Inside a company, ready-made roles decide who may do what, and the database enforces them on the records that matter.
How it tends to work without this
A lot of multi-company software separates customers in application code: every query is supposed to add "and company = yours". That works until one query, somewhere, forgets — and the failure is silent, because the data was always reachable; it simply had not been asked for.
What Lanexa does, and on which plan
Out of reach
The most sensitive data is out of reach
Your connection credentials, your QuickBooks connection, payment events and identity documents are kept where only Lanexa's own servers can reach them. No signed-in user can read them from a browser.
Every plan
Roles
Capabilities per person, per company
Ready-made roles bundle named permissions, and any person's permissions can be adjusted individually. They are held per company, so the same person can run one company in a group and only read another.
Start and up (Solo has one office user)
Duties
Separation of duties
A billing clerk can raise an invoice but cannot void one. An A/P clerk can enter a carrier bill but cannot approve it. Whoever creates a driver's settlement cannot approve it — the database refuses, even for an administrator.
Start and up
Writes
Hidden buttons are not the defence
For the records that matter, the database itself refuses a change from someone whose permissions do not allow it, so going around the screen does not get around the rule.
Every plan
History
A record that shows tampering
Changes are recorded with who and when, in a tamper-evident record where any alteration is detectable.
Audit log on Start and up
What it means on a Tuesday
Two carriers run under one group. A dispatcher who belongs only to the first opens the load list and sees that company's loads — the second company's rows are not reachable from that session at all. If a query somewhere forgot to filter by company, it would still return only what the database allows. And because the dispatcher's role does not include rate visibility, rates, margins and totals are masked on the load ledger and dashboard.
Questions about this claim
Can another Lanexa customer see my data?
No. The database returns only the records of the companies you are a member of, on every request, and your most sensitive records cannot be reached from a browser at all.
Does Lanexa store card numbers?
No. Card numbers go straight to the payment processor through its own secure field and never touch Lanexa.
Can I stop a dispatcher from seeing our rates?
Yes. The dispatcher role does not include rate visibility, and rates, margins and totals are masked on the load ledger and dashboard for roles without it.
Visibility is set per person, per company.