Default and per-asset settings

What it is

Most syndicates own one asset. Multi-asset syndicates are the minority. Syndik8 is built around that shape: when a syndicate has a single asset, billing settings live in one place — on the syndicate. There is no separate asset-level billing screen. The fields on the Asset rates screen are just called Billing, Minimum Usage, and Home airfield fees. Usage capture has its own screen — see Usage capture.

When a syndicate adds a second asset, the UI changes. Those same syndicate-level settings stay where they were, but the headings are relabelled with a “Default” prefix — Default Billing, Default Minimum Usage, Default home airfield fees. At the same time, a new per-asset billing screen appears for every asset. On each asset’s screen you can either leave the value empty (in which case the syndicate default applies) or enter a value that overrides the default for that asset only.

The result: single-asset syndicates never see the word “default” and never have to navigate between syndicate and asset settings. Multi-asset syndicates get a single place to set shared defaults and a simple override mechanism for anything that differs.

Who can use it

Admin — view and change both the syndicate defaults and each asset’s per-asset overrides.
Members — see the rates in effect for any booking they create. Cannot change the settings.
Treasurers (admins) — same as admin.

Where to find it

The settings live in two places once a syndicate has more than one asset:

Syndicate defaults: Admin tab → Asset rates, under the Money heading. Route: /syndicates/:syndicateId/settings/billing. The route keeps an older settings segment; there is no Settings tab in the UI.
Per-asset override: Assets → [asset] → Billing Settings. Route: /syndicates/:syndicateId/assets/:assetId/billing.

On a single-asset syndicate, only the first one exists, unless the aircraft still has settings of its own (see Behaviour rules).

Fields / options

Which fields cascade

Every field below follows the default-then-override cascade. The labels here are the multi-asset versions; on a single-asset syndicate the same fields appear without the “Default” prefix.

Default usage rate
Default shortfall rate
Default weekday minimum usage
Default weekend minimum usage
Default event fees (landing, touch-and-go, etc.)
Default captured measures (engine meter, block time, airborne time)
Default billed measure (“Bill on”)
Default engine meter label, and the start and end names of each captured measure (these travel with the captured measures: an asset has its own only as part of its own capture override)
Default taxi minutes
Default fuel rate and fuel unit
Max Advance Booking Days (set per asset on the asset’s edit screen, where an empty field shows the syndicate default it falls back to)
Home airfield (set per asset on the asset’s edit screen, once the syndicate has more than one asset)

These all live as syndicate defaults; in a multi-asset syndicate each asset can override any of them.

Currency does not cascade. It is set once on the Payment account screen, is syndicate-wide, and has no per-asset value to override — an asset’s billing settings hold no currency at all, and every charge reads the syndicate’s. Two aircraft in one syndicate cannot be priced in different currencies.

Per-scheme rates — the nuanced case

Billing scheme definitions (name, dues amount, rate modifier type and value) are always syndicate-wide. See Payment account, Member billing and Bill members.

Billing scheme rates — the numeric rate that applies when an asset is booked by a member on that scheme — cascade per asset. The per-scheme section only appears once the syndicate has more than one billing tier; with just the default tier, the asset’s base rate is the rate everyone pays and no per-scheme section is shown.

Single-asset syndicate (more than one tier): the Asset rates screen shows a Per-Scheme Rates table directly. You edit the single asset’s scheme rates there.
Multi-asset syndicate (more than one tier): the Per-Scheme Rates section is replaced with a note that tells you to configure rates on each asset individually. Each asset carries its own per-scheme rate overrides.

Which fields do not cascade

These syndicate settings apply uniformly to every asset in the syndicate. They cannot be overridden per asset:

Require booking approval
Minimum booking duration
Require admin confirmation for squawks
Show member names
Usage log visibility
Share usage photos with all members

Behaviour rules

Single-asset syndicate → no “Default” label, no asset-level billing screen. The complexity is hidden entirely.
The instant you add a second asset, the UI changes. Section headings on Asset rates gain the “Default” prefix. Each asset gets its own billing screen with the same fields, where an empty value means “fall back to the syndicate default”.
Capture settings are overridden as one unit. An asset’s captured measures, billed measure, engine meter label and start and end names are its own together or not at all.
An asset’s own settings can be given back in one go. When an asset has any setting of its own, its billing screen says so at the top and offers Use the syndicate’s settings. That asks first (Cancel backs out), then discards every setting the asset has of its own: its rates, minimums, event fees, fuel rate and unit, taxi minutes, booking-ahead limit and home airfield, and its capture settings. From then on it follows the syndicate default for all of them, including any later change. Its per-scheme rates and per-scheme event fees are kept, since there is no syndicate default for them to follow. Giving back the capture settings is a change to what the asset records, so it is checked like any other: it is refused while maintenance counts a measure the syndicate default does not record, and you may be asked what the meters read. If it is refused, nothing else is discarded either.
If you later archive or delete the second asset, the syndicate returns to single-asset mode. The “Default” prefix disappears, and the asset-level screen goes away.
- Every setting the remaining aircraft has of its own becomes the syndicate’s. Its rates, minimums, event fees, fuel rate and unit, taxi minutes, booking-ahead limit, home airfield and capture settings, whichever it has, are each moved to the matching syndicate setting, and the aircraft follows them from then on. A setting the aircraft did not have of its own leaves the syndicate’s value as it was. Pilots see no change, and the syndicate’s own screens now edit what the aircraft uses. The archive and erase confirmations warn you when this will happen, naming the aircraft. It happens however the aircraft leaves, and an aircraft added later takes these settings as its default.
- An archived aircraft that followed the old syndicate default keeps what it resolved to as its own, for each setting that moved, so restoring it later changes nothing about how it is flown or charged. There are three exceptions, where no stored value can say “none”: if the syndicate had no fuel rate (receipts reimbursed), no home airfield, or no taxi minutes, the archived aircraft takes the moved value instead.
- The same happens when a syndicate gains its only aircraft: restoring an archived aircraft while no other is active, or moving one into a syndicate that has none.
- A sole aircraft that still has settings of its own keeps its Billing Settings screen. This can happen when you set a sole aircraft’s booking-ahead limit on its edit screen, which offers that field whatever the syndicate’s size, or, rarely, when the aircraft was being edited at the very moment the other aircraft was removed, which leaves its home airfield on the aircraft. While it holds any value of its own, its Billing Settings card stays on the asset screen, saying the aircraft’s settings override the syndicate’s, so you can see them or use Use the syndicate’s settings. Once it holds none, the card goes away.
Precedence for any usage calculation (where the fields cascade): the asset’s value if set, otherwise the syndicate default, otherwise the system default. The first value set in that chain wins.
The snapshot rule still applies. When a usage log is saved, the resolved rates at that moment are snapshotted onto the log. Later changes to the default or the override do not back-date a booking’s charge. See Finalisation rules.
Currency is syndicate-level and not part of the cascade. It is set once on the Payment account screen and applies to every asset’s billing. There is no per-asset override to set.
Captured measures cannot be narrowed underneath maintenance, at either level. Turning off a measure that any maintenance item counts is refused, and the affected items are named. A syndicate-default change is checked against every asset that inherits the default; a per-asset override is checked against that asset alone. See Usage capture.