> 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.md). # Ask TARS Ask TARS, the in-app assistant, about your production, attach files or use your voice, and reopen past chats. TARS is the assistant built into RollCredits. Ask it about your production's transactions, budget, payroll and team, or where to find something in the app. Select **TARS** in the header, next to the RollCredits logo, to open the TARS page. Everyone on the production can use it, whatever their role. ## In this section * [Approve changes TARS suggests](/getting-started/tars/approve-changes.md): review the coding, descriptions, notes and new transactions TARS prepares, and approve or reject them. * [Download exports from TARS](/getting-started/tars/exports.md): get reports and documents from TARS as files you download. ## What TARS can see * **The production you have open.** Each chat belongs to one production. If you [switch projects](/getting-started/switch-projects.md), the chat clears and **History** shows the new production's chats. To ask about another production you're on, name it in your question. * **Only what you can see.** TARS reads RollCredits with your permissions, so it can't show you anything your role can't. When you ask for something you don't have permission for, TARS tells you who on the production can do it. * **Which features are on.** TARS knows which features your production has, so when you ask about one that's turned off, it tells you instead of sending you to it. * **Masked numbers.** Tax IDs, bank account numbers and ID document numbers reach TARS masked, so it can give you the last four digits at most. Birth dates are hidden from it entirely. * **No changes on its own.** When TARS suggests a change, you approve or reject it on a card. See [Approve changes TARS suggests](/getting-started/tars/approve-changes.md). Links to pages in RollCredits are clickable in TARS's replies. A link to any other site shows as plain text with its full address, and an image shows as text ending in **(image not shown)**. A list of more than six items in a reply shows its first five. To see the rest, select the button under the list, such as **Show 7 more** for a list of 12. Select **Show fewer** to fold it again. ## Ask a question 1. Select **TARS** in the header. 2. On the **Hi, I'm TARS** card, select a question under **Try asking:**, or type your own in the **Ask TARS anything...** box. Selecting a suggested question sends it right away. The suggestions are: * "What urgent actions do I need to take?" * "Which transactions still need coding?" * "Code my uncoded transactions" * "Which transactions are missing a receipt or invoice?" * "Which bills are past due?" 3. Press Enter, or select the send button (paper plane). While TARS works, **TARS is thinking...** shows, with what it's doing underneath, such as **Finding where that data lives**. Keys in the message box: * Enter sends. Shift+Enter adds a new line. * On a phone or tablet, the return key adds a new line, so select the send button to send. Cmd+Enter or Ctrl+Enter sends from any keyboard. * When the box is empty, or the cursor is at the very start, press the Up arrow to bring back the last message you typed and sent. Press it again for earlier ones, and press the Down arrow to step forward. RollCredits keeps the last 20 messages you typed on that browser. ## Interrupt or stop a reply While TARS replies, the box shows **Type to interrupt...**, and while the box is empty, a red stop button takes the place of the send button. * To stop the reply, select the red stop button, or press Esc on a computer. * To change course, type a new message and send it. TARS stops the reply it's writing and answers your new message. If you leave the page, select **New chat** or open another chat while TARS is replying, TARS keeps going and saves the reply. If you left the page, come back to **TARS** in the same browser tab, without switching projects, to read it. Otherwise, open the chat from **History**. Until the reply is saved, the chat shows **TARS is thinking...**. A reply that ended before TARS wrote anything shows **This reply was interrupted. Send your message again to try again.** ## Ask out loud 1. Select the microphone button in the message box. If your browser asks, allow it to use your microphone. 2. Speak. The box shows your recording and how long it is. 3. Select the stop button in the box to finish. To throw the recording away instead, select the trash button. 4. Wait while your recording turns into text. An empty box shows **Transcribing...** meanwhile. Your words then appear in the box. Change them if you need to, then send. The transcribed text replaces anything you'd already typed in the box. The microphone button is hidden while TARS is replying. ## Attach files 1. Select the paperclip next to the message box and choose your files. On a computer, you can also drag files onto the chat. 2. Wait for the files to upload. Each one shows as a tile above the message box, with a spinner while it uploads. 3. Type a message if you want, then send. You can send files without a message. Files you can attach: * PDF, PNG, JPG or HEIC. HEIC photos are converted to JPG when they upload. * Up to 5 files per message, each 25 MB or smaller. Files that don't fit these rules are left out, and a note above the box says why: **Files must be PDF, PNG, JPG or HEIC**, **Files must be 25 MB or smaller** or **Attach up to 5 files per message**. To remove a file before you send, select the **X** on its tile. A tile that says **Upload failed** stops the message from sending, so remove it and attach the file again. In a message you've sent, select a file to open it in a new tab. TARS can read the files you attach in the chat. To file an attached receipt or invoice as a new transaction, or, if your company has the newer change card, attach it to a transaction that already exists, see [Approve changes TARS suggests](/getting-started/tars/approve-changes.md). ## Reopen a past chat On a computer, **History** is the list on the left of the chat. It shows your own chats on this production, each with its first message and how long ago it was last updated, the most recently updated first. 1. Select a chat in **History** to reopen it. 2. To start over, select **New chat** at the top of the list. TARS also reopens the chat you had open when you reload the page, press Back to return to it, or come back to **TARS** in the same browser tab. Opening TARS in a new tab starts a new chat. To hide the list, select the collapse button at the top of it, or press Cmd+B on a Mac or Ctrl+B on other computers. **History** and **New chat** then appear above the chat. Select **History**, or press the shortcut again, to bring the list back. RollCredits remembers your choice on that browser. On a phone: 1. Select **History** above the chat. The list opens over the chat. 2. Select a chat to open it, or select **New chat**. To close the list without choosing, select the **X**. If you have no chats yet, the list shows **No conversations yet. Your chats will appear here.** If the list doesn't load, select **Retry**. ## Save a chat as a text file 1. Open the chat. 2. Select **Export** next to the message box. On a phone, it's the download icon. Your browser downloads a text file with the text of each message, labeled "You" or "TARS". Files you attached aren't in it. **Export** appears once the chat has a message. ## Rate a reply Thumbs up and thumbs down buttons appear under each reply TARS finishes. 1. Select thumbs up or thumbs down under the reply. 2. For a thumbs down, **What went wrong? (optional)** opens. Select any reasons that fit: **Wrong answer**, **Didn't do what I asked**, **Too slow**, **Sent me to support** or **Other**. To add details, type in **Tell us more (optional)**. 3. Select **Send**, or select **Skip** to send the thumbs down without reasons or details. Your rating is saved when you select a thumb. After **Send** or **Skip**, **Thanks for the feedback.** appears next to the thumbs, and your thumbs down, with any reasons and details, goes to the RollCredits team. To change your rating, select the other thumb. ## Get help from a person When your question is one RollCredits support handles, such as a sign-in problem, an error or a payment that didn't arrive, or when you ask for a person, TARS ends its reply with **Chat with RollCredits support**, and writes up your question under **Your question**. 1. Select **Chat with support**. RollCredits copies your question and opens the support chat. 2. Paste your question into the support chat and send it. If the support chat can't open, the help center opens in a new tab instead. ## If a reply fails When a reply fails, a card says why. **Try again** asks TARS to answer your last message again, and **New chat** starts a new chat. | Message | Button | | ----------------------------------------------------------------------------------- | ----------------------------------------- | | **TARS is busy right now. Try again in a minute.** | **Try again** | | **TARS couldn't be reached. Check your connection and try again.** | **Try again** | | **Something went wrong. Try again.** | **Try again** | | **This conversation is too long for TARS. Start a new chat to keep going.** | **New chat** | | **This chat belongs to a different production. Start a new chat to use TARS here.** | **New chat** | | **Your session has expired. Refresh the page to sign back in.** | None. Refresh the page and sign in again. | --- # 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.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.