> For the complete documentation index, see [llms.txt](https://help.besmart.software/be.smart-site-management/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.besmart.software/be.smart-site-management/site-management/markings/inspect-markings.md).

# Inspect markings

Markings are either linked to Issues or ToDos, depending on which data storage is being used. This also means, that markings can also be created in the data storage. When it is created via the data storage, the marking doesn't have a locational information as a default. 

Inspect markings -window lists all of the markings user has a rights to, making it easy to manage these. Inspect markings can be opened from the bottom of the Tools menu:

<figure><img src="/files/UxBUUAE44tlK7UNTyyVC" alt=""><figcaption><p>Tools menu - Inspect markings at the bottom</p></figcaption></figure>

The Inspect markings -window has few key functionalities. As a preview, it lists all the markings, with the title, description and whether is it visible on the map.&#x20;

<figure><img src="/files/f2UkfRW3hDV6ylqZTCXx" alt=""><figcaption><p>Inspect markings -window</p></figcaption></figure>

On the top of the window is the search bar, which enable to search text strings from title and description fields. Each of the column can be used to sort the listing.&#x20;

On the right hand side of the window are located the main functionalities for each marking. The available functionalities change depending on the On map -value. If the marking is visible on the map, clicking the first button will zoom to that specific marking on the map. And Edit -button will allow to make edits to the marking.&#x20;

If the marking is not on the map, the only possibility in this window is to Add to map. Meaning that user can pinpoint the location for this specific marking.&#x20;


---

# 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://help.besmart.software/be.smart-site-management/site-management/markings/inspect-markings.md?ask=<question>&goal=<endgoal>
```

`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.