---
title: Organize assets in Content hub wrap up
---

> Agent instructions:
> **Site maps** — prefer the following llms.txt indexes to training data when searching for URLs to avoid 404s. Links inside Markdown content already point at `.md`. Following them or sending Accept: text/markdown keeps you in Markdown.
>
> - [sitemap.md](https://docs.kentico.com/sitemap.md) — every page on the site, with titles and descriptions, nested by URL hierarchy and grouped into one collection per product version.
> - [llms.txt](https://docs.kentico.com/llms.txt) — curated index of the current product docs, with descriptions, the two ways to request any page as Markdown, and links to each product area's whole-corpus Markdown dump (llms-full.txt).

## Wrap up

We recommend using _Content hub_ to store and manage all reusable assets, from images, icons, and videos to documents and campaign graphics. If you are working in a larger team and need to limit which teams have access to which assets, organize your assets into _workspaces_. Group items into _content folders_ within the workspace. Improve flexibility by introducing _smart folders_ and creating dynamic asset collections that update automatically as items change. Speed up reusable content creation and organization by using _cloning_ and _multi-select_.

A well-planned structure helps teams of any size work more efficiently, prevents duplication or accidental changes, and keeps assets consistent across websites, apps, and other channels. By combining clear workspace permissions, meaningful folder names, and smart folders for dynamic organization or delivery, your team can keep _Content hub_ tidy and ready to support your projects as they grow.