Grace period and read-only mode
What it is
Section titled “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 syndicate’s admins time to fix the 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
Section titled “Who can use it”- Admin: the grace notice and read-only banners are aimed at admins; any admin can resolve the payment from the web version’s subscription settings.
- Member: sees a banner explaining the syndicate is in a limited state.
Where to find it
Section titled “Where to find it”- Subscription settings:
/syndicates/:syndicateId/settings/subscriptionshows the current subscription status, including past due, cancelled, or unpaid. - Banners and inline notices appear throughout the app when the syndicate is in grace or in read-only mode.
Fields / options
Section titled “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
Section titled “Behaviour rules”The timeline runs from the first failed payment attempt:
| Day | State | What admins see | What the syndicate can do |
|---|---|---|---|
| 0 – 7 | Red grace | Urgent warning: payment has failed, please update your details soon. | Full read and write. |
| 8 – 14 | Amber grace | Gentle 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
Section titled “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
Section titled “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
Section titled “Resolving the grace or the read-only state”An admin 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
Section titled “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.
Free-tier syndicates
Section titled “Free-tier syndicates”Syndicates on the free tier have no recurring payment, so they cannot enter grace. The rules above apply only to syndicates on a paid subscription.
See also
Section titled “See also”- Pricing: the recurring amount that is failing
- Upgrade prompt: the path from free to paid
- Free-tier limits: what the syndicate drops back to if a subscription lapses within the limits