Viewer

What it is

A viewer is a read-only participant in a syndicate. Viewers can see what is going on (the calendar, the members list, the assets and their status) but cannot take any action that changes syndicate state.

The viewer role is useful when you want someone to have visibility without the authority to book, such as a family member, a prospective member before they commit, or a trustee.

Who can use it

Admins can invite a viewer directly, or promote or demote an existing member to or from the viewer role through the member edit dialog.

Where to find it

Viewers appear in the members list with a “Viewer” label. On the Create invite screen, the role selector offers three options (Admin, Member, Viewer), with Viewer carrying an eye icon. Role filter chips on the Members screen omit Viewer from the quick-filter set, but viewers still appear in the full list.

Fields / options

A viewer can:

Action	Where
View the calendar	Syndicate → Calendar.
View bookings (including details subject to privacy settings)	Calendar; Bookings (their own: empty unless they held bookings before becoming a viewer).
View the members list	Syndicate → Members.
View asset details	Syndicate → Assets → asset.
View the fairness dashboard and their own balance	Dashboard cards.
See expenses they submitted before becoming a viewer, whether each was approved, and why one was not	Dashboard → My Expenses, or My Balance → My Expenses.
Update their own profile	Profile tab.
Leave the syndicate	Profile → Manage my syndicates.

A viewer cannot:

Create a booking, or be named on one. The booking service rejects the action with “Viewers cannot create bookings”, and the server refuses a booking made out to a viewer, saying that viewers cannot hold bookings.
Log usage, except on their own booking that has already started or finished; report a squawk, except a defect they record while logging that flight; or submit an expense.
See admin-only queues or settings.

Behaviour rules

The viewer role is enforced on the server, not only in the UI. Even with a crafted request, the server refuses to create a booking for a viewer, and refuses an expense submitted by one.
The app does not offer a viewer the actions the server would refuse. The calendar shows no booking hints and does not respond to a long-press or drag. The Book now app shortcut, the Report Squawk controls, Submit expense, and Log Usage on a maintenance booking are all hidden.
A viewer’s “Bookings” tab lists only bookings from before they became a viewer; they cannot make new ones.
Making a member a viewer cancels their future bookings, including tentative and pending ones, exactly as leaving the syndicate would. The admin is asked to confirm first, and each cancelled booking shows the reason “Member was made a viewer”. The member is sent the usual “Booking cancelled” notice for each one, saying it was cancelled because they are now a viewer. Bookings that have already started or finished are kept for an admin to finalise, and the viewer can still log the flight on one of their own and close it early. Maintenance they booked as an admin stays, because it belongs to the syndicate.
A defect a viewer records on the Log Flight form while logging a flight on their own booking goes into the tech log like a member’s: it names the flight, and waits for an admin to confirm it if the syndicate asks for that. This is the only squawk a viewer can report; the standalone Report Squawk controls stay hidden, and the server refuses any other squawk from a viewer.
If one of those future bookings already has a flight logged against it, the change of role is refused until that booking is sorted out.
Promoting a viewer to member is reversible and has no financial effect on its own, though the admin may also want to change the member’s type or billing scheme at the same time.
All privacy settings that apply to members apply identically to viewers; they see only what the syndicate’s privacy configuration allows.