Calendar
The Calendar tab of the System screen. Three ceilings, and they guard different things: two of them bound the body of a single event, the third bounds the size of a single read of the grid.
All three are whole numbers of 1 or more, and all three are stored together with one Save. Every field is checked before the first of them is written, so a value the form does not accept leaves none of the three saved; the refusal names the field it came from — «{{field}}»: enter a positive whole number.. Pressing save without a change answers No changes.
The body of one event
Event limits holds the two ceilings on a single event. Both exist for the same reason: an event is visible to everyone it is addressed to, and a recurring one is additionally expanded per occurrence — with every occurrence carrying a full copy of all the event's texts. So an oversized event is not a burden on its author alone; it slows the calendar for the whole installation.
- Guests per event — how many people may be invited to one event. The default is 500, the same number one invitation may reach in Microsoft 365 (Google Calendar allows 200).
- Characters per text field — how many characters each text field of an event may hold. One ceiling covers all four fields — the title, the description, the location and the link — so that the refusal can name a single number. The default is 8192, with room to spare for a detailed meeting agenda.
An event that exceeds either ceiling is not saved — neither when it is created nor when it is edited.
Both ceilings let an already saved event through as long as the offending part does not grow: a guest list that is over the limit may be shortened, a text that is over the limit may be trimmed. Without that leniency, lowering a ceiling would lock the organiser out of their own event — the edit would be refused wholesale, and there is no way to shorten the list except by editing.
The size of one read
Limit of one read holds the third ceiling, and it is about reading rather than saving.
The grid is read in periods of at most 92 days, but any number of events can fall inside one period, and the answer is assembled in memory whole. Events per read caps how many events one such read may return. The default is 5000 — the same allowance a single chart on a dashboard gets, and out of reach on an ordinary calendar.
Above the ceiling the answer is cut short rather than refused: a refusal would leave the person without a calendar at all, while a truncated answer still leaves a working grid. Nothing is hidden silently — the reply carries a warning that not all events are shown.
This ceiling does not touch saved events. It changes nothing about what is stored, only how much one read may carry.