Role capability matrix
What it is
Section titled “What it is”The single source of truth for what each role can do in a syndicate. Every role-gated capability the UI exposes appears in exactly one row; the one documented exception is casting a vote, which is gated by shares rather than role, and is called out as a note rather than a row. When the code and this matrix disagree, the code wins and this page is wrong; please report it.
Who can use it
Section titled “Who can use it”Anyone. This page is aimed at admins deciding which role to give a new member, but it is useful for any member who wants to understand what their fellow members can and cannot do.
Where to find it
Section titled “Where to find it”This is a reference page. In the app, the role selector in the Create invite screen and the Member detail screen is where roles are assigned.
Fields / options
Section titled “Fields / options”A tick (yes) means the role can perform the action. A dash (—) means it cannot. A subscript note expands on a non-obvious rule.
Syndicate lifecycle
Section titled “Syndicate lifecycle”| Capability | Admin | Member | Viewer |
|---|---|---|---|
| Create a syndicate (becomes its first admin) | yes | yes | yes |
| Edit syndicate name / branding / business details | yes | — | — |
| Close the syndicate | yes | — | — |
| Leave the syndicate | yes¹ | yes¹ | yes¹ |
¹ Not permitted if it would leave the syndicate without an admin, or while you have unresolved payments or bookings (for example, an unsettled balance, or a recent flight not yet finalised). The server enforces this; Leave a syndicate lists exactly what counts.
Membership
Section titled “Membership”| Capability | Admin | Member | Viewer |
|---|---|---|---|
| View the members list | yes | yes | yes |
| Invite new members | yes | — | — |
| Change own or another member’s role, shares or billing scheme | yes | — | — |
| Remove a member | yes | — | — |
| Edit own profile, timezone, and notification preferences | yes | yes | yes |
Assets
Section titled “Assets”| Capability | Admin | Member | Viewer |
|---|---|---|---|
| Add an asset | yes | — | — |
| Edit asset metadata | yes | — | — |
| Archive / delete an asset | yes | — | — |
| View asset details, meter readings, airworthiness | yes | yes | yes |
Bookings
Section titled “Bookings”| Capability | Admin | Member | Viewer |
|---|---|---|---|
| View the calendar | yes | yes | yes |
| Create a booking | yes² | yes | — |
| Create a booking in the past, to record a flight already flown | yes | own, up to 4 hours after it started | — |
| Pencil in a tentative booking | yes | yes | — |
| Confirm own tentative booking | yes | yes | — |
| Cancel own booking | yes | yes | — |
| Approve another member’s pending booking | yes | — | — |
| Reject another member’s pending booking | yes | — | — |
| Subscribe to personal ICS calendar feed | yes | yes | yes |
² Admin bookings skip the pending queue even when the syndicate requires approval. See Booking statuses.
| Capability | Admin | Member | Viewer |
|---|---|---|---|
| Log usage for own booking | yes | yes | own⁴ |
| Log usage on another member’s booking once it has ended | yes | — | — |
| Log usage on a maintenance booking | yes | yes | — |
| Edit a past usage log (own) | yes | yes | own⁴ |
| View asset-level usage history | yes | yes³ | yes³ |
³ Everyone sees the usage history itself (hours and landings); the money figures on other members’ logs are subject to the syndicate’s usage log visibility setting. A flight on your own booking, including one an admin recorded for you, and a flight you logged yourself always show you their money figures.
⁴ Only on a booking they held before being made a viewer that had already started or finished; future ones are cancelled.
Maintenance and squawks
Section titled “Maintenance and squawks”| Capability | Admin | Member | Viewer |
|---|---|---|---|
| Report a squawk | yes | yes | — |
| Record a defect when logging a flight | yes | yes | own⁵ |
| Confirm or dismiss a reported squawk | yes | — | — |
| Defer a grounding squawk | yes | — | — |
| Resolve a squawk | yes | — | — |
| Add / edit maintenance items | yes | — | — |
| Log a maintenance task | yes | — | — |
| Defer a maintenance limit | yes | — | — |
⁵ Only while logging a flight on a booking of their own that had already started or finished (see ⁴). The defect goes into the tech log like a member’s, and waits for an admin to confirm it if the syndicate asks for that.
Finance
Section titled “Finance”| Capability | Admin | Member | Viewer |
|---|---|---|---|
| View own balance | yes | yes | yes |
| Submit an expense | yes | yes | — |
| Approve or reject an expense | yes | — | — |
| Set up asset billing rates | yes | — | — |
| Create and assign billing schemes (member rates) | yes | — | — |
| Finalise a booking | yes | — | — |
| Close your own booking (post its charge), while the syndicate lets members close their own bookings | yes | yes | own⁴ |
| Bulk-finalise zero-shortfall bookings | yes | — | — |
| Record a payment made outside the app | yes | — | — |
Governance
Section titled “Governance”| Capability | Admin | Member | Viewer |
|---|---|---|---|
| Open a vote | yes | — | — |
| Cancel a vote | yes | — | — |
| Close a vote early | yes | — | — |
| See who has voted on an open vote (never how) | yes | — | — |
Note: casting a ballot is not role-gated, so it has no row above. It depends on whether the member holds a share, not their role: any admin, member, or viewer who is an equity member can vote, and a member with no shares cannot, regardless of role. See Vote.
Import and export
Section titled “Import and export”| Capability | Admin | Member | Viewer |
|---|---|---|---|
| Import bookings from Goboko or CSV | yes | — | — |
| Export a tech log (PDF / CSV) | yes | — | — |
Settings
Section titled “Settings”| Capability | Admin | Member | Viewer |
|---|---|---|---|
| Change booking policy (approval required, advance window, minimum duration) | yes | — | — |
| Change privacy settings (show member names, usage log visibility, share usage photos) | yes | — | — |
| Change billing and scheme settings | yes | — | — |
| Change subscription tier | yes | — | — |
Behaviour rules
Section titled “Behaviour rules”- There is no owner role. Ownership is expressed through shares; admins operate the syndicate, and the member who created it holds no special powers.
- Role capability is enforced both in the UI (buttons are hidden) and on the server (requests are rejected). Viewer booking attempts and viewer expense submissions, in particular, are rejected server-side even if the UI were bypassed.
- Admins may edit their own membership, including demoting themselves to member or viewer. Share changes retain the open-vote warning, and a viewer demotion retains the future-booking confirmation.
- A syndicate must always keep at least one active admin. The server refuses to demote or remove the last admin of an open syndicate.
- Making a member a viewer cancels their future bookings, including tentative and pending ones, the same way leaving the syndicate does. Bookings that have already started or finished are kept, and the new viewer can still log a flight on one of their own and close it early. See Viewer.
- A member cannot be removed while they have unresolved payments or bookings (an unsettled balance, or a flight not yet finalised). This is enforced on the server; Remove a member lists what counts.
- “Renter” is a common name for a member rate (billing scheme label), not a role. It does not appear in this matrix. See Roles and member rates.