> 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/contacts/edit-a-contacts-details-or-where-their-roles-live.md).

# Edit a contact's details, or where their roles live

Use Edit on the contact page to change a contact's name, email addresses, phone numbers, title, and notes. A contact has one primary **Email** and can have any number of **Additional emails**; see [Give a contact more than one email address](/customers-and-work/contacts/give-a-contact-more-than-one-email-address.md). The contact's roles, meaning which property they're on and what they're responsible for (for example approvals or billing), are listed under the Roles tab.

To update extra information defined by your business, use **Edit** on that custom field's card in the right column and click **Save**. Each field saves individually. Required fields must be filled in; optional fields can be cleared. Cancel discards the draft. Admins can add or change the available fields in [Settings → Custom Fields](/administration/settings/create-and-manage-custom-fields.md).

The Edit form is also where you set roles: it has a Customer-level roles section and a Property-level roles section (use "+ Add Property-level roles" to pick a property and its roles). Open the property picker and type in **Search properties** to narrow the list by its displayed name or address; your selected properties stay selected while you search. The property picker's list starts with a **Select all** option that assigns every property still available to that role group in one click, which saves clicking through them individually on an account with many properties. You can alternatively add a property role from that property's own Contacts card. With the picker open, use the arrow keys to move through results and Enter to choose a property; Escape closes the picker.

You can delete a contact even while their automations are in progress:

1. Open the contact and choose **Delete Contact**.
2. Review the confirmation and select **Delete**.

Future automated messages to that contact stop, and their roles are removed. Job approval outreach is recalculated using the remaining eligible contacts and their role priorities. If no eligible contact remains, no replacement job approval outreach is scheduled. Previous messages stay in the history; messages already sent cannot be recalled.

A contact is tied to one customer; to involve a different account, use or create a contact under that customer.

> **Where to find it:** On the contact page, the Edit link (which sets roles too) and the Roles tab; you can also add a property role from that property's Contacts card

## Related guides

* [Creating a contact](/customers-and-work/contacts/creating-a-contact.md)
* [Give a contact more than one email address](/customers-and-work/contacts/give-a-contact-more-than-one-email-address.md)
* [Contact roles explained](/customers-and-work/contacts/contact-roles-explained.md)
* [Give a contact access to the customer portal](/customers-and-work/contacts/give-a-contact-access-to-the-customer-portal.md)
* [See and browse all your contacts](/customers-and-work/contacts/see-and-browse-all-your-contacts.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/contacts/edit-a-contacts-details-or-where-their-roles-live.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.