> 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/view-interface.md).
# View Interface
***
View Interface of the CMS
***
### When to use it?
Use the View interface to quality-check your map before sharing it with users. Because it reflects your live solution, it's the most accurate way to verify that locations look correct, routes work as expected, and any [App Configuration](/products/web-app.md#configuration) settings are applied properly.
Common uses include:
* Checking that Display Rule changes look right on the map
* Testing that wayfinding routes are working correctly
* Verifying that App User Role restrictions are applied as expected
* Confirming how your map looks before a launch or update
***
### Refreshing after changes
The View interface does not update automatically when you make changes in Edit mode. If you have both tabs open at the same time, you'll need to manually refresh the View tab to see your latest changes reflected.
{% hint style="info" %}
**Tip:** Make all your changes in Edit first, save them, then switch to View and refresh — rather than switching back and forth after every individual change.
{% 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.mapsindoors.com/cms/interface/view-interface.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.