> For the complete documentation index, see [llms.txt](https://docs.eventication.com/event/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eventication.com/event/hardware/kiosks.md).

# Kiosks

Unmanned actions.

Our kiosks are a kind of hardware that does not need a person managing it. Use these devices to have your crew perform actions themselves.

## List

This page displays a list of the rented devices. If you have currently rented devices the top of the page will show a map followed by the list. This page will auto refresh depending on the heartbeats the devices send to Eventication every 30 seconds.

This will update:

* The online or offline status of the device
* If the Eventication app is at the foreground or not
* The current [flow](https://docs.eventication.com/event/hardware/kiosks/flows.md) that is attached to this kiosk

## Usage

Here you can find an overview of the usage of the kiosks. You will see a table that has the different kiosks in the rows and the different event days in the columns. Per day per kiosk you get the number of actions it has done. Next to each kiosk name, a badge shows whether the kiosk is currently online or offline. At the right side of the page you can find the total per kiosk.

{% hint style="info" %}
The usage numbers are not live: the top of the page shows when they were last refreshed.
{% endhint %}

## Flows

Every kiosk needs a [flow](https://docs.eventication.com/event/hardware/kiosks/flows.md) to allow it do work.

{% hint style="info" %}
The kiosks check their current flow once every 30 seconds. So if you change a flow, the kiosk will update itself after maximum 30 seconds.
{% endhint %}

## Ordering kiosks

To order these devices, please go to the [Hardware](https://docs.eventication.com/event/hardware/scan-app-devices.md) section in your event and click on [orders](https://docs.eventication.com/event/hardware/orders.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.eventication.com/event/hardware/kiosks.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.
