Grace period and read-only mode

What it is

When a paid subscription’s recurring payment fails, the syndicate enters a grace period rather than being cut off immediately. The grace period gives the owner time to fix their card or resolve the failure before any write access is lost. If the grace period expires without the payment succeeding, the syndicate moves into read-only mode: members can still see their data, but no new writes go through.

Read access is never revoked, at any stage. You will always be able to look at your bookings, assets, maintenance, squawks, and financial history.

Who can use it

Owner — the grace notice and read-only banners are aimed at the owner, who resolves the payment.
Admin — sees the same indicators; cannot fix the payment on the owner’s behalf but can see the syndicate’s status.
Member — sees a banner explaining the syndicate is in a limited state.

Where to find it

Subscription settings: /syndicates/:syndicateId/settings/subscription shows the current subscription status, including past_due, canceled, or unpaid.
Banners and inline notices appear throughout the app when the syndicate is in grace or in read-only mode.

Fields / options

There are no fields to set. Grace and read-only are states driven by subscription status and the expiry of the grace window.

Behaviour rules

The timeline runs from the first failed payment attempt:

Day	State	What the owner sees	What the syndicate can do
0 – 7	Amber grace	Gentle warning: payment has failed, please update your details.	Full read and write.
8 – 14	Red grace	Urgent warning: payment still failing, read-only coming up.	Full read and write.
15+	Read-only	Clear notice that the syndicate is read-only until payment is resolved.	Read only. No new bookings, no new usage logs, no new expenses, no finalisation. Reading everything already there still works.

What “read-only” blocks

Creating or editing bookings, including tentative bookings.
Creating or editing usage logs.
Submitting or approving expenses.
Finalising bookings.
Recording payments.
Adding or removing members, assets, maintenance items, or squawks.

What read-only still allows

Reading every screen: calendar, bookings, balances, transactions, maintenance, squawks.
Exporting and viewing ICS feeds for bookings already in the system.
Logging in and out.
Resolving the payment from the web subscription settings screen.

Resolving the grace or the read-only state

The owner resolves the failure from the web version’s subscription settings. A successful retry closes the grace window and restores full read-write immediately. The grace period is forgiven on success — the clock does not carry over to the next failure.

Lapsed or cancelled subscriptions

A subscription set to cancel at the end of the current period shows a warning on the subscription settings screen with the end date. When the period ends, the syndicate drops back to the free tier if it is within the free-tier limits. If it is over the free-tier limits when the subscription lapses, the syndicate enters read-only until either the subscription is restarted or the syndicate is brought within the free-tier limits.

When no provider is live

The failure described here assumes a working payment integration. Currently, the checkout path is dormant — see upgrade prompt. Existing syndicates that are not on a paid plan cannot enter grace because they have no recurring payment to fail. The rules above apply once payment is live and subscriptions are in flight.