> For the complete documentation index, see [llms.txt](https://docs.arcade.software/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.arcade.software/kb/build/interactive-demo/share/internal-organization.md). # Internal Organization ## Organization ### How can I organize my Arcades? We offer tagging and folders for Arcades on the Growth plan. Once your Arcades are tagged, you'll be easily able to filter results and make sure you are seeing the most relevant Arcades. ### How do I add a folder? Folders are only available for users on the Growth plan. To add a folder, go to your Team Workspace and click the dropdown menu. You'll see an option to add a new folder there. You can add as many folders as you like! We don't yet support subfoldering, folders in your personal space, or folders with restrictions (i.e. only specific people can view or edit this folder), but those things are all on the roadmap! ### Can I set branding specifics for a folder? For sure! Growth users have access to Themes. When you edit a folder, you'll be able to select a theme to apply to all Arcades within it. When you move an Arcade into the folder, a popup will ask you if you want to change the branding of the Arcade to match the folder's theme. You'll be able to choose if you want to change that specific Arcade's branding or have it not match the folder's settings. *** ## Subfolders ### What are Subfolders? Subfolders help you organize your Arcade workspace as your demo library grows. They allow you to group related Arcades within folders for better structure and easier navigation. *** ### How do I create a subfolder? 1. Locate an existing folder 2. Click the **three dots (•••)** next to the folder 3. Select **Add new folder** 4. Name your folder 5. (Optional) Assign a theme *** ### Why should I use Subfolders? Subfolders are useful for: * Organizing demos by team, use case, or customer * Keeping large libraries clean and navigable * Structuring content for different workflows (sales, marketing, onboarding, etc.) --- # 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.arcade.software/kb/build/interactive-demo/share/internal-organization.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.