> 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/interface/interface-overview.md). # Interface Overview *** The CMS is organized into five main areas, accessible from the top navigation bar. Each area has a focused purpose — together they give you complete control over your map solution.

**1)** [**Edit**](/cms/interface/edit.md) is your main workspace for adding and updating locations on the map. **2)** [**View**](/cms/interface/view-interface.md) lets you browse the map without making changes. **3)** [**Solution Details**](/cms/interface/solution-details-interface.md) is where you manage the structure behind your data — types, categories, and visibility settings. **4)** [**Media Library**](/cms/interface/media-library.md) holds all your icons 2D and 3D models. **5)** [**Settings**](/cms/interface/settings-interface.md) controls who has access to your CMS. *** ### Interface Areas

		Cover image
Edit	Add, edit, and manage locations directly on your map	CMS Edit View.png	Edit Interface
View	Browse your map in read-only mode	CMS Viewing View.png	View Interface
Solution Details	Manage location types, categories, and visibility rules	CMS Solution Edit View.png	Solution Settings
Media Library	Upload and manage icons and 2D models	CMS Media Library View.png	Media Library
Settings	Control who has access to your CMS	CMS Settings View.png	Settings Interface

--- # 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/interface/interface-overview.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.