> For the complete documentation index, see [llms.txt](https://docs.netmap.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.netmap.dev/product-introduction/terminology.md).

# Terminology

| Term          | Meaning                                                                       |
| ------------- | ----------------------------------------------------------------------------- |
| Device        | A tracked network endpoint or infrastructure asset.                           |
| Relationship  | A topology link between devices or groups.                                    |
| Group         | A topology grouping that may include VLAN/subnet metadata.                    |
| VLAN          | Network segmentation metadata stored on topology groups.                      |
| Site          | A physical or logical location for devices.                                   |
| Subnet        | An IPAM network range.                                                        |
| Reservation   | An IP address reservation in IPAM.                                            |
| DHCP lease    | Imported lease data used by IPAM.                                             |
| Observation   | A scheduled discovery finding that must be reviewed before inventory changes. |
| Service check | A monitored TCP/UDP target associated with a device.                          |
| API key       | A revocable secret that authenticates REST calls as its owning user.          |

## Permission Terms

| Term          | Meaning                                                                  |
| ------------- | ------------------------------------------------------------------------ |
| Authenticated | The user or API key is valid.                                            |
| Authorized    | The authenticated user has the role or permission needed for the action. |
| SuperAdmin    | Built-in role with all permissions and administrative access.            |
| Custom role   | Role created by a SuperAdmin through the role-permissions system.        |

## Deployment Terms

| Term              | Meaning                                                                                                    |
| ----------------- | ---------------------------------------------------------------------------------------------------------- |
| All-in-one image  | Docker image that includes frontend, nginx, FastAPI, workers, and syslog service.                          |
| Host networking   | Docker mode where the container uses the host network namespace. Required for MAC discovery through ARP.   |
| Bridge networking | Docker mode with explicit port publishing. Easier to isolate, but ARP discovery does not cross the bridge. |
| WAL               | SQLite write-ahead logging mode, which creates sidecar files that matter for live backups.                 |

## Related Pages

* [Features](/product-introduction/features.md)
* [Architecture](/product-introduction/architecture.md)
* [Glossary](/reference/glossary.md) | SuperAdmin | Built-in administrative role with all permissions. |


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.netmap.dev/product-introduction/terminology.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.