> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/local-governance/access/local-governance-stack/property-tax/pt-user-manual/employee-user-manual/edit-property.md).

# Edit Property

Edit property allows users to make changes to the property details. The system allows users to make partial edits too.

To make changes search and view the property details. Click on the Edit Property option in the Action column for the corresponding property. The following details can be edited for the property:

* Only **Street Name** and **Door No.** can be edited in the **Location Details**.
* All information can be edited in the **Assessment Details**.
* None of the information allowed for edits in the **Ownership Details.**
* Documents can be re-attached.

Follow the same flow as in [New Property Registration](https://urban.digit.org/products/modules/property-tax/pt-user-manual/employee-user-manual#register-property) to submit the changes.


---

# 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.digit.org/local-governance/access/local-governance-stack/property-tax/pt-user-manual/employee-user-manual/edit-property.md?ask=<question>&goal=<user_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.