> 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/integrations/document-management/smartvault.md). # SmartVault With this integration connected, you can use Filed **Chat** and **Routines** to retrieve information from SmartVault and, when **Write** access is enabled, perform approved actions in 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 autonomous authentication. Filed uses the SmartVault API client and RSA private key that you provide for this connection to request a short-lived delegation token for the selected SmartVault user. There is no browser sign-in or OAuth popup. ## 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. You also need these values from your SmartVault autonomous API client: * Client ID * Delegated user email address — the SmartVault account Filed will act as * Firm URI * RSA private key — PEM or base64-encoded PKCS#8 format The delegated SmartVault user must have already authorized the API client and have access to the folders Filed needs. Filed encrypts these values as connection credentials and uses them only to authenticate this SmartVault connection. ## Connecting SmartVault to Filed 1. Go to **Plugins**, then open **SmartVault**. 2. Select **Connect SmartVault** and name the connection. 3. Enter the Client ID, delegated user email, Firm URI, and RSA private key. 4. Select **Connect SmartVault**. Filed verifies the credentials and connects without opening a SmartVault sign-in page. ## 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 while connecting.** Confirm the Client ID, delegated user email, Firm URI, and RSA private key are entered correctly. The private key must be PEM or base64-encoded PKCS#8. Also confirm the delegated user has authorized the API client in SmartVault and has access to the required vaults. **401 Unauthorized while browsing files.** Confirm the connection is active and reconnect after correcting the delegated user or API client authorization. The delegated user needs permission for the specific Account/Vault/Folder path being accessed. **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. ## Using this integration with Filed Chat and Routines Use **Chat** for one-off questions and guided work on a client, such as finding SmartVault information, summarizing it, or preparing an approved next step. Use **Routines** to automate repeatable work with SmartVault data on a schedule or in response to a trigger. Both experiences respect the connection's access: they can only use data the authorized account can reach, and they can only perform changes when **Write** is enabled. Review changes in the connected application before you finalize them. ## Example prompts Use these as starting points and replace the bracketed details with the client, date range, folder, record, or task you need. Filed will only run write actions when this connection's **Write** access is enabled. * “Find the SmartVault folder for \[client name] and list the most recent source documents.” * “Summarize the tax documents in \[folder name] and flag anything that appears missing.” * “With write access enabled, create an approved folder structure for \[client name] and upload \[file name].” ## Capabilities ### Find and read client documents Use Filed to browse, search, and retrieve the files and folders available to the connected account. This is useful for gathering source documents, answering questions, and preparing a client file for review. ### Organize approved content When **Write** access is enabled, Filed can create folders and upload, move, rename, or update approved documents where the connected account has permission. Use this to keep client deliverables and workpapers in the agreed location. ### Preserve your provider’s access model Filed works within existing folder, site, shared-drive, or library permissions. Use the provider’s own sharing controls to decide which client content the connection can reach. --- # 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/integrations/document-management/smartvault.md?ask=&goal= ``` `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.