> 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/members.md).

# Members

Are your members present?

## Attendance

This is a list of all members that are currently checked in with their checkin timestamp.

## In shift

A list of your members that are checked in and currently have a shift.

## Missing

A list of members that currently have a shift, but are not checked in. This list also shows you their phone number for easy access.

## Location

This page is an overview of all jobs of the selected day. Below these jobs is a list of people who are assigned to the job with indicators if they are checked in or not.

{% hint style="info" %}
If the member is checked in they will have a green checked-in icon, otherwise they have a pink icon.
{% endhint %}

There is a second indication for [time track](/event/accreditation/time-tracking.md) data and a button to start a time track right from this screen. Clicking this button does not leave this page but starts the time track for this user in this job.

{% hint style="info" %}
The time track indicator is another icon with the following values:

* **Grey**: No time track started
* **Yellow**: Tracking right now
* **Blue**: Track is finished, job completed
* **Pink**: Track finished, job not completed
  {% endhint %}

On the top of the page you can select the day you want to visualise, the station and the substation.


---

# 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/members.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.