> For the complete documentation index, see [llms.txt](https://support.kea.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.kea.ai/kea-brand-portal-setup/editing-multiple-locations-at-once.md).

# Editing multiple locations at once

Bulk editing in Kea allows users to update settings across multiple locations at once instead of editing each location individually. This helps save time, reduce errors, and ensure consistency across all locations.

Users can select one, multiple, or all locations and apply updates (such as hours, greetings, FAQs, or settings) in a single action. Changes are applied immediately across the selected locations once confirmed.

Follow [this instructional how-to guide](https://app.tango.us/app/workflow/Bulk-Editing-Multiple-Locations-in-your-Kea-Portal-fee32902c2064e74bfb6bd7d06b55b7f) or read the steps below:

#### 1. Access Locations

* Navigate to the **Locations overview** in your Kea portal
* View all locations in one place

#### 2. Open Bulk Edit

* Click the **Modify / Bulk Edit option**
* This opens the bulk editing interface

#### 3. Select Locations

* Choose:
  * Individual locations
  * A group of locations
  * Or **select all locations**

#### 4. Choose What to Update

* Select the fields you want to edit across locations, such as:
  * Business hours
  * Holiday hours
  * AI greetings
  * FAQs
  * Amenities or settings

#### 5. Apply Changes

* Enter updated values
* Apply changes to all selected locations at once


---

# 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://support.kea.ai/kea-brand-portal-setup/editing-multiple-locations-at-once.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.
