> 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/sdks-and-frameworks/built-in-map-edits.md). # Built-In Map Edits A writable SDK add-on for MapsIndoors that allows you to integrate self-service map editing capabilities directly into your own product This extension allows your customers to make real-time updates to their indoor maps without leaving your application or requiring external assistance. You maintain complete control over the implementation, including user interface design, permission structures, and functionality. The SDK provides the core mapping and editing capabilities, while you determine how these features appear and function within your product ecosystem.

This flexibility enables you to offer a seamless, fully integrated mapping experience that feels like a natural extension of your platform rather than a third-party tool. Your customers can easily manage common mapping tasks—such as renaming spaces, repositioning assets, changing location types, or adding new points of interest—all within your familiar interface.

The following documentation will guide you through implementing Built-in Map Edits in your application, from initial setup to advanced customization options. Whether you're building workplace management software, event planning tools, or any platform that benefits from interactive indoor maps, Built-in Map Edits provides the foundation for creating a powerful, user-managed mapping experience. --- # 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/sdks-and-frameworks/built-in-map-edits.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.