> For the complete documentation index, see [llms.txt](https://knowledge.rollcredits.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.rollcredits.io/getting-started/tars/exports.md).

# Download exports from TARS

Ask TARS for a report, a zip of documents, paystubs or a stored file, then download it from the card under TARS's reply.

Ask TARS for a file and it runs the export, then puts the file on a card under its reply. The **TARS** button in the header opens the chat ([Ask TARS](/getting-started/tars.md)).

{% hint style="info" %}
Anyone who can open TARS can ask for files. TARS runs each export with your permissions, so it makes only files your role can export in the app. For one you can't run, TARS tells you which roles can, and who on the production has them.
{% endhint %}

## Ask for a file

1. Ask for the file, such as a report as PDF or Excel, a zip of documents, paystubs, or one stored document like a receipt or a W-9.
2. Answer any questions TARS asks. It may need dates, filters such as only approved transactions or certain vendors, PDF or Excel, or which payroll run or timecard.
3. Wait while TARS shows **Preparing your file**. The card appears under its reply.

Each file gets its own card. TARS never writes a link to the file, so the card is the only way to get it. An export changes nothing on the production.

## Download the file

1. On the card, select **Download**. On a phone, the file opens in a new browser tab.

The card's title says what the file holds. Under the button, **The link works for about 10 minutes. After that, ask TARS to run the export again.** For a background file, the 10 minutes start when **Download** appears.

A card that also says **This file contains sensitive information.** holds details such as SSNs, W-9s or onboarding documents.

## Wait for a file that builds in the background

Some exports, such as a zip of transactions with their documents, take longer. Their card shows **Building your file. It usually takes a few minutes. Keep this page open and the download button shows up here.**

Stay on the TARS page until **Download** appears. If you leave, the file doesn't reach the card, and about 15 minutes after the export started the card shows **The file didn't arrive on this page. If you left the page while it was building, ask TARS to run the export again.**

## If the card shows a message

* **This link has expired. Ask TARS to run the export again.** The 10 minutes are up. Cards in chats you reopen from **History** show this too, except a background file's card, which says the file didn't arrive.
* **The export failed. Ask TARS to try again.** The file couldn't be built.

{% hint style="info" %}
The **Export** button next to the message box saves the conversation's text as a file, not the files from cards. See [Ask TARS](/getting-started/tars.md).
{% endhint %}


---

# 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://knowledge.rollcredits.io/getting-started/tars/exports.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.