> 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/edit.md). # Edit Interface The Edit interface is your main workspace within the CMS — the first thing you see when you log in and where all map management happens. ***

*** The Edit interface is organized into three areas: **1 — Selectors and Filters** control what data is visible on the map and in the list. Use them to narrow down by Venue, Building, Floor, Location Type, Category, or App User Role. **2 — Location Details Editor** opens when you select a location on the map. This is where you view and edit everything about a location — its name, type, visibility, images, custom properties, and more. **3 — Actions Toolbar** sits at the bottom of the screen and contains tools for adding and editing locations, managing the route network, and adjusting your map view.

			Cover image
Selectors and Filters	Control what data is visible on the map and in the list.	Selectors and Filters	image.png
Location Details Editor	View and edit everything about a location.	Location Details Editor	image.png
Actions Toolbar	Your toolkit for adding locations, managing the route network, and adjusting your map view	Actions Toolbar	image.png

--- # 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/edit.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.