> ## 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.

# Resend

> Inspect and manage shared email infrastructure from Roomote tasks.

Connect Resend when tasks need email delivery status, received messages,
domains, contacts, templates, broadcasts, or other email infrastructure.

## How setup works

An admin connects Resend once from **Settings > Integrations** using OAuth. The
connection is shared across the deployment and requests Resend's
`full_access` scope so Roomote can use inspection and management tools.

## Safer defaults

Roomote initially disables tools that send or reschedule email, create or
remove API credentials, mutate domains or webhooks, mutate or trigger
automations, and mutate contacts. Read operations remain available, and
canceling a pending scheduled email remains enabled as a safety action.

The disabled tools include:

* single, batch, and broadcast sending
* rescheduling a scheduled email
* creating or removing API keys that could bypass Roomote's tool policy
* creating or updating automations, or sending events that trigger them
* updating or removing domains
* creating or updating webhooks
* creating, updating, or removing contacts
* creating, updating, or removing contact properties
* changing contact segment or topic membership
* importing contacts from CSV

An admin can opt in to individual tools from **Settings > Integrations >
Resend > Manage tools**. Disabled tools are hidden from tasks and rejected by
the server if called directly. Admin choices persist when Resend is reconnected
or disabled and enabled again.

## Verify the connection

After connecting Resend, start with a read-only request such as listing recent
emails or checking domain status. Enable only the additional tools your team
expects Roomote to use.