> 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/administration/settings/enable-or-disable-the-customer-portal-for-all-customers.md).

# Enable or disable the Customer Portal for all customers

The Customer access card on the Customer Portal settings page turns portal access on or off for your whole book of business at once. The Customer Portal settings page appears whenever your role can manage portal settings; the page opens with an Enable Customer Portal switch. Change the switch and select **Save** to turn the portal on or off. The Customer access card (with the rest of the configuration cards) appears once the portal is turned on.

If the page is missing but you need to manage portal rollout, contact your business's administrator to review your role.

It shows how many customers currently have portal access, and the action applies only to customers marked Active - inactive customers are skipped. Enable for all grants every active customer and their non-deleted contacts portal access. Disable for all removes portal access from those active customers and their non-deleted contacts.

Both actions ask you to confirm first. Use this when rolling the portal out or pulling it back across all active customers; to change one customer, do it on that customer instead.

This controls who can sign in. To control which portal sections customers can see after they sign in, use the Customer-facing sections card on the same settings page.

> **Where to find it:** Settings -> Customer Portal, the Customer access card

## Related guides

* [Set your Customer Portal heading and URL](/administration/settings/set-your-customer-portal-heading-and-url.md)
* [What your customers see in the Customer Portal](/administration/what-your-customers-see-in-the-customer-portal.md)
* [Add or edit a pricebook item](/administration/settings/add-or-edit-a-pricebook-item.md)
* [Add the intake form to your website](/administration/settings/add-the-intake-form-to-your-website.md)
* [Automate task statuses with Task Automations](/administration/settings/automate-task-statuses-with-task-automations.md)
* [Build your intake form](/administration/settings/build-your-intake-form.md)
* [Feature availability and setup](/getting-started/getting-started/feature-availability-and-setup.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/administration/settings/enable-or-disable-the-customer-portal-for-all-customers.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.