Admin
What it is
Section titled “What it is”An admin is a member with operational control of a syndicate. Admins handle day-to-day management: inviting members, adding assets, approving bookings, confirming squawks, finalising bookings, approving expenses. Admins also hold the syndicate-level powers: changing settings, managing the subscription, and closing the syndicate. There is no role above admin; ownership of the aircraft is expressed through shares, not through a role.
A syndicate can have any number of admins, and must always keep at least one.
Who can use it
Section titled “Who can use it”Admins can promote members to admin, and demote admins to member, from the member edit dialog. The member who creates a syndicate starts as its first admin.
Where to find it
Section titled “Where to find it”Open any syndicate and go to the Members screen — Admin → Members, or the My Syndicate card on the Dashboard. Members is a screen, not one of the syndicate’s tabs; the tabs are Dashboard, Calendar, Asset(s), Admin (admins only) and Profile. Admins carry an “Admin” label in the list. To promote a member, tap the member tile (admins only) and change the role in the edit dialog.
Fields / options
Section titled “Fields / options”Admin-only UI elements across the app:
| Action | Where |
|---|---|
| Invite members | Members screen floating action button; Members → invite route. |
| Change another member’s role | Member edit dialog, role field. |
| Remove a member | Member edit dialog, remove button, guarded for last-admin, and for unresolved payments or bookings. |
| Add an asset | Assets tab floating action button; Assets → new route. |
| Edit / archive an asset | Asset detail screen. |
| Approve or reject pending bookings | App bar badge in the syndicate shell when there are pending bookings. |
| Confirm or dismiss reported squawks | App bar badge in the syndicate shell when there are unconfirmed squawks. |
| Finalise a booking | Booking detail, and the unfinalised-bookings queue. |
| Bulk finalise zero-shortfall bookings | Unfinalised-bookings queue. |
| Approve or reject an expense | Expense approval screen. |
| Record a payment made outside the app | Member balance screen. |
| Import bookings from CSV | Syndicate settings → Import bookings. |
| Edit syndicate settings (billing, privacy, policy) | Syndicate settings hub. |
| Manage the subscription | Admin tab → Subscription. |
| Close the syndicate | Edit syndicate screen, destructive-action section. |
| Export a tech log PDF | Asset detail → Tech log export. |
Behaviour rules
Section titled “Behaviour rules”- Admins can change roles and remove members. These guards are enforced on the server, not just in the app:
- A syndicate must always keep at least one active admin. The server refuses to demote or remove the last admin of an open syndicate, and refuses to delete that admin’s account.
- A member cannot be removed while they have unresolved payments or bookings (an unsettled balance, or a flight not yet finalised). Sort those first; Remove a member lists what counts.
- Admin actions like finalisation and expense approval generate audit trail entries; the action records who performed it and when.
- Any admin can manage the subscription and close the syndicate. Closing is described in Close a syndicate.
- An admin editing themselves can demote themselves to member, unless they are the syndicate’s last admin.
See also
Section titled “See also”- Member: the standard booking-and-using role.
- Viewer: read-only access.
- Role capability matrix: the full table of who can do what.