> 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/document-management/smartvault.md).

# SmartVault

## What this integration does

The SmartVault integration gives Filed direct access to client documents stored in your SmartVault vaults, without manual uploads. SmartVault organizes content in a three-level hierarchy: Account, Vault, and Folder. Filed navigates this hierarchy to locate client folders and maps them to client records. Once clients are imported, Filed can read and write files within each client's SmartVault folder, so your team can file documents back to SmartVault directly from Filed.

SmartVault uses a proprietary OAuth flow. During connection, you sign in through SmartVault's integrated applications page and authorize Filed to act on your behalf, and Filed holds the resulting access and refresh tokens. Unlike the other DMS integrations, SmartVault's refresh tokens have a defined expiry period: if the connection lapses after an extended period, you will need to disconnect and reconnect to obtain a fresh token.

## Before you start

You need a SmartVault account with access to the vaults that contain your client files. Client folders must be organized with one folder per client inside a vault. The person completing the connection must be able to sign in to SmartVault and grant access through the integrated applications authorization page.

## Connecting SmartVault to Filed

## Importing clients from SmartVault

## What Filed can do with SmartVault

Once connected, Filed exposes the following actions against your SmartVault vaults:

**Browsing and finding files**

* List the contents of a folder using the Account/Vault/Folder path
* Retrieve metadata for a specific file or folder node
* Search for files and folders by name within a folder subtree

**Managing files and folders**

* Download a file
* Upload a file to a folder
* Create a new folder
* Move a file or folder to a different path
* Copy a file or folder to a destination path
* Delete a file or folder

These capabilities power binder creation and update: when Filed prepares a client's binder, it uses this action set to retrieve source documents from SmartVault and to file completed documents back.

## Troubleshooting

**Connection error after the integration was working.** SmartVault refresh tokens have a limited lifespan. If the connection has been inactive for an extended period or the token has expired, disconnect the integration and reconnect to generate a fresh token.

**Clients are not appearing after import.** Confirm that the SmartVault account used during connection has access to the vaults and that client folders exist at the correct level in the Account/Vault/Folder hierarchy. Filed maps the immediate children of the selected path as client records; deeply nested structures will not be detected.


---

# 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/document-management/smartvault.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.
