> 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/flows.md). # Flows A flow is an action that this kiosk will do when it scans a wristband or a ticket. You can set the flow per kiosk, and after a maximum of 30 seconds, the kiosk will retrieve that new flow and start executing it. This allows you to change the behavior of our devices without the need to be near them. You can create as many flows as you like. ## Actions A flow is made up of one or more **actions**. When someone scans their wristband or ticket, the kiosk runs through the actions in order. ### Check in / out Check someone in or out of the event. You can configure what happens if the person has no visiting day, and which lists or members are allowed. ### Time tracking Start or stop a time track for the scanned person. You can configure: * **Allow members** — let members start and stop time tracks. You can limit this to specific work stations or substations, or allow all of them. You can also choose whether members without an upcoming shift can still start a time track. * **Allow list visitors** — let list visitors (accreditation attendees) start and stop time tracks. You can limit this to specific lists, or allow all of them. If a member already has a time track running, the kiosk will show a stop button instead of a start button. ### Sign documents Prompt the person to sign a document before continuing. --- # 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.eventication.com/event/hardware/kiosks/flows.md?ask=&goal= ``` `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.