> 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/using-the-platform/sites.md).

# Sites

**Sites** are the physical locations where your devices are used — a hospital, a warehouse, a campus building. Each site records where it is, who to contact about it, and how much equipment it holds.

Sites give your access points and devices a physical home, so a problem on a screen can be traced to somewhere a person can walk to.

## Before you start

Adding a site requires the **create site** permission. Deleting one requires the **delete site** permission. Where you lack a permission, the control is shown but grayed out.

## Screen layout

{% hint style="info" %}
Screenshot needed: Sites at the standard viewport, with two or three site cards showing addresses, contacts and non-zero counts
{% endhint %}

Each site is a card. The card shows:

| Field             | What it shows                                                     |
| ----------------- | ----------------------------------------------------------------- |
| Site name         | The name you gave it. An unnamed site reads **(Unnamed Site)**    |
| Address           | Where it is. With none recorded, it reads "No address on file"    |
| Contact           | Name and phone. With none recorded, it reads "No contact on file" |
| **Floors**        | How many floors you recorded                                      |
| **Access Points** | How many access points are assigned to this site                  |
| **Devices**       | How many devices are at this site                                 |

## Adding a site

{% stepper %}
{% step %}

#### Select **Add Site**

The button is at the top right. It is grayed out without the **create site** permission.
{% endstep %}

{% step %}

#### Fill in the details

**Site Name**, **Address** and **Number of Floors** are required. **Contact Person** and **Phone Number** are optional.

Give the site the name people actually use for the building, not a formal address — it appears throughout the product and needs to be recognizable at a glance.
{% endstep %}

{% step %}

#### Save

The site appears immediately as a new card. If it cannot be saved you are told so and the details you entered are kept.
{% endstep %}
{% endstepper %}

Floors matter because they determine how many floorplans a site can hold. Set it to the number of floors you intend to map, not necessarily every floor in the building.

## Deleting a site

Select **Delete** on the site's card. This requires the **delete site** permission.

{% hint style="warning" %}
Deleting a site removes the location record. Consider what is assigned to it first — the **Access Points** and **Devices** counts on the card tell you how much is attached.
{% endhint %}

## Assigning access points to a site

Access points are assigned from the [Access Points](/amie-advanced/using-the-platform/access-points.md) screen, not from here. The **Access Points** count on a site card reflects those assignments.

## Reading the counts

* **A site with zero access points cannot show anything useful on a floorplan.** The count is the quickest check that a site has been set up properly.
* **A site with zero devices** either has nothing deployed yet, or has devices that have not been seen at any of its access points.

## Related

* [Access Points](/amie-advanced/using-the-platform/access-points.md) — the wireless infrastructure assigned to your sites
* [Battery details](/amie-advanced/using-the-platform/battery-details.md) — uses the last access point a battery connected through to tell you roughly where it is


---

# 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/using-the-platform/sites.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.