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

# Plugins & integrations

Plugins are the connections that make Filed useful at the point of work. They fall into two groups:

* **Prowork** surfaces bring Filed's AI assistant into the tools preparers already use every day.
* **Integrations** pull client data from the systems where it already lives.

Together they let Filed read from the right sources and respond in the right place.

The Plugins page is at **Plugins** in the Filed web app.

## Prowork - bring AI where you work

Prowork puts Filed's AI assistant inside the tools preparers spend their day in: a Windows desktop sidebar, an Excel task pane, and a Google Sheets sidebar. The AI comes to the preparer rather than requiring a context switch to a separate app.

Each Prowork installation is called a surface. A surface is tied to a specific device and user combination, so installing on a laptop and a desktop creates two separate surfaces, each with its own name and login code. One person can have multiple surfaces across different tools and devices.

### Desktop

A Windows native app that docks as a sidebar on the right side of the screen, sitting alongside tax software automatically when it opens. [Learn more about Prowork Desktop](/reference/plugins/prowork/desktop.md).

### Excel

An Office task pane add-in that opens a Filed sidebar inside any Excel workbook, letting preparers chat with the AI and write data directly into the active sheet. [Learn more about Prowork for Excel](/reference/plugins/prowork/excel.md).

### Google Sheets

A Google Workspace add-on that delivers the same Filed AI sidebar inside Google Sheets, with the same capabilities as the Excel add-in. [Learn more about Prowork for Google Sheets](/reference/plugins/prowork/google-sheets.md).

## Integrations - connect your data sources

Integrations are the connections to the systems where client data already lives. They are what give Prowork and the rest of Filed their context: when a preparer asks about a client's income, Filed pulls the answer from the documents and data that integrations have made available.

Integrations are set up once at the workspace level. Any team member with the right permissions can connect an integration, and once connected it is available to everyone in the workspace.

### Tax software

Filed connects to the major tax preparation platforms to sync client lists and return data. Supported providers: CCH Axcess, Drake, Lacerte, and UltraTax CS.

### Document management

Filed connects to the document management systems where client files are stored. Supported providers: Box, Dropbox, Google Drive, SharePoint, and SmartVault.

### Email

Filed can connect to email accounts to give the AI access to client correspondence. Supported providers: Gmail, Outlook, and IMAP.

## MCP - connect AI assistants

The Filed MCP server connects your workspace to AI assistants like ChatGPT and Claude over the Model Context Protocol. The assistant can query your workspace, make changes, and upload files, authenticated through Filed's own sign-in. [Learn more about MCP](/reference/plugins/mcp.md), or jump straight to the setup guides for [ChatGPT](/reference/plugins/mcp/chatgpt.md) and [Claude](/reference/plugins/mcp/claude.md).

## Filed Printer

*Coming soon!*

Filed Printer is a virtual printer that appears in the operating system's printer list. Preparers can print from any desktop application - tax software, a browser, a PDF viewer - and the document lands directly in their Filed workspace. It appears under **Others** on the Plugins page. [Learn more about Filed Printer](/reference/plugins/filed-printer.md).

## How connecting works

The general pattern is the same across all plugins: find the plugin on the Plugins page, click **Install** or **Connect**, complete the guided steps, and the plugin shows as active.

The two groups use different authentication models:

* **Prowork surfaces** use a login-code model: Filed generates a short-lived token that the preparer pastes into the app or add-in. The token is scoped to one workspace and one device and should not be shared.
* **Integrations** use either OAuth (the provider's own authorization screen) or credential entry (username and password for the service), depending on what the provider supports.

## Permissions and team access

* **Integrations** are connected by workspace admins on behalf of the whole workspace.
* **Prowork surfaces** (Desktop, Excel, and Google Sheets) are installed by each team member on their own devices and accounts.
* **Filed Printer** is per-user too: each person sets it up on each computer they use, and each workspace requires its own separate printer setup.

All Prowork installations across the workspace appear in the Installations table on each Prowork plugin page, so admins can see which devices are connected.


---

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.filed.com/reference/plugins.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
