> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/user/guide/devices-and-settings/tachograph-and-compliance/ddd-emails.md). # DDD files recipient email Add up to five email recipients so downloaded DDD files are delivered automatically after each tachograph download completes. Automatically sends downloaded DDD files to the people who need them, for archiving, compliance record-keeping, or forwarding to an analysis service. It pairs with [DDD download](/docs/user/guide/devices-and-settings/tachograph-and-compliance/ddd-download.md): once a file is retrieved from the device, it's emailed to the configured recipients. ## Settings * **Recipient emails**: Add the email addresses that should receive downloaded DDD files. Click the **+** button to add each address. You can specify up to 5 recipients. ## Availability Appears on tachograph-capable devices that support DDD download. ## Limitations * Up to 5 email addresses can be configured. * DDD files are emailed after a download completes: Configure download separately on the [DDD download](/docs/user/guide/devices-and-settings/tachograph-and-compliance/ddd-download.md) page. * Navixy only delivers the files. It does not read or process their contents. ## How it works Navixy emails each DDD file **when the device delivers it**. Navixy never proactively pulls files from the device to send them. For the email to fire, a download must first be requested via [DDD download](/docs/user/guide/devices-and-settings/tachograph-and-compliance/ddd-download.md) and the device must successfully push the file back to Navixy. Typical required conditions are listed on that page (ignition ON, company card inserted, Tacho Auth Client connected). ## See also * [DDD download](/docs/user/guide/devices-and-settings/tachograph-and-compliance/ddd-download.md): request and download DDD files from the device. --- # 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://navixy.com/docs/user/guide/devices-and-settings/tachograph-and-compliance/ddd-emails.md?ask=&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.