> For the complete documentation index, see [llms.txt](https://docs.filed.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.filed.com/reference/partners/rightworks.md).

# Rightworks

## What Rightworks is and how it relates to Filed

Rightworks is a hosted cloud-desktop environment where tax software such as Drake runs on remote servers rather than on the firm's local machines. Because the tax-software environment is hosted and isolated, Filed cannot connect to it the same way it connects to locally installed software.

Firms in a Rightworks environment use Filed through a manual backup-file process: export a backup from the tax software inside Rightworks, upload it to Filed, then download and restore the completed file after AI preparation is done.

## Using Filed in Rightworks (manual backup-file process)

Firms export a backup file from their tax software inside Rightworks, upload it to Filed along with supporting documents, and download and restore the completed file after AI preparation is complete.

### Drake - manual backup file process

For Drake, the manual process has three parts:

1. Create a Drake backup file inside Rightworks.
2. Upload it to Filed AI Prep along with prior-year returns and current-year documents.
3. Download and restore the completed backup once preparation is complete.

If a backup file cannot be retrieved after preparation, contact <support@filed.com>.

## Getting help

For issues with backup-file retrieval after AI preparation is complete, contact Filed support at <support@filed.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 by asking a question.

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

```
GET https://docs.filed.com/reference/partners/rightworks.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.