Appearance
External calendars
External calendars let AuroraDocs show outside events beside your native tasks and daily notes without turning them into editable Aurora tasks. Imported events are read-only overlays in Calendar, so your source calendar remains the system of record.
Where calendar connections live
Open Settings -> Preferences -> Calendar connections.
From there you can add or manage supported calendar sources, refresh mirrored events, and control which calendars appear in Aurora's Calendar page.
Supported sources
| Source | How it connects | Notes |
|---|---|---|
iCal / .ics feed | Paste a feed URL | Good for public or tokenized read-only calendars. AuroraCloud fetches the feed so browser CORS does not block it. |
| CalDAV | Server URL, username, password or app password | Aurora discovers calendars on the account and mirrors selected calendars into the workspace. |
| Google Calendar | OAuth sign-in when the AuroraCloud server is configured | Aurora stores the connected email and mirrors discovered calendars. |
| Microsoft 365 | OAuth sign-in when the AuroraCloud server is configured | Uses the same mirrored-account flow as Google Calendar. |
| Calendar bridge imports | Connector-backed calendar.upsert events | Used by integrations that push stable external calendar records into AuroraCloud. |
What appears in Calendar
Open Calendar from the sidebar. External events appear separately from Aurora tasks:
- they keep provider/source styling
- they can be hidden per provider or source
- clicking an event opens a read-only detail view
- Open in source takes you back to the original calendar when the provider supplied a link
External events do not open the normal task editor from Calendar. If you need an editable Aurora task, create a native task and link it to the relevant page or event context.
Refreshing and reconnecting
Use Refresh on a connection to pull the latest calendars and events. For CalDAV, refresh also rediscovers calendars on the account, so new remote calendars can appear without removing and reconnecting the account.
Folder-backed metadata can restore connection labels, URLs, workspace/source toggles, and visibility preferences, but not secrets. After restoring or moving a workspace, password and OAuth-backed calendar accounts may show a needs reconnect state until you reconnect credentials on that device.
Privacy and limits
- Calendar credentials are not written into the Local Files folder format.
- OAuth providers appear only when the AuroraCloud server has the required provider credentials configured.
- Calendar overlays are currently read-only from the Calendar page.
- Recurring Aurora tasks are separate from external recurring events; Aurora renders each through its own task or overlay path.