Problem:
When an admin invites a user to a Fleet Manager organisation, they can only set that user's role and aircraft visibility after the invite is accepted, in a separate members-settings step. Until an admin does that second pass, a newly accepted user has no meaningful access and cannot get going.
Desired outcome:
An admin can nominate the essentials for basic onboarding — Fleet Manager role and aircraft visibility — in the single invite step, so the invited user is productive the moment they accept, with no second admin pass required.
Proposed change:
Let the admin choose a role (Member or Admin) and aircraft visibility (all aircraft or a selected set) when creating the invite. Store those choices with the invite and apply them automatically on acceptance. Other member settings remain optional and unchanged; the invite email is unchanged.