Write access (creating events)

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

Below it sits a second toggle: “May change and delete existing events”. It is deliberately separate, because it is the larger power: creating an event adds something, rewriting an existing one changes what is already there.

What the assistant may do

With the first toggle:

• Create events — “Book me a meeting with XY on Tuesday 10–11am.”
• Change or delete its own events — the ones it created itself.

With the second toggle, additionally:

• Change and delete existing events — “Move the dentist to 2pm.”
• Answer invitations — accept, decline, tentatively accept. The organiser is notified; merely deleting an invitation would leave them expecting you.

Where the second toggle does not apply

It can only be switched on where it can actually work:

• Only at “All details”. If the assistant sees only “Busy” or title and time, it could not even tell you which appointment it is changing. Acting blind is worse than refusing.
• Only for Google and Microsoft. Other providers do not report who organised an event — without that, there is no way to tell your own appointment from someone else’s invitation.
• Only for events you organise yourself. The assistant cannot rewrite someone else’s invitation. It can decline it for you, and that reaches the organiser.
• Not for synchronised copies. Change a copy and the next sync overwrites it. The assistant refuses and names the source calendar, where the change sticks.

The safety boundaries

• Recurring invitations ask back. For a series the assistant asks whether you mean this one date or the whole run — unless you named a date. A decline sent to the organiser cannot be taken back.
• 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.