# CSV / Local File

Write records as CSV or JSONL to a file under a sandboxed root path.

## What this connection offers

Read a CSV or file location made available to the workspace. A filesystem path here refers to the environment offered by the connection, not arbitrary files on your own computer. Upload personal files through a file upload control.

| Detail | Value |
| --- | --- |
| Available uses | records |
| Sign-in | No sign-in |
| Catalogue identifier | `fs.local` |
| Connection scope | tenant |
| Direction | destination |

## Connect

1. Open **Connections**, choose to connect a service, and select **CSV / Local File** with the uses listed above.
2. Give the connection a recognisable name.
3. Complete creation; no external secret is required for this entry.
4. Check the connection status and run a connection test where offered.
5. Select this saved connection in the app, workflow step, storage browser, or Assistant task that needs it.

## Connection settings

| Setting | Type | Required | Secret | Explanation |
| --- | --- | --- | --- | --- |
| Root path (`root_path`) | text | yes | no | — |
| File path (relative to root) (`relative_path`) | text | yes | no | — |

## Diagnose a failure

Check the connected account, its permission to the target, the selected folder, table or collection, and the connection’s current status. A successful sign-in is not proof that a particular resource is shared with that account. An empty search or folder page is not necessarily an authentication error. Revoke access when it is no longer needed; deleting the connection can also affect its tools and synced data. See [connection lifecycle](/docs/connections/revoke-and-delete).