> 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/products/fast-track-maptemplate/location-details-configuration.md).
# Location Details configuration
This page provides a step-by-step guide on how to configure the content displayed on the **Location Details** page in your web app.
When you load your solution in the web app, several pages are available — one of them is the Location Details page, which appears when a user selects a location on the map.
You can customize the content of the Location Details page directly in the CMS. This includes the **description**, **image**, and **additional details**. [This guide ](/products/cms/additional-location-details.md)will walk you through how to set up those additional details.
To display the additional details in the app, make sure the **“Show in app”** toggle is enabled.
In the image below, you can see how these settings are configured in the CMS.
CMS additional location details
Below that, you'll find an example of how the additional location details appear in the web app.
Additional location details in the web app
---
# 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/products/fast-track-maptemplate/location-details-configuration.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.
