> 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/set-your-customer-portal-heading-and-url.md). # Set your Customer Portal heading and URL Customer Portal settings control the portal where customers view quotes, approve work, see invoices, and pay online. The page opens with an Enable Customer Portal switch: turn it on and select **Save** to bring the portal online and reveal the configuration cards below. Turning it off and selecting **Save** takes the portal offline for all customers until you turn it back on - your settings are kept, and turning it off asks you to confirm first. Under Branding, the Portal heading is the title customers see when they land in the portal (up to 80 characters). The same configured heading appears at every brand-specific portal URL; the brand's name, logo, and color still match that URL. Under Portal URL you replace the default base address with a memorable slug after your portal prefix (shown on the page, e.g. grow\.withessential.com/customer-portal/) - use 3 to 40 lowercase letters, numbers, and hyphens, starting and ending with a letter or number. As you type, a banner shows whether the slug is Available or already in use. Below it, Essential lists a separate live URL for the default Business Profile brand and every additional brand currently assigned to an office. The default brand keeps the original business-level URL; additional brands get their own URL. Copy and share the URL for the brand that customer should see, or open it in a new tab to check it. Several offices can share one brand and therefore one portal URL. The URL determines the brand automatically, so customers are never asked to choose one. Branding and Portal URL each have their own Save. The Customer-facing sections card on the same page controls whether customers can see Paid invoices, Signed quotes, and Asset group information in the portal. Turning one off hides that section for every customer. Action Required items, upcoming services, service history, shared files, and portal users still follow the portal's normal access rules. Under **Customer-facing sections**, **Show Statements** is off by default. Turn it on and click **Save** to show the Statements tab and PDF downloads when customer statements are enabled for your business. Customers can still pay several invoices together in **Invoices** (or **Invoices & Quotes**) with this setting off. ![Customer portal settings](https://3838208579-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Flu1pgNH0CrkCPslG8suQ%2Fuploads%2Fgit-blob-21c3f9864e854d23909f8101913002222e612ff8%2Fsettings-customer-portal.png?alt=media) > **Where to find it:** Settings -> Customer Portal, the Branding and Portal URL cards ## Related guides * [Enable or disable the Customer Portal for all customers](/administration/settings/enable-or-disable-the-customer-portal-for-all-customers.md) * [What your customers see in the Customer Portal](/administration/what-your-customers-see-in-the-customer-portal.md) * [Set up your business profile: name, logo, brand color, contact, address](/administration/settings/set-up-your-business-profile-name-logo-brand-color-contact-address.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) --- # 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/set-your-customer-portal-heading-and-url.md?ask=&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.