> For the complete documentation index, see [llms.txt](https://docs.archisketch.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.archisketch.com/guide/user-en/manage-project/project-folder.md).
# Move project folder
## Manage and share projects with folders
In Arkisketch, you can organize and share projects by folder.\
Projects organized into folders can be managed efficiently, and you can also share folders with the users you want.
Click a folder name to view projects by organized folder.\
Of course, if you click All Projects at the top, you can see all projects at a glance without folder separation.
## How to use folder features
#### Create a folder
* Click the \[New Folder] button on the screen.
* Enter a folder name and save it to create a new folder.
#### Put projects into a folder
* Single move:
* Click the project's \[More] button.
* Select \[Move to Folder] to move it to the desired folder.
Bulk move:
* Select multiple projects.
* Click the \[Move to Folder] button in the top menu to move them all at once to the desired folder.
#### Manage folders
* Click the \[More] button to the right of the folder name.
* Manage folders by selecting features such as create subfolder, rename, delete, and share.
---
# 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.archisketch.com/guide/user-en/manage-project/project-folder.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.
