> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/user-guide/files-and-storage/configure-resource-storage.md).
# Configure resource storage and app uploads
Easily create new storages or upload files to your storage from the Data Editor.
### Upload files as an App Builder
In the menu on the left, go to the storages section and click on the storage to which you want to upload a file. Then, simply click on **Upload File** in the upper right corner, and choose the file you wish to upload.
### Add a storage as an App builder
To add a new storage to your resource, go to the storages section in the **Data Editor** menu, and click on the *Create Storage* button. Then, you will need to configure the queries that suit your needs, only the *Upload* query is required.
### Allow app users to upload files in Classic App Builder
You can allow your app users to upload files to your storage by using a **File Picker** form. Drag and drop it into your app, then set it up by choosing the Output Format **Save to Storage** and choosing the storage that you want to upload the file to.
 
---
# 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://docs.jetadmin.io/user-guide/files-and-storage/configure-resource-storage.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.
