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

# Create cards by email

> Give a board or My Board its own email address and turn incoming emails into cards. Handy as a forwarding target for customer inquiries.

Each board, and My Board, can have its own inbound address (`<id>@app.zarms.cloud`). Email it and the subject becomes the card name while the body becomes the card's document. It is meant for forwarding customer inquiries and running them as cards.

## Turn it on

1. Open the board settings and choose the **Email** tab. For My Board, open **Cards by email (My Board)** from the right-hand navigation.
2. Switch on **Enable card creation by email**.
3. Copy the address and use it as a forwarding target or recipient.

The address is off at first. Cards and documents are created with the permissions and Google connection of the person who turns it on. If that connection lapses, no document is created and the body stays in the card description.

## What becomes of the email

| Email part | Card |
| - | - |
| Subject | Card name ("(No subject)" if empty) |
| Body | The card's document. HTML keeps its formatting; plain text is Markdown |
| Attachments | The card's Drive folder |
| Sender | Received by |

Assignees, due dates and status follow the **card create defaults** of the board and team.

## Accepted senders

Chosen per address.

* **Team members only**: only emails from member addresses are accepted.
* **Members and allowed senders**: also accepts senders on the allow list (`taro@example.com` or `@example.com`).
* **Anyone**: anyone who knows the address can create cards, and spam becomes cards too. Keep the address private.

When an email from someone who is not a member is accepted, they are registered as a member with their display name and email address, and a Gravatar icon if one exists.

Emails whose sender cannot be verified (DMARC or DKIM) are not accepted under "Team members only" or "Members and allowed senders". Under "Anyone" they are accepted, but the sender is not treated as a member.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.