> For the complete documentation index, see [llms.txt](https://help.docexport.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.docexport.com/troubleshooting/additional-app-settings/allow-text-columns-as-email-recipient.md).

# Allow text columns as email recipient

By default, **DocExport** uses **Email Columns** in your monday.com board to determine who receives generated documents.

However, if your workflow stores email addresses in a **Text Column** instead, you can enable an option to allow those columns to be used as valid recipients and display them as selectable options when choosing your recipient column.

{% hint style="warning" %}
When this option is active, **all text columns** in your board will appear in the dropdown list for recipients, not just the ones that actually contain emails.

This can quickly become **cluttered or confusing**, especially on boards with many text columns. For best results and cleaner configuration, we strongly **recommend using Email Columns** whenever possible.
{% endhint %}

## How to enable "Allow Text Columns for Email Recipients"

1. Open your monday.com board and open the DocExport App View.
2. Select **'Settings'** and go to **'App Settings'.**\
   \&#xNAN;***Note:** The first time you open App Settings, the Pricing page may appear. Simply close it and click 'App Settings' again.*
3. Scroll down to the **'Advanced settings'** section.
4. Enable the option **'Allow text columns for email recipients'**.
5. Once enabled, all text columns in your board will appear in the recipient dropdown inside DocExport.

<figure><img src="/files/XsUsIGJ5zdYdj1WZT8tZ" alt=""><figcaption></figcaption></figure>

### Multiple Email Addresses

You can also include **multiple recipients** in a single text cell by separating the addresses with semicolons (;).&#x20;

**Example:**&#x20;

```
hi@towerapps.com;support@towerapps.com
```


---

# 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://help.docexport.com/troubleshooting/additional-app-settings/allow-text-columns-as-email-recipient.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.