Events on the calendar
What it is
Section titled “What it is”An event is a syndicate-level calendar entry that is not a booking — an AGM, a fly-in, a safety evening, a maintenance day, a social. Events belong to the syndicate, not to a specific asset. They render on the calendar alongside bookings but do not interact with booking conflict detection.
Who can use it
Section titled “Who can use it”- Viewing. Every member of the syndicate sees the events on the calendar.
- Creating, editing, deleting. Admins and owners only.
- Personal ICS feed. Events are included by default in every member’s subscribed feed.
Where to find it
Section titled “Where to find it”- Syndicate → Calendar — events appear on month, week, and day views alongside bookings.
- Personal ICS feed — events for every syndicate you belong to are included in the feed served by the Subscribe to calendar button on the Bookings tab. See ICS calendar feed.
Fields / options
Section titled “Fields / options”An event carries:
| Field | Required | Notes |
|---|---|---|
| Title | yes | Short, up to 100 characters. |
| Start time | yes | UTC-stored; shown in your timezone. |
| End time | yes | Must be the same time as or after the start time. |
| Description | no | Long-form, up to 2,000 characters. |
| Location | no | Free text, up to 200 characters. Not a map reference. |
Events do not have an asset, a status enum, or an approval workflow. They are created and they exist until an admin edits or deletes them.
Behaviour rules
Section titled “Behaviour rules”- Not subject to conflict detection. An event occupying 09:00–12:00 on the 20th does not prevent any member from booking an asset during the same window. Members and the asset are two orthogonal things.
- No asset. Events are owned by the syndicate. Deleting or archiving an asset does not delete events.
- Admin-only creation. The create-event button is only rendered for admins and owners. The server also enforces this — a non-admin cannot create an event even with a crafted request.
- Events are included in the ICS feed by default. The underlying setting (
include_events) defaults to on at the backend. There is no user-facing toggle in the Syndik8 app to turn events off in your feed. If you want a bookings-only feed, subscribe to it from a calendar client that lets you filter by calendar category — Syndik8 does not offer the toggle today. - Low-volume by design. V1 events are meant for occasional high-signal items. RSVPs, attachments, and voting are expected in a later version.