Everyone sees everything
In a shared spreadsheet, sales reads the salaries and the accountant can rewrite a closed mission. Nobody wants that; nobody prevents it.
Part of the service, across every module
What protects your company
A management system deserves two questions before you buy it: what does it stop me from doing wrong, and who owns my data. This page answers both — with the product’s real constraints, including the ones that look like limitations and are exactly what you are paying for.
7 roles
from director to driver, separated rights
Append only
money ledgers are never rewritten
Your data
exportable at any time
What people notice too late
The figure corrected in silence
A cell edited afterwards leaves no trace. The total changes, and the version that supported the decision no longer exists.
Data held hostage
The day you want to leave, the history stays inside the vendor’s software, in a format nobody can read.
The guarantees, one by one
Every company is isolated inside the database
Isolation is not a filter written in application code but a rule enforced by the database itself on every multi-company table. A query cannot return another company’s row, even after a programming mistake.
The detail that matters. An automated test walks every table and fails if one is added without its isolation rule: the protection does not depend on a developer’s vigilance on a Monday morning.
Seven roles, two checks
Director, dispatcher, sales, accountant, mechanic, driver, administrator: the menu is built from the role and the modules. Sales issues an invoice without being able to collect it; the mechanic never sees the bank.
The detail that matters. The interface check and the API check are one and the same. What does not appear in your menu is not reachable through a direct link — an internal rule of the product, not two lists kept in parallel.
Issued documents no longer change
Order form, invoice, credit note: issuance freezes the content and the document keeps its own copy of what it prints. Changing a client tariff tomorrow does not rewrite paper that went out yesterday.
The detail that matters. A mistake is corrected by a corrective document with its own series — the way accounting works, and the only way that survives an audit.
Money is written append-only
Client payments, movements of paper, bank statement lines: these ledgers only grow. A correction is an additional entry, dated and attributed, never a rewrite.
The detail that matters. Un-matching a reconciliation is a counter-entry; a wrong statement import is rolled back as a batch, with everything it created.
Repetitions do not create duplicates
A double click, a dropped connection, a re-imported file: every operation carries its identifier, and the product recognises the retry instead of creating a second file or a second payment.
The detail that matters. Real repetitions are preserved: two identical fill-ups on the same day stay two lines. Deduplication counts occurrences, it does not delete what looks similar.
Your data stays yours
Export at any time, hosting in Morocco or on AWS as contracted, and a demonstration dataset erasable with one button — what was generated goes, what you entered stays, row by row.
The detail that matters. Geolocation positions, when the module arrives, will only be collected during an active mission: tracking serves operations, not surveillance of people.
The product runs on its own
Your subscription billing lives in the TinyCIO hub, not in the product. If the link to the hub is unavailable, your portal keeps working on its local rules: operations do not stop for a commercial reason.
The detail that matters. No transfer is ever issued by the product, and no access to your bank is requested: payment orders produce a file that you upload yourself.
my.transport.tinycio.ma/settings
Security & data
Team & roles
5 workplace seats · rights by job
| Member | Role | Access | Can collect |
|---|---|---|---|
| Director | owner | everything | yes |
| Dispatcher | dispatcher | operations, documents | no |
| Sales | sales | clients, quotes, invoices | no |
| Accountant | accountant | invoices, purchases, bank | yes |
The constraints you are buying
Expired paperwork blocks the truck
An expired licence or insurance makes the assignment impossible. It is an inconvenience on a Tuesday morning; it is a fine avoided and an insurer that cannot walk away after an accident.
No invoice without a signed CMR
The refusal is explicit and names the file. Invoicing without proof of delivery means funding a dispute you will lose.
The numbering cannot have a gap
The number is allocated at issuance, atomically, with one series per year. Two simultaneous approvals never produce the same number.
A container number with history is locked
Renaming it would silently transfer one box’s history to another — and that history is your defence in a damage dispute.
No extra charge: these guarantees are part of the service, whatever your subscription.
They cannot be switched on or off. A product whose security is an option is selling the same thing twice.
Frequently asked questions
Where is our data hosted?
In Morocco or on AWS, as agreed in the contract. The data belongs to your company and is exportable at any time, without prior request.
What happens if we stop the subscription?
The screens of the switched-off modules close, the data stays. You export what you want to take with you; nothing is deleted to force you to stay.
Can an employee delete an inconvenient invoice?
No. An issued invoice cannot be modified or deleted: it is cancelled by a credit note, which leaves both documents visible. And issuing and collecting are separate rights.
See also