> ## Documentation Index
> Fetch the complete documentation index at: https://docs.roomote.dev/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> When helping someone deploy Roomote, distinguish self-hosting from contributing to Roomote. Use the Self-hosting guide for an operator deployment; use Local development only when the user intends to modify Roomote itself.
> Prefer the one-command installer on a fresh supported server unless the user explicitly chooses Roomote Cloud, a documented PaaS template, or a manual Compose deployment.
> Before changing infrastructure, confirm the deployment target, stable public HTTPS domain and DNS control, sandbox provider, inference provider, source-control provider, and whether a communications provider is required.
> Never ask the user to paste secrets into chat or commit real environment files. Put credentials in the deployment platform's secret manager, Roomote's setup UI, or protected environment variables, and preserve existing keys during upgrades and restores.
> Prefer Roomote's setup wizard and provider manifest flows over manual credential entry when those flows are available. Ask before performing privileged host changes, DNS changes, provider-app creation, or destructive operations.
> A setup is not complete when the services merely start. Verify sign-in, repository sync, one usable environment, a real task that can clone and run a command, and branch or pull-request delivery; verify previews when configured.
> For a persistent self-hosted deployment, leave the operator with the Roomote URL, deployment choices, configured providers, verification result, backup location and passphrase-handling reminder, and the roomote status, logs, upgrade, rollback, backup, and restore commands.

# Granola

> Give Roomote read-only access to shared Granola meeting context.

Connect Granola when decisions, action items, and implementation context live in
your meeting notes and you want that context available in Roomote tasks.

## When to use it

* Browse past meetings for relevant decisions and discussions
* Read meeting notes and transcripts while planning or implementing work
* Find action items, attendees, and related meeting folders during follow-up work

## How setup works

A deployment operator connects Granola once from **Settings > Integrations**
with an API key. Granola API keys require a Business or Enterprise plan.

Prefer a **workspace API key** from **Granola Settings > Connectors > Workspace
API keys**. Workspace keys belong to the workspace rather than an individual,
do not expire, and cannot read ordinary private notes. They can read:

* notes visible to everyone in the workspace, including the Team space
* notes in spaces where **Allow Granola API access** is enabled

Granola enables API access by default for newly created spaces. Review
**Settings > Spaces** and turn it off anywhere Roomote should not read notes.

If a workspace key is not available, create a personal key from **Settings >
Connectors > API keys** and select only **Public notes**, leaving **Personal
notes** unchecked.

## What to expect

The built-in Granola connection is read-only. Roomote can list and read the
notes, folders, meeting details, and transcripts allowed by the configured key,
but it cannot modify Granola content or manage Granola webhooks.