These connections belong to the organization, not to you. There is one feed and one Google connection and one Outlook connection per scope, shared by everyone. If a colleague connects Google, you see “Connected”. If someone disconnects it, it stops for everyone. This is not a personal calendar setting.
Find it under Workspace → Calendar → Sync. Seeing the page needs the Events permission. Generating a feed, or connecting and disconnecting Google or Outlook, needs Settings · Edit — without it you can read the state but every control is replaced with “ask an organization admin”.
The scopes
You get one card for All locations (organization) — every event and booking across the organization — and then one card per active location. Each card carries its own ICS feed, its own Google connection and its own Outlook connection, so a venue manager can subscribe to just their site.
There is no per-space feed.
The ICS subscription feed
Generate ICS feed creates a private subscribe URL you can paste into any calendar app that accepts one. It is read-only in both directions of meaning: it shows your schedule, and the subscribing app can never write back into ARRIVE.
Apple Calendar:
- Open Apple Calendar.
- Choose File → New Calendar Subscription…
- Paste the ICS URL and click Subscribe.
The security point, stated plainly
The feed link is unauthenticated. Anyone holding the URL can read your organization's schedule without signing in to ARRIVE, without being a member, and without leaving a trace. The unguessable link is the password. Share it the way you would share a password.
Regenerating is how you revoke it. The panel says so in as many words:
Regenerating creates a new URL and immediately invalidates the old one — anyone subscribed to it will stop receiving updates until you share the new URL.
If a link has been forwarded somewhere it should not have been, regenerate. Everyone on the old link, including your own team, will need the new one.
What the feed contains
Your events (excluding archived ones) and your organization's bookings, from about 90 days ago forwards, up to a capped number of each. Every entry carries its title, its date and time or an all-day marker, the space or location name, and a status. A booking's title is the performer's name and the service.
It carries no money, no notes, no client details and no contact details.
Google Calendar and Outlook
Connecting either one starts a consent flow with that provider and then pushes one way, out of ARRIVE. Nothing your team adds or edits in Google or Outlook is ever read back — ARRIVE is the source, and the external calendar is a copy.
- What is sent: your events (cancelled ones excluded) and your bookings (cancelled and refunded excluded), from a week ago forwards, capped per run. Each carries a title, dates and times, and for events the space or location as its location line.
- How often: a job pushes every connected calendar roughly every quarter of an hour. The card shows Last synced once it has run.
- Updates, not copies: each pushed entry keeps its identity, so a later run edits the existing entry rather than adding a duplicate.
Events arrive as all-day entries
This is the limitation to know about, and it is documented in the code that does the pushing: an event has no stored timezone, so events are pushed to Google and Outlook as all-day entries — even when you have set a start and end time on the event in ARRIVE.
Bookings are different. A booking stores its own timezone, so it is pushed at the correct time. A booking missing a start time or a timezone falls back to all-day too — only older ones can: every booking made since September 30, 2026 has both.
If exact times matter to you, the ICS subscription feed above preserves the times you set.
“Reconnect needed”
That badge means the connection to the provider has failed — usually because access was revoked on the provider's side, or the stored permission expired. Pushing stops until someone with Settings · Edit presses Reconnect. ARRIVE deliberately stops retrying rather than hammering a dead connection.
Disconnect revokes ARRIVE's access and stops all further pushing. It does not remove entries that have already been pushed — those stay in the external calendar until someone deletes them there.
What this does not do yet
There is no two-way sync: nothing is ever read from Google, Outlook or a subscribed file back into ARRIVE. There is no per-space feed, and no way to choose which calendar inside a connected account receives the push. Nobody is emailed or notified if a push starts failing — the “Reconnect needed” badge on this page is the only signal.