> For the complete documentation index, see [llms.txt](https://docs.spectralink.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spectralink.net/amie-advanced/introduction/how-your-space-is-organized.md).

# How your Space is organized

Everything in AMIE belongs to your **Space**, and within it to a **group**. Physical places where handsets are used are recorded as **sites**. Understanding those two ideas makes the rest of the console make sense.

## Groups

Groups organize your handsets and users into a tree. The top of the tree is your whole Space; beneath it you can create groups for whatever structure suits you — regions, buildings, departments, shifts — nested as deeply as you need.

Every device and every user belongs to exactly one group.

Groups are what the **group selector** in the header of every screen works on. Choose a group and most screens narrow to that group and everything beneath it. Choose the top of the tree and you see the whole Space.

{% hint style="info" %}
Not every screen follows the group selector. Where one does not, its page in this guide says so.
{% endhint %}

Groups are created and managed under **Settings** on the **Groups** tab; creating one requires the **Admin** or **Owner** role — see [Planning your groups](/amie-advanced/planning-and-installation/planning-your-groups.md#create-a-group).

## Sites

A site is a physical place: a hospital, a warehouse, a campus building. It has an address, a contact, and a number of floors. Access points are assigned to sites, so the [Access Points](/amie-advanced/using-the-platform/access-points.md) screen shows which site each access point belongs to, and the [Sites](/amie-advanced/using-the-platform/sites.md) screen counts the handsets last seen at each site's access points.

Sites are independent of the group tree. A group is a way of dividing up your fleet; a site is somewhere your fleet goes. A single site can hold handsets from several groups, and a single group can span several sites.

Sites are created and managed on the **Sites** screen. See [Sites](/amie-advanced/using-the-platform/sites.md).

## If you are moving from the previous AMIE console

The previous console organized your deployment as an **Account** containing **Organizations**, each containing **Locations**. AMIE replaces that fixed three-level structure with the group tree described above.

When your deployment is migrated:

| In the previous console                                  | In AMIE                                                                      |
| -------------------------------------------------------- | ---------------------------------------------------------------------------- |
| Your Account                                             | Your Space, at the top of the group tree                                     |
| An Organization                                          | A group directly beneath the top                                             |
| A Location                                               | A subgroup beneath its Organization's group, and a site carrying its address |
| A user assigned to one Location                          | A member of that Location's group                                            |
| A user assigned to several Locations in one Organization | A member of the Organization's group                                         |
| A user assigned across several Organizations             | A member of the top group — the top of the tree                              |
| A device in a Location                                   | A member of that Location's group                                            |
| A device with no Location                                | A member of the top group — the top of the tree                              |

Your handsets, users, licenses and batteries are all present; they are arranged differently.

## Planning your structure

How to shape your groups and sites for a new deployment — and what to change after a migration — is covered in [Planning and Deployment](/amie-advanced/planning-and-installation.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://docs.spectralink.net/amie-advanced/introduction/how-your-space-is-organized.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.