A billing clerk cannot void
A billing clerk raises invoices and applies cash, but cannot void an invoice or issue a credit memo.
Four questions, four separate answers.
Signed in? Whose data? Allowed? What happened? Lanexa answers each one separately, and the one that keeps your company's data apart from every other company's is decided by the database, on every request.
- Your data
- Kept apart
- Permissions
- Per person
- Card numbers
- Never stored
- Every change
- On the record
Kept separate on purpose
Each mechanism answers one question and nothing else. Keeping them separate is the design.
- 01
Are you signed in?
Sign-in
Email and password or an emailed magic link, with password reset. Public pages such as tracking search and quote acceptance sit behind a bot check.
- 02
Whose data is this?
Kept apart
Your company's data is kept apart from every other company's by the database itself, on every request, whatever a screen asks for.
- 03
Are you allowed?
Permissions
Permissions are held per person, per company, and the database enforces them on the records that matter, not only the buttons on screen.
- 04
What happened?
A record
Changes are recorded with who made them and when, in a tamper-evident record that makes any alteration detectable.
Your most sensitive records never reach a browser.
Some records are kept where only Lanexa's own servers can reach them. No signed-in user, however senior, can read or change them from a browser.
That is where Lanexa keeps the things that would hurt most if they leaked.
- Your connection credentials, such as an ELD account
- Your QuickBooks connection
- Payment events from the payment processor
- Identity documents uploaded at signup
- The terms you accepted, and when
- Outbound email
Ready-made roles, and permissions per person
Permission is a set of named capabilities held by a person in a specific company — not a job title. The roles below are ready-made bundles, and any person's capabilities can be adjusted individually. Someone can administer one company in a group and only read another.
| Role | What it is for |
|---|---|
| Company Administrator | Full control of the company. |
| Controller | The full books: receivables, payables, settlements, the ledger and period close. |
| Accounting | Day-to-day receivables and payables, with financial visibility. |
| Dispatcher | Runs the freight. Rate visibility is not part of the role by default. |
| Safety & Compliance | Compliance, credentials, documents and customs. |
| Billing Clerk (A/R) | Creates invoices and applies cash. Cannot approve or void. |
| A/P & Settlements Clerk | Enters bills and runs settlements. Approval is someone else’s. |
| Sales / CSR | Quotes and customer relationships. |
| Driver | Messages, and their own loads and documents. |
| Viewer | Read-only. |
| Demo Viewer | Read-only demo access. |
Users, roles and per-person permissions are on Start and up. Solo has one office user.
An A/P clerk cannot approve
An A/P clerk enters carrier bills and runs settlements, but cannot approve a bill.
Two people for driver pay
A driver settlement run is approved by someone other than the person who created it. The database refuses the creator.
Money shown to those who need it
Rates, margins and totals are masked on the load ledger and dashboard for roles without rate visibility.
A hidden button is a courtesy, not the control. For the records that matter, loads among them, the database itself refuses a change from a person whose permissions do not allow it.
Every change, on the record.
Changes are written with who made them and when. Every business event joins a tamper-evident record, and a Verify check confirms it, so any alteration is detectable.
The Activity log is on Start and up.
Money, AI and credentials
Card numbers never touch Lanexa
Where a plan asks for a card, it is typed into Stripe's own payment field. No card number reaches Lanexa's servers, database or code, and nothing is charged at signup.
AI that never sees your data
Ask Lanexa turns a question into a report; it never computes a number and never sees your data. Money figures stay hidden from anyone without rate visibility.
Connection credentials locked away
A Samsara or Geotab credential is checked with the provider, then stored encrypted for your company and never shown again.
Usage data skips what you type
Product analytics record which screens and controls are used, never the values typed into them.
User content is cleaned
Anything a user supplies is cleaned before it is displayed.
Security questions
How does Lanexa keep one company's data away from another?
The database itself keeps every company's data apart, on every request.
Your most sensitive records, such as connection credentials and identity documents, cannot be reached from a browser at all.
Can a dispatcher see our rates?
Rates, margins and totals are masked on the load ledger and dashboard for roles without rate visibility, and the dispatcher role does not include it by default.
Visibility is set per person, per company.
Does Lanexa store card numbers?
No. A card is entered in Stripe's own payment field and never reaches Lanexa's servers, database or code.
Does Lanexa's AI see our data?
No. Ask Lanexa turns your question into the same report the report builder makes by hand, and the report engine does the arithmetic.
The AI never computes a number and never sees your data.
Can I see who changed a record?
Yes. Changes are recorded with who made them and when, and the record is tamper-evident, so any alteration is detectable.