> 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/accreditation/attendance/currently-checked-in.md). # Currently checked in Everybody who is at your event Here you can find a complete list of everybody who is currently checked in at your event, members or lists. You can see their check in and check out timestamps. You are also presented with a graph to visually show you what happened and when.

This graph shows you how many people were checked in, check in and check out actions per time duration. The red spike down was the "automatically check out everybody at a certain hour" action performed by the servers.

On top of the page there is a blue button that allows you to change the "current time" to another timestamp. This is a great way to see who was checked in at a certain moment in the past. A download button is clickable on top of the page. This will email you a list of the current table (all pages). --- # 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/accreditation/attendance/currently-checked-in.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.