Which calendars work (Google, Microsoft 365, Apple)
Daisy reads your calendar through a read-only ICS (iCal) link — see Recording from your calendar for the setup. Whether that link works, and how much detail it carries, depends on two things you don't fully control:
- Which calendar provider you use (Google, Microsoft 365, Apple).
- What your organization's IT admin allows. Many companies lock down calendar sharing with policies, so a feature that works on a personal account may be switched off on a work account.
Here's what to expect from each.
Google Calendar — works best
Google Calendar is the most reliable. Its secret iCal address (Settings → Settings for my calendars → Integrate calendar → Secret address in iCal format) includes event titles, times, and the attendee list, so recordings start pre-filled with participants ready to label.
If you have a choice, point Daisy at a Google Calendar.
Microsoft 365 / Outlook — works, but no attendee names
Microsoft 365 publishes an ICS link too (Outlook on the web → Settings → Calendar → Shared calendars → Publish a calendar), and Daisy will happily import your event titles and times from it.
The one thing it can't do is bring in the attendees. Microsoft does not include attendee names in the published ICS feed. The only way to read them is through a special Microsoft Graph permission that an IT admin has to grant to an approved app — and Daisy deliberately does not ask for that level of access to your company's directory. We'd rather not be a tool your IT team has to vet for tenant-wide calendar permissions.
So on Microsoft 365, expect:
- ✅ Upcoming meetings show up, pre-filled with the title and time.
- ✅ One click still starts a recording from the event.
- ❌ The participant list is empty — you add people yourself.
Adding them by hand is quick: once the meeting is recorded, Daisy groups the speakers for you, and you can name each one or pull them from your saved voiceprints. See Identifying who said what.
Apple Calendar / iCloud
A public calendar.icloud.com share link imports titles and times. Attendee detail varies by how the event was created and shared, so treat it like Microsoft 365 — reliable for when a meeting is, less so for who's in it.
When import doesn't work at all
Sometimes the ICS link itself is the problem, and it's almost always a policy set by your admin rather than anything in Daisy:
- ICS publishing is disabled. Some organizations turn off calendar publishing entirely. If your provider won't give you a secret/published iCal URL, there's nothing for Daisy to subscribe to.
- The link is access-restricted. A few setups gate the ICS feed behind a sign-in, which a read-only subscription can't pass.
- Stale or empty feed. Published feeds can lag or only cover a limited window. Use ↻ Sync to force a refresh.
If your work calendar is locked down, the simplest path is to subscribe a personal Google Calendar (even just for the meetings you record), or skip calendar import and start recordings manually — every Daisy feature works the same either way. The calendar is a convenience for pre-filling details, not a requirement.
Good to know
- Whatever the provider, the calendar link is read-only and the fetch goes straight from your machine to your provider — Daisy never routes it through us.
- Changing providers or fixing a locked-down feed is an IT/account setting on their side; there's no Daisy setting that can grant access your admin hasn't.