> For the complete documentation index, see [llms.txt](https://docs.bossithq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bossithq.com/venue-devices.md).
# Venue Devices
The devices page serves as an inventory system for your venue's hardware. It allows you to view, add, and manage the equipment connected to your network, such as tills and kiosks.
This defines the device selection options upon initial log in. This also defines how each device is named across reports that are related to devices.
## Accessing Venue Devices
To manage the devices, go to the [**Admin Portal**](https://admin.gobossit.com/) then navigate to **Venue > Devices.**
## Adding a Venue Device
Click Add device and fill in the details:
* **Device Name** – Enter a name that staff can easily identify, such as Till 1 , Kiosk 1 or Pizza Station.
* **Serial Number** – Enter the device's unique serial number to identify the specific piece of hardware.(optional)
* **Active** – Enable this option to allow the device to connect to the system and process orders. If the device is inactive, it will not be able to operate.
Once saved, the device will be linked to your venue and available for use.
## Activating or Deactivating a Venue Device
Use the tick box in the **Active?** column to activate or deactivate venue devices.
## Deleting a Venue Device
Select the tick box next to one or more devices in the list, then click the **Delete** button at the top to remove them from your system.
{% hint style="danger" %}
We do not recommend deleting devices as this may affect historical data in reports linked to the device. **We recommend deactivating the device instead.**
{% endhint %}
---
# 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.bossithq.com/venue-devices.md?ask=&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.
