> For the complete documentation index, see [llms.txt](https://guide.plusai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.plusai.com/other/live-snapshots/organizing-your-content.md).
# Organizing your content
### Folders
You can create folders in your Drafts and Team space. You cannot nest folders, i.e., create a folder inside another folder.
To move content into a folder, you can drag and drop from the grid or use the "Move to" action.
You can also select multiple items and move them at once.
Moving multiple Snapshots at once
### Search
You can search for Snapshots, Pages, and Folders across your Personal and Team spaces. You can search for:
* Snapshot and Page titles and descriptions
* Snapshot URLs
* Text within Snapshots ✨
Use search to find a specific piece of content
### Sort and filter
You can filter for Snapshots, Pages, and Folders and sort by Date created or the Name of the document.
---
# 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://guide.plusai.com/other/live-snapshots/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.