Owners can invite mechanics again; who adds aircraft is an admin setting

- 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>
This commit is contained in:
rickyandClaude Opus 5.5 committed 2026-11-15 19:09:49 -05:00
1 parent 19bc3efa19
commit 9a20c91f5e
30 files changed
+219 -40

No files matched your search

+18
View File
@@ -169,4 +169,22 @@ class SsoTest < ActionDispatch::IntegrationTest
assert_not User.exists?(email_address: "someone.else@example.com")
assert_equal 0, invitation.reload.uses_count
end
test "an Owner's signing invitation makes the mechanic's account by signing in with SSO, for its address only" do
ENV.delete("OIDC_AUTO_CREATE_USERS")
owner = create_user("owner3@example.com")
aircraft = create_aircraft(owner: owner, tail_number: "N888CD")
entry = aircraft.logbook_entries.create!(date: Date.new(2026, 10, 1), log_type: "AC", entry_type: "MAINTENANCE", aircraft_hours_at_entry: 1000, text: "Oil changed.")
invitation = entry.signing_invitations.create!(email: "mech@example.com", invited_by: owner)
get invited_signing_path(invitation.token)
mock(uid: "sub-other", email: "not.mech@example.com")
sso_sign_in
assert_not User.exists?(email_address: "not.mech@example.com")
get invited_signing_path(invitation.token)
mock(uid: "sub-mech", email: "mech@example.com", name: "Mo Mechanic")
sso_sign_in
assert_equal "sub-mech", User.find_by!(email_address: "mech@example.com").sso_uid
end
end