> For the complete documentation index, see [llms.txt](https://docs.kaedim3d.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kaedim3d.com/groups.md). # Groups {% embed url="" %} Learn how to create and use folders {% endembed %} Groups allow you to organize assets together based on their tags, generation quality, and creator (studio only). For example, you can create a group that specifically filters assets with the tags: "plant" and "furniture," in Standard quality, and were made with the account .
Groups can be added by clicking "+ Add group" in the navigation bar.
When adding a folder, you can search through tags from your existing models or create new tags for future generations. Assets with these tags will show up in your folder. If "Or" is selected, the folder will contain assets with **any** of the selected tags. If "And" is selected, the folder will contain assets that have **all** of the selected tags.
{% hint style="info" %} Relevant tags are automatically added to your new generations based on your input images. {% endhint %} ## Enterprise Features Enterprise customers can also create folders organized by creator and custom style.
Studio admins can click "Save for Studio" to make groups visible to all of their teammates. Studio users can also add tags to their generations on the create page.
Using this feature, you can search through tags from your team's asset library and add any relevant tags to your new generation. Studio admins can also create new tags for future generations. --- # 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.kaedim3d.com/groups.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.