- Admin → Settings → Who can add aircraft: administrators only (the
default) or everyone. Adding an aircraft or importing a .sam.zip makes
you its Owner, so this decides who can become one.
- A signing invitation from an Owner of the aircraft (or an
administrator) lets the outside mechanic create an account for the
invited address again, with a password or by signing in with SSO;
checked when it's used. Others' signing invitations still need an
existing account, and say so.
- Docs: who makes accounts, the new setting.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Anyone can add an aircraft and so manage its people, so invitations from
non-administrators could bring in new accounts without an administrator.
- An invitation makes a new account only if whoever made it is still an
administrator when it's used; an aircraft's Access page invitations are
for people who already have an account (its welcome page says so).
- Signing invitations no longer make accounts: the mechanic needs one
first, and the owner is told when they don't have one.
- With SSO, "Continue with <provider>" on an administrator's invitation
makes the account and accepts the invitation (only for its address when
it has one), so invitations work without OIDC_AUTO_CREATE_USERS. That
setting stays, documented as giving accounts without an invitation; the
Authentik example now leaves it off.
- Docs: who makes accounts (guide, README, Authentik, .env.example, API).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
What people can do on an aircraft now comes from their role there, and
administrators set what each role allows (Admin → Roles).
- Roles are installation-wide sets of permissions (31, grouped as flying,
squawks and notes, maintenance records, imports and exports, the
aircraft, notifications). Seeing an aircraft's records needs none.
- Built in: Owner (always every permission, so an aircraft can always be
managed), Mechanic (shop maintenance: logbook, signing, components,
inspections, ADs, squawks, reminders), Pilot (what pilots could do
before) and Viewer (view only). Administrators can change all but
Owner's, and add their own; a role can be deleted once nobody has it.
- Existing owners and pilots keep exactly what they could do.
- Admin → Users → a user lists their role on every aircraft, to change,
remove or add. On the aircraft's Access page, anyone who manages people
hands out roles, but only an Owner can give or take away Owner, nobody
changes their own (except administrators), and an aircraft always
keeps an Owner (AircraftAccess).
- Controllers declare the permission each action needs; a request that
changes something with none declared is refused (and raises in
development and tests), and a test walks every route to check.
- Weekly reminders and overdue alerts go to roles that get reminders;
the DRS reminder also needs Manage ADs. The API follows the person's
role; its owners_only error is now not_permitted.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Setup checklist on a new aircraft's Overview (owners): components,
standard inspections, DRS AD import, registration/airworthiness
certificate, weight and balance; hideable per device
- Log Flight: "Save and log next leg" reopens the form on the same date,
starting where the leg ended
- Component form: limits in two collapsible groups (replacement and expiry;
overhaul and TBO), open when in use
- Squawk form warns what "Ground Aircraft" does
- Logbook entry form: inspection result only for inspection entries
(show-when controller); document names default from the file
- Dates in pickers, the activity log, airworthiness lines, search, audits
and transcription notes use the app format
- No duplicate Report Squawk button on Squawks; "Record service" label
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Offline
- Flights and squawks saved offline are tagged with their user and only sent
while that user is signed in; storage is made persistent; Background Sync
sends them with the app closed (Chromium); unsent count on the app badge
- Report Squawk works offline (photos included, one-time key like flights)
- The Fleet page and, for each of your aircraft, the Overview, W&B, Log
Flight and Report Squawk pages and photo are saved ahead of time, so the
app opens and works without signal; copies say when they were saved
- Sign-out clears saved forms, pages and photos (asks first if items wait)
- Offline page rendered by Rails (localized, follows the theme, no inline
script); service worker version follows the build
Install and notify
- Web Push (web-push gem, VAPID keys from env or storage/vapid_keys.json):
grounding squawks, newly overdue items (daily, once each), signing
requests; per-device on/off and test in Profile -> This device; only
browser push service endpoints accepted
- Manifest shortcuts (Log Flight, Report Squawk via /go/...), lang and
localized description; install help on Profile; reload notice after a
release
Also
- Dockerfile: libssl-dev in the build stage (openssl gem); lockfile checksums
- Leftover English and %{_} interpolation names from the localization pass
- Guide and README updated
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Views use lazy t(".key") lookups; sentences with values or links stay
whole (interpolation, _html keys); counts use one/other plurals
- Stored-value labels (statuses, types, priorities...) are LabelSets read
from labels: in the current locale; field names and validation messages
under activerecord:; flash and activity text under flash:
- Services, models, helpers, mailer subjects, the logbook PDF, procedures
templates, records package README and transcription warnings localized;
the PDF reuses LogbookEntry#certification_statement instead of a copy
- Scripts read js: strings from a JSON tag via app/javascript/i18n.js
- Dates through I18n.l (app, weekday, month_year, long formats); html lang
follows the locale
- APP_LOCALE picks the language (falls back to English); missing
translations raise in development and tests
- README: Translating section and APP_LOCALE
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Sign an entry: review exactly what's certified, choose a current
certificate (eligibility checked: pilot only for preventive maintenance,
inspections need their result and time), re-enter the password or sign
in again with SSO (prompt=login, within 5 minutes), and confirm the
"Certified by" statement (43.9 return to service, 43.11(a)(5) for
inspections, preventive maintenance for pilots)
- The signature stores signer, certificate, statement, UTC time, how they
authenticated, IP/browser, a SHA-256 fingerprint of the entry's content
and a readable snapshot; an HMAC seal covers the signature record. Status
shows Valid / Superseded / Altered since signing. The signer is emailed
- Signed entries (and their sub-components) can't be edited or deleted;
a correction entry, once signed, supersedes the original (kept)
- Owners invite an outside mechanic by email to sign one entry: one-time,
14-day link; they create or use their own account and certificate and
see only that entry
- Admins can disable accounts (signed out, can't sign in or sign; past
signatures kept); users with signatures can't be deleted
- Printouts show the electronic signature and fingerprint; archives carry
signatures (marked imported, with their origin) and corrections
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>