> For the complete documentation index, see [llms.txt](https://docs.ngsurvey.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ngsurvey.com/form-management/form-designer/form-settings/kiosk.md).

# Kiosk

## 💻 What is kiosk mode ?

The kiosk mode options allow you to setup your survey to run under browsers having their kiosk mode enabled in environments like fairs or museums where the survey will have an unknown number of respondents that will take the survey and drop out at any time.

## ⏳ Inactivity timer

Using the inactivity timer you can set your survey to automatically abort the current respondent session if the respondent didn't do anything on your survey for a number of minutes. 

You may either silently end the session or you may also setup a warning dialog before the sessions gets automatically ended.  

![](https://1025048312-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M8fLhS0bmfBRyq0HdUm%2F-MOAoChG2JYUDrnR3kif%2F-MOAugmIa_G_2DfdK7Hh%2Fimage.png?alt=media\&token=59a382e0-b775-45a9-a05e-eeee529eaf0a)

## 🔅 Inactivity properties 

* **`Inactivity timeout`** time before the survey will reset.
* **`Display warning before being inactive`** show a warning dialog time before the inactivity time out ends.
* **`Inactivity action`** reload the form, keep warning open will keep the warning dialog open with a restart button, redirection URL allows you to set an URL that will be called once the respondent times out.
* **`Disable inactivity timer on thank you`** stop counting the inactivity once the thank you page is displayed.
* **`Save progress on inactif`** will save the respondent progress. Note that it doesnt trigger "final submit", answers will be saved in an unfinished state as the respondent didn't finish the survey.


---

# 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.ngsurvey.com/form-management/form-designer/form-settings/kiosk.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.