The single source of truth for what each role can do in a syndicate. Every capability the UI exposes appears in exactly one row. When the code and this matrix disagree, the code wins and this page is wrong — please report it.
Anyone. This page is aimed at admins and owners 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.
This is a reference page. In the app, the role selector in the Create invite screen and the Edit member dialog is where roles are assigned.
A tick (yes) means the role can perform the action. A dash (—) means it cannot. A subscript note expands on a non-obvious rule.
| Capability | Owner | Admin | Member | Viewer |
|---|
| Create a syndicate (becomes its owner) | yes | yes | yes | yes |
| Edit syndicate name / branding / business details | yes | yes | — | — |
| Delete the syndicate | yes | — | — | — |
| Transfer ownership (promote another member to owner) | yes | — | — | — |
| Leave the syndicate | yes¹ | yes² | yes² | yes |
¹ The last remaining owner cannot leave until they transfer ownership.
² Not permitted while an outstanding balance is owed to the syndicate.
| Capability | Owner | Admin | Member | Viewer |
|---|
| Invite new members | yes | yes | — | — |
| Change another member’s role (to admin, member, or viewer) | yes | yes | — | — |
| Promote a member to owner | yes | — | — | — |
| Remove a member | yes | yes | — | — |
| Edit own profile, timezone, and notification preferences | yes | yes | yes | yes |
| Capability | Owner | Admin | Member | Viewer |
|---|
| Add an asset | yes | yes | — | — |
| Edit asset metadata | yes | yes | — | — |
| Archive / delete an asset | yes | yes | — | — |
| View asset details, meter readings, airworthiness | yes | yes | yes | yes |
| Capability | Owner | Admin | Member | Viewer |
|---|
| View the calendar | yes | yes | yes | yes |
| Create a booking | yes³ | yes³ | yes | — |
| Pencil in a tentative booking | yes | yes | yes | — |
| Confirm own tentative booking | yes | yes | yes | — |
| Cancel own booking | yes | yes | yes | — |
| Approve another member’s pending booking | yes | yes | — | — |
| Reject another member’s pending booking | yes | yes | — | — |
| Subscribe to personal ICS calendar feed | yes | yes | yes | yes |
³ Admin and owner bookings skip the pending queue even when the syndicate requires approval. See Booking statuses.
| Capability | Owner | Admin | Member | Viewer |
|---|
| Log usage for own booking | yes | yes | yes | — |
| Edit a past usage log (own) | yes | yes | yes | — |
| View asset-level usage history | yes | yes | yes⁴ | yes⁴ |
⁴ Visibility is subject to the syndicate’s usage log visibility setting.
| Capability | Owner | Admin | Member | Viewer |
|---|
| Report a squawk | yes | yes | yes | — |
| Confirm or dismiss a reported squawk | yes | yes | — | — |
| Defer a grounding squawk | yes | yes | — | — |
| Resolve a squawk | yes | yes | — | — |
| Add / edit maintenance items | yes | yes | — | — |
| Log a maintenance task | yes | yes | — | — |
| Capability | Owner | Admin | Member | Viewer |
|---|
| View own balance | yes | yes | yes | yes |
| Submit an expense | yes | yes | yes | — |
| Approve or reject an expense | yes | yes | — | — |
| Set up asset billing rates | yes | yes | — | — |
| Create and assign billing schemes (member rates) | yes | yes | — | — |
| Finalise a booking | yes | yes | — | — |
| Bulk-finalise zero-shortfall bookings | yes | yes | — | — |
| Record a payment made outside the app | yes | yes | — | — |
| Download a monthly statement | yes | yes | yes | yes |
| Capability | Owner | Admin | Member | Viewer |
|---|
| Import bookings from Goboko or CSV | yes | yes | — | — |
| Export a tech log (PDF / CSV) | yes | yes | — | — |
| Capability | Owner | Admin | Member | Viewer |
|---|
| Change booking policy (approval required, advance window, minimum duration) | yes | yes | — | — |
| Change privacy settings (show member names on bookings, usage log visibility, share usage photos) | yes | yes | — | — |
| Change billing and scheme settings | yes | yes | — | — |
| Change subscription tier | yes | yes | — | — |
- Admins and owners are treated identically by most of the service layer. The owner-only actions — delete syndicate and promote to owner — are the exceptions.
- Role capability is enforced both in the UI (buttons are hidden) and at the service layer (requests are rejected). Viewer booking attempts, in particular, are rejected server-side even if the UI were bypassed.
- “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.
