Security & trust
Built for shops whose records are on the line.
Aviation maintenance is a liability-sensitive trade. The page below states how Dash Aero actually works — not promises about it. These are architecture facts: tenant isolation, deliberate publication, append-only records, explicit authority, and an AI that proposes rather than decides.
Your data is yours
One shop can never read another shop’s data
Every shop runs in its own isolated tenant. A mechanic at one shop has no path — accidental or intentional — to the records, findings, or customer correspondence of another. The boundary is enforced by the data model, not by a permission someone could forget to set.
- A vendor or expert joins through Collaboration Rooms with access to the specific maintenance event — not the shop, not the aircraft, not the customer history.
- Every external grant ends. There is no permanent session and no standing key; access lapses on the date the shop set when it opened the door.
- Every external action — view, comment, upload — is written to the same audit trail as internal work. The shop can read back exactly who saw what, and when.
Publication is deliberate
Nothing internal reaches a customer as a side effect
Mechanic notes, images, and findings live internal by default. A customer sees only what the shop chooses to publish — and every publication is versioned, scoped to a specific audience, and correctable. The Operator Portal renders from that deliberate publication history, not from a parallel copy of the truth.
Records integrity
Signed records lock. Corrections amend, never overwrite.
When a mechanic signs an entry in the Aircraft Service Record, that signature locks the record. A later correction adds a signed, dated amendment that references the original — the original report is never overwritten and never deleted. Every action — capture, edit, sign, publish, correct — writes to a complete audit trail.
Authority is explicit
Technical, financial, and signature authority are separate things
Access is not authority. A user can be permitted to see a record without being permitted to approve the work, commit the spend, or sign the inspection. Inspection independence is enforced by the product: the person who signs an inspection cannot be the person who performed the work, and advice from a collaborator never counts as an inspection. The rules hold whether the shop remembers them or not.
- Technical
- Who can approve the work, sign an inspection, release an aircraft.
- Financial
- Who can commit spend against the event, up to the threshold the shop set.
- Signature
- Who can sign a record — held by a named, qualified human, never by a tool.
AI boundaries
Copilot proposes. People confirm. People sign.
Dash Aero treats AI as an assistant, not an authority. The four guarantees below are product behavior, enforced by the same rules that govern the rest of the record.
Copilot proposes, humans confirm
Technical Intelligence drafts, retrieves, organizes, and extracts — it never commits a fact to the record on its own. Every proposed entry carries its source so the mechanic can confirm or reject it.
AI never approves work or spending
Approval authority — technical or financial — stays with the people the shop has named. Copilot cannot approve a maintenance event, authorize a parts purchase, or release work back to a customer.
AI never signs
Copilot cannot sign an inspection. Copilot cannot sign a maintenance record. Airworthiness and part-eligibility determinations rest with the qualified, named human who holds that authority.
AI never hides uncertainty
Copilot cannot conceal uncertainty behind a confident answer, and it cannot turn a casual conversation into a controlled approval. Where it is unsure, it says so and points to the source.
Put plainly: Copilot cannot approve work, cannot approve spending, cannot determine part eligibility, cannot determine airworthiness, cannot sign an inspection, cannot sign a maintenance record, cannot conceal uncertainty, and cannot convert a casual conversation into a controlled approval. Those are the rules the platform is built to enforce.