> 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/access-points.md).

# Access Points

**Access Points** lists the wireless access points your devices have connected through. The system discovers them automatically — devices report which access point they used, and it appears here.

This screen matters for two reasons: it is how you assign access points to sites, and it is where you plot them on floorplans so location can be shown visually.

## Before you start

Access points appear on their own as devices connect through them. You do not add them manually.

## Screen layout

{% hint style="info" %}
Screenshot needed: Access Points at the standard viewport, with a populated table showing both plotted and unplotted access points
{% endhint %}

Two figures at the top:

| Card                      | What it shows                                |
| ------------------------- | -------------------------------------------- |
| **Total APs**             | How many access points have been discovered  |
| **Plotted on Floorplans** | How many have been positioned on a floorplan |

The gap between those two numbers is your outstanding setup work.

Below that, a table:

| Column          | What it shows                                                                 |
| --------------- | ----------------------------------------------------------------------------- |
| **Name**        | The access point's name. One that has not reported a name reads **(Unnamed)** |
| **BSSID**       | Its unique wireless identifier                                                |
| **Site**        | The site it is assigned to. An em dash means it is unassigned                 |
| **Plot Status** | **Plotted** or **Unplotted**                                                  |
| **Last Seen**   | When a device last connected through it                                       |
| **Discovered**  | When it first appeared                                                        |

## Controls

| Control                           | What it does                                                                                             |
| --------------------------------- | -------------------------------------------------------------------------------------------------------- |
| Search box                        | Searches the access point list                                                                           |
| Column headings                   | Sort by **Name**, **BSSID**, **Plot Status**, **Last Seen** or **Discovered**. **Site** cannot be sorted |
| Row checkboxes and **Select all** | Select access points                                                                                     |
| Page size                         | 10, 25, 50 or 100 rows. Opens on 25                                                                      |

The group selector in the header narrows this screen.

## Why plotting matters

Until an access point is plotted on a floorplan, the product can tell you a device was near it but cannot show you where that is.

**Last Seen** on a battery or device points at a BSSID. On its own, that is an identifier. Once the access point is named, assigned to a site and plotted, the same information becomes "third floor, east wing" — which is what someone looking for a missing device actually needs.

Work through **Unplotted** access points in **Last Seen** order, newest first. Those are the ones carrying real traffic and therefore the ones whose location will be asked about.

## Reading the list

* **An unnamed access point still works.** The name comes from the access point itself; a missing one means it has not reported its name, not that anything is wrong.
* **An old Last Seen date** means no device has connected through it recently. Either it is in a part of the building nobody visits, or it has been decommissioned and can be ignored.
* **Discovered tells you when it first appeared**, which is useful for spotting infrastructure added without anyone telling you.

## Related

* [Sites](/amie-advanced/using-the-platform/sites.md) — the physical locations access points are assigned to
* [Battery details](/amie-advanced/using-the-platform/battery-details.md) — shows the last access point a battery connected through
* [Performance](/amie-advanced/using-the-platform/performance.md) — call quality broken down by access point


---

# 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/access-points.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.