> For the complete documentation index, see [llms.txt](https://docs.kinwall.family/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kinwall.family/settings-reference/calendars.md).

# Calendars

*Admin only.* This tab is hidden on displays.

## Calendars

Each calendar row shows its colour, name, kind and status: "Synced *time*", "Never synced", "Local calendar", or the last error. Row actions:

* **Sync now**: synced calendars only.
* **Reconnect**: for an imported ICS calendar that has no URL. See [Reconnecting after import](/connecting-calendars/reconnecting-after-import.md).
* **Remove**: "Remove this calendar and its events from Kinwall?" Nothing is deleted from the original calendar.
* Tap the row to open **Edit calendar**:
  * **Name** and **Color**.
  * **Members**: whose calendar it is. Its events are tagged with these members unless tagged otherwise.
  * **Default category**: "Applied to events here with no keyword match or their own category."
  * **Enabled**: when off, the calendar stops syncing and its events are hidden.

Add buttons:

| Button               | Does                                                                                                                                        |
| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
| **+ Local calendar** | A Kinwall-only calendar (**Add local calendar**: a name; it gets the next unused colour, and you can change the rest in **Edit calendar**). |
| **+ ICS URL**        | [ICS feed](/connecting-calendars/ics-feeds.md).                                                                                             |
| **+ CalDAV**         | [iCloud & CalDAV](/connecting-calendars/icloud-caldav.md).                                                                                  |
| **Connect Google**   | [Google](/connecting-calendars/google.md). Greyed out until a Google client is configured.                                                  |
| **Connect Outlook**  | [Microsoft / Outlook](/connecting-calendars/microsoft.md). Greyed out until configured.                                                     |

After connecting an account, **Calendars for *****account*** lists its calendars. Pick members, then **Add calendar** on each one you want.

## Calendar providers

* **Public URL**: the base URL used for OAuth redirect URIs and the passkey domain, for example `https://cal.home.example`. The server warns about a bare IP address or plain `http` on a non-localhost host. If `PUBLIC_URL` is set in the environment, this shows "Set via PUBLIC\_URL" and is locked.
* **Google** and **Microsoft** cards: **Client ID**, **Client secret** (leave blank to keep the saved one), **Tenant** (Microsoft), **Redirect URI** with copy, setup steps, **Save**, **Remove** and **Test sign-in**. Credentials that come from environment variables show "Provided by your host" and are read-only.

Client secrets are encrypted at rest and never returned. See [Configuration](/self-hosting-reference/configuration.md) for precedence rules.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.kinwall.family/settings-reference/calendars.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.