> 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/add-or-manage-contacts-on-a-property.md).

# Add or manage contacts on a property

The Contacts card on the property page shows the people tied to that property and their roles, such as who to contact for approvals. Use Add on the Contacts card to put an existing contact on the property and choose their role; when there are none yet, the card reads "No contacts on this property".

Contacts with a Primary role appear first, followed by Secondary contacts. Names are alphabetical within each priority. A property-specific assignment takes precedence over the same customer-level role.

Each contact has an Edit action. Contacts belong to the customer account, so the same contact can be on more than one of that customer's properties, each with its own role.

> **Where to find it:** On the property page, the Contacts card (right side), the Add button

## Related guides

* [Create a property](/customers-and-work/properties/create-a-property.md)
* [Adding an asset group to a property](/customers-and-work/properties/adding-an-asset-group-to-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)
* [Property files and who can see them](/customers-and-work/properties/property-files-and-who-can-see-them.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/add-or-manage-contacts-on-a-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.