> For the complete documentation index, see [llms.txt](https://datalab-docs.datacamp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://datalab-docs.datacamp.com/connect-to-data/files.md).
# Files
A files data source allows you to share files in a read-only way between multiple workbooks within a single account context.
## Set up a file data source
Select **Data Sources** in the sidebar and click on **New Data Source** in the screen that follows. You'll be prompted to select the type of the data source. Either drag in files you want to use to create a data source or press **browse files** to select the files you want to upload.
A *files* data source will be created and you'll see an overview on the following screen. Here you can update the name, change the description, upload more files or just browse a preview of the data.
## Query a files data source
You can now query your files data source with a [SQL cell](/work/sql-cell.md). Select it in the **Select source** dropdown in the top left corner of a SQL cell. You can query the individual files by specifying their name in the `FROM` clause. The schema of the data source is also available by clicking on **Browse Files**, from here it's also easy to start querying individual files.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://datalab-docs.datacamp.com/connect-to-data/files.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
