> For the complete documentation index, see [llms.txt](https://docs.reportandrun.com/manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reportandrun.com/manual/faq/c160/c164/q539.md).

# Why won’t it let me send, export, or share my reports via email?

Some email clients have a file size limit and won't share files if they are too large. See [this article for alternative sharing options](/manual/faq/c160/c164/q540.md) if your email client won't send a large report.

## Related

* [Article: How to share reports from the Report and Run: Cloud web portal](/manual/readme/report-generation/share-a-document-via-link.md)
* [Article: How to share reports from the Report and Run: Integrate mobile app](/manual/report-and-run-integrate/report-generation/share-a-report.md)
* [Article: How to share reports from the Report and Run: Offline mobile app](/manual/report-and-run/report-generation/share-a-published-report.md)
* [FAQ: How do I share reports that are too large to send via email?](/manual/faq/c160/c164/q540.md) 
* [FAQ: What should I do if the app fails to convert files or export reports to PDF and shows errors?](/manual/faq/c160/c164/q538.md)
* [FAQ: How do I contact support?](/manual/faq/c169/q575.md) 


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.reportandrun.com/manual/faq/c160/c164/q539.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.