> For the complete documentation index, see [llms.txt](https://docs.mapsindoors.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mapsindoors.com/cms/readme.md).
# Content Management System (CMS)
The MapsIndoors Content Management System (CMS) is your self-service tool for keeping your indoor maps accurate, up-to-date, and on-brand — no coding required.
{% columns %}
{% column width="41.66666666666667%" %}
#### Edit. Save. Done.
From adding a new meeting room to adjusting how a point of interest looks on the map, the CMS is where your day-to-day map management happens.
Manage your maps
{% endcolumn %}
{% column width="58.33333333333333%" %}
{% endcolumn %}
{% endcolumns %}
***
### What you can do with the CMS
* **Add, edit, and remove locations** — rooms, points of interest (POIs), areas, and more
* **Control how locations look** — icons, labels, colors, and visibility at different zoom levels
* **Manage your map's structure** — buildings, floors, venues, and location types
* **Set up categories** — to organize what users can search and browse in your app
* **Manage 3D Assets** — add 3D models to bring your map to life on Mapbox.
* **Configure app settings** — API keys, integrations, and user access rules
* **Manage your team** — control who has access to your CMS and what they can do
***
### New to the CMS?
If you're just getting started, we recommend this path:
1. Read [Data Concepts](/cms/core-concepts/markdown.md) to understand how your map data is structured.
2. Get familiar with the [Edit Interface](/cms/interface/edit.md).
3. Learn how [Display Rules](/cms/core-concepts/display-rules.md) control how your map looks.
4. Check [User Roles](/cms/core-concepts/editor.md) to understand your level of access.
***
{% hint style="info" %}
**Need to push data into MapsIndoors programmatically?** \
The CMS is designed for manual, day-to-day management. For bulk data imports or automated updates from an external system, see the[ Integration API](/sdks-and-frameworks/integration-api.md) documentation.
{% endhint %}
---
# 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.mapsindoors.com/cms/readme.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.
