> For the complete documentation index, see [llms.txt](https://docs.diaflow.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.diaflow.io/productivity-tools/diaflow-vectors/how-to-guides/organizing-your-content.md).
# Organizing Your Content
## **How to Create and Manage Groups**
Steps:
1. Navigate to the Group tab
2. Click Create a vector group to organize your content (best practice)
3. Use Add to Group for existing files:
* Select files in Root tab
* Choose Add to Group action (not recommended for search from vector groups)
* Select target group
* Confirm selection
Expected Result: Files appear in both Root and selected Group.
## **How to Move Content Between Groups**
Prerequisites: You have content in groups that you want to reorganize.
Steps:
1. Navigate to the Group tab
2. Select files you want to move
3. Choose Remove from group to remove from current group
4. Navigate to Root tab
5. Select the same files
6. Choose Add to group and select new destination
Expected Result: Content is moved from original group to new group while remaining in Root.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.diaflow.io/productivity-tools/diaflow-vectors/how-to-guides/organizing-your-content.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.