The amber scheduling conflict banner is advice. It tells you two things are booked into the same space at the same time; it does not stop them, it did not stop them being saved, and nobody is notified. Treat it as a checklist you read, not a guard rail you rely on.
Find it under Workspace → Calendar. You need the Events permission to open it, and Events · Create to import.
What appears on it
Two record types, and only two:
- Events, including the ones a program generated — those carry a small repeat icon.
- Your organization's bookings.
Archived events are excluded. Cancelled ones are kept and coloured, because a cancelled night is still part of the picture.
What is not on it: programs themselves (a program is a rule — its generated events appear, the program does not), opportunities, tasks, meetings logged against a contact, and anything belonging to another organization.
An opportunity isn't on the calendar, but its event is: posting from Create Opportunity adds that event the same day.
The calendar loads one month at a time — the month you are looking at plus the days that complete the grid. Filters and the conflict check only ever see that window.
Views
Week, Month and Agenda work. Quarter, Year, Timeline and Resource are shown as coming soon on wide screens; they are not clickable.
Filters
Location and Status sit in the workspace filter bar at the top of the page — the same controls you use elsewhere. Space and Program sit on the calendar itself, because they are specific to it.
The Status list is built from what is actually loaded rather than a fixed list, because the calendar mixes events and bookings and those have different status vocabularies.
There is deliberately no date filter. The calendar owns its own date window — use Today, the arrows, and the period label.
What counts as a conflict
Exactly this: two entries, in the same space, on the same day, whose times overlap.
- An entry with no space assigned can never conflict — it is skipped.
- Cancelled entries are skipped.
- An entry with no start time is treated as taking the whole day.
- An entry with a start but no end is treated as a single instant.
The banner counts the conflicting groups and lets you review each one and jump into the records. Beyond that it does nothing: no block, no constraint in the data, no notification, and nothing stored. If you archive one of the two entries, the banner simply stops showing that group.
Importing an .ics file
Import takes a single .ics file. Read this before you use it.
- Times are imported at their literal wall-clock value. There is no timezone conversion. A 7:00pm entry imports as 7:00pm regardless of the timezone the source calendar recorded it in. Timezone markers in the file are ignored, not applied.
- Recurrence rules are ignored. A repeating series imports as a single event on its first date. If you need the series, generate it with a program.
- Re-importing the same file updates rather than duplicates. Entries are matched on the unique ID the file gives them, within your organization. An entry with no unique ID cannot be matched and will be added again on every import. An import only ever updates an event that was itself imported — a hand-made event that happens to share an ID is never overwritten.
- Limits. Around 1 MB per file and 1,000 events. Over either and the whole import is refused rather than partly applied. An event title over 500 characters, a location over 500, a description over 5,000 or an ID over 512 also refuses the whole file — nothing is silently truncated.
- Skips. An entry with no start date, or one ARRIVE cannot read, is skipped and counted in the result message.
- End times are only kept when the entry ends on the same day it starts.
- The location line in the file cannot be matched to your ARRIVE locations, so it is folded into the event's description as “Location: …”.
- Imported events arrive as plain Draft events with no location, space, program or manager. Fill those in afterwards.
Exporting an .ics file
Export downloads your organization's calendar as one .ics. Two things to expect: it covers roughly two years back and three years forward from today, not the month on screen, and it ignores the filters you have applied. Timed entries are written at their local wall-clock time with no timezone attached; entries with no start time export as all-day.
For a calendar that keeps itself up to date rather than a one-off file, use a subscription feed instead.
Printing
Print prints the view you are looking at. The toolbar, buttons and banners are hidden from the printout.
What this does not do yet
You cannot drag an entry to reschedule it, or click a day to create something. Quarter, Year, Timeline and Resource views are unbuilt. Conflicts are not stored and nobody is notified about them. And an imported file is a snapshot — a later change in the source calendar only reaches ARRIVE when you import again.