> For the complete documentation index, see [llms.txt](https://docs.aqua-cloud.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aqua-cloud.io/documentation/projects-and-folders/folders/import-project-folder.md).

# Import project folder

Import a specific project folder with step-by-step guidance. Learn how to customize data imports for efficient folder-level management in your workspace.

Now you can not only import data for the entire project, but also for a specific folder, allowing you to tailor the data management process to your individual needs.

<figure><img src="https://3920520305-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyZbW8vbNs5hz8x57emJJ%2Fuploads%2FRHnvkS0UEUxv8MgC0HAC%2Fchrome-capture-2023-7-9%20(4).gif?alt=media&amp;token=66903f42-35fc-4137-8b35-0202f381fc37" alt="" width="563"><figcaption><p>Initiating an import to the selected folder from the context menu</p></figcaption></figure>

Simply right-click on the folder you are interested in and select the import option. More information and guidance on the data import process can be found in this article: [Import project](/documentation/projects-and-folders/projects/import-project.md). It provides detailed step-by-step instructions and practical tips for importing your selected data more efficiently.


---

# 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.aqua-cloud.io/documentation/projects-and-folders/folders/import-project-folder.md?ask=<question>&goal=<user_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.
