> 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/editing-a-marking.md).

# Editing a marking

Marking can be edited in Site Management by selecting a marking. By clicking a marking user can open possible attachments to this marking and list additional options. Additional options include editing and deleting marking. All the fields can be edited.

{% hint style="info" %}
Please note, that when using Autodesk Construction Cloud, the delete marking -functionality doesn't delete the Issue from Autodesk Construction Cloud.
{% endhint %}

<figure><img src="/files/XoEhabO3egQHwxPrpRpP" alt=""><figcaption><p>Editing an existing marking</p></figcaption></figure>

Because markings and ToDos / Issues are linked to each other, these can also be edited in Autodesk Construction Cloud and in Trimble Connect. When creating and editing marking in Autodesk Construction Cloud orin Trimble Connect , user might have few more fields they can fill.&#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/editing-a-marking.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.