> 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/making-a-property-active-or-inactive.md).

# Making a property active or inactive

Inactive properties show an **Inactive** pill near the top of the property page and in property lists. Active properties have no status pill. To change it, click Edit on the property page to open the Edit Property window, choose Active Property or Inactive Property under Status, then click Save.

Marking a property active or inactive doesn't delete it or its history; it simply reflects whether the property is currently in service. One thing to know before deactivating: if you switch an active property to inactive while it still has running subscriptions, the Edit Property window shows a warning that reads The following subscriptions will be canceled when this property is deactivated, along with a list of the affected subscriptions so you can review exactly what's involved.

Saving the change cancels those subscriptions. Already-completed and draft subscriptions aren't listed, because they aren't affected. After saving, if any subscription couldn't be canceled, you'll see a message telling you how many failed so you can follow up.

Since deactivating ends active billing arrangements, double-check the list before saving. You can reactivate a property later by opening Edit Property again and setting the status back to Active Property, but previously canceled subscriptions aren't automatically restored.

A property's status is also linked to its customer's: if you deactivate a property and it was the customer's last remaining active property, the customer is automatically deactivated too. Likewise, reactivating a property while its customer is inactive automatically reactivates the customer. Customers have their own status control on the customer page; see [Making a customer active or inactive](/customers-and-work/customers/making-a-customer-active-or-inactive.md).

Inactive properties are hidden by default in the customer's **Properties** tab. Clear the **Hide inactive properties** checkbox at the bottom right of that table to find and open them. Your browser remembers this choice across customer pages and page reloads.

> **Where to find it:** Property page, Edit Property modal, Status field

You can also [reactivate the selected property and its customer when saving a visit](/customers-and-work/scheduling/why-cant-i-schedule-a-visit-here-inactive-customer-or-property.md). Other inactive properties stay inactive, and existing Automation settings are preserved so recurring-service outreach can resume.

## Related guides

* [See and browse all your properties](/customers-and-work/properties/see-and-browse-all-your-properties.md)
* [Create a property](/customers-and-work/properties/create-a-property.md)
* [Use Customer Billing or set Property Billing](/customers-and-work/properties/property-billing-profile-the-customer-default-or-its-own.md)
* [Move a property to another customer](/customers-and-work/properties/move-a-property-to-another-customer.md)
* [Making a customer active or inactive](/customers-and-work/customers/making-a-customer-active-or-inactive.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/making-a-property-active-or-inactive.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.