> For the complete documentation index, see [llms.txt](https://docs.efento.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.efento.io/efento-cloud/advanced/locations.md).

# Locations

Efento Cloud allows you to **organise your locations and sensors** using a flexible, tree-based hierarchy. You can create a structure that fits your needs, whether **geographical** (e.g., Country > State > City > Building), **functional** (e.g., Building Type > City > Location), or any other format that aligns with your Organisation.

## **Adding /** e**diting Locations**

Users with **Administrator** or **Manager** permissions can edit locations in the **Organisation Structure** panel on the left side of the screen. The **location tree** displays all existing locations, starting with the **root location**, which cannot be deleted and defaults to your Organisation’s name. New locations are added as **sub-locations** of an existing location.

To add / edit a location:

1. Click the location’s name.
2. Select the **three dots** on the right to access the menu.
3. Available options:
   * **Rename** – change the location name
   * **Add Sub-location** – create a new location under the selected one
   * **Remove Location** – delete the location
   * **Change Parent Location** – move the location under a different parent

{% hint style="warning" %}
**Important:** To remove a location, you must first remove any **sub-locations** or **assigned sensors**.
{% endhint %}

![](https://3083289504-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOZ7FanYxG2hiIStESXW1%2Fuploads%2FFAt6hWPu8Orol2XCGGcX%2FUnknown%20image?alt=media\&token=b76075bb-a93b-43a1-8dd1-73f338040afb)

## **User Permissions**

When adding a new user or creating an API token, you can select the **specific locations** they will have access to. This ensures that users can only view or modify data relevant to their assigned locations, enhancing **data security** within your Organisation.

Users with **Administrator** or **Manager** permissions can manage these settings in the [Access](https://docs.efento.io/efento-cloud/advanced/editor.md) panel. Properly assigning permissions helps maintain control over your monitoring system while allowing collaboration across teams.


---

# 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://docs.efento.io/efento-cloud/advanced/locations.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.
