Write access (creating events)

You can allow the assistant, per calendar, to create and manage events — on every plan. The toggle sits in the same setup as the detail level, right under each calendar — and is off by default.

What the assistant may do

• Create events — “Book me a meeting with XY on Tuesday 10–11am.”
• Change or delete only its own events — the ones it created itself. It can neither change nor delete your existing events — they are not addressable for write access.

The safety boundaries

• Only shared, writable calendars. Write can only be enabled for a calendar you already share for reading. Read-only calendars (e.g. subscribed feeds) never appear as a write target.
• Confirmation happens in the client. Claude Code asks before every write. Turning on auto mode is a deliberate choice.
• Double-booking is reported, not prevented. If a new event overlaps an existing one it’s still created — but the overlap comes back as a warning. Whether a double-booking is intended is your call, not ours.
• Timezone is required. The assistant must send a timezone with every event, so it never lands at the wrong time.

Logging

Every write is in the access log — with calendar, outcome and duration, but without the event’s title. Zero retention applies here too.

Enabling write access later

If you enable write access after the assistant was already connected, it does not know about the new write tools yet — it loaded the tool list when it connected. It will keep telling you it cannot create events.

So after saving in the app, reload the tool list in your client once:

• Claude: open the three-dot menu on the connector and choose Refresh.
• Other clients: reload the connection, or disconnect and connect again. A new token is not needed.

You can switch write access off per calendar at any time, or revoke the access entirely.