> For the complete documentation index, see [llms.txt](https://learn.withessential.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.withessential.com/customers-and-work/properties/set-a-propertys-access-info-and-notes.md).

# Set a property's access info and notes

The property page has two free-text cards on the right. Access Info is for how to get into the site, such as gate codes, a lockbox, where to park, or who to ask; it reads "No access info" until you add something.

Notes is for general notes about the property and reads "No notes about this property" when empty. Click Edit on either card to update it. Both are visible to your team on the property; use Access Info for what a technician needs to reach the equipment.

Links pasted into either field (for example a map link or a building portal URL) become clickable wherever the text is shown in the web app — on the property page, in scheduling, and on tasks — and open in a new tab. Notes, custom field values, technician instructions, scheduling notes, and comments shown in the web app work the same way.

> **Where to find it:** On the property page, the Access Info and Notes cards (right side), each with an Edit link

## Related guides

* [Add or manage contacts on a property](/customers-and-work/properties/add-or-manage-contacts-on-a-property.md)
* [Adding an asset group to a property](/customers-and-work/properties/adding-an-asset-group-to-a-property.md)
* [Create a property](/customers-and-work/properties/create-a-property.md)
* [Move a property to another customer](/customers-and-work/properties/move-a-property-to-another-customer.md)
* [Use Customer Billing or set Property Billing](/customers-and-work/properties/property-billing-profile-the-customer-default-or-its-own.md)


---

# 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://learn.withessential.com/customers-and-work/properties/set-a-propertys-access-info-and-notes.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.
