> 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/plugins/integrations.md).

# Integration guides

Provider-by-provider integration setup for Filed.

These guides follow the same order as the Integrations page. A workspace administrator creates each connection in **Plugins**; the account they authorize determines what Filed can access.

1. [Tax software](/reference/plugins/integrations/tax-software.md)
2. [Practice management](/reference/plugins/integrations/practice-management.md)
3. [Accounting & ERP](/reference/plugins/integrations/accounting-and-erp.md)
4. [Document management](/reference/plugins/integrations/document-management.md)
5. [Communications](/reference/plugins/integrations/communications.md)
6. [Productivity](/reference/plugins/integrations/productivity.md)
7. [Documents & signatures](/reference/plugins/integrations/documents-and-signatures.md)
8. [CRM](/reference/plugins/integrations/crm.md)
9. [Payroll, spend & payments](/reference/plugins/integrations/payroll-spend-and-payments.md)

## How document and practice management integrations work

Document management (DMS) and practice management (PMS) connections are a live, two-way link between Filed and the system your firm already uses. Once connected, files flow in without anyone uploading them by hand.

* **You choose the scope.** During setup you select which folders to connect. Filed syncs content only from the locations you select.
* **New documents sync on their own.** Filed detects documents added to a connected folder and pulls them in, so the workspace reflects what is in your DMS or PMS without a manual upload step.
* **Setup is short.** A workspace administrator grants access during onboarding. Most firms finish a connection in under 30 minutes.

**Best practice:** keep a clear, consistent naming convention in the folders you connect. Filed uses file names as one signal when classifying and displaying documents, so descriptive names produce better organization. See [Organizing documents](/reference/products/binder/organizing-documents.md).

If your DMS or PMS is not on the list, you can still upload documents directly. See [Managing files](/reference/clients/managing-files.md).

## Connection flow

### 1. Name the connection and choose access

Select the provider in **Plugins**, choose **Connect**, and enter a name that identifies the account or environment. Read access is always enabled. Write access is enabled by default, but you can clear it to make the connection read-only; you can change this later from the connection settings.

### 2. Authorize the provider

Filed then opens the provider's sign-in page or, for organization-specific apps, asks for the required credentials in the next dialog step.

### 3. Authorize and verify

Approve the provider's consent screen and return to Filed. Filed verifies the connection before it becomes active. Pending or failed connections can be reconnected from the provider page.


---

# 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://docs.filed.com/reference/plugins/integrations.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.