> 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/planning/stations/substations/jobs/people-shifts.md). # People / shifts This page shows you the people who are in this job. A person in a job is called a shift. If your event has [Double confirmation](/event/planning/settings/members/double-confirmation.md) enabled, these statuses will be shown per person. ## Add more people Click the button to search for other people to put in this job. This will open up a new page with a search bar and some buttons. If you just want to see everybody who is available on the day of this job, click "**Search**". Adding people to this just can be done by clicking the checkmark box next to their name(s) -> and clicking the button "**Add jobs to selected members**". The tags button allows you to search only people with a certain [tag](/event/general/tags.md). The groups button allows you to search only people of a certain [group](/event/planning/groups.md). ## Settings The settings button can be used to customise the search result list. **Show overlaps?**: Show people who have an overlap with this job (doing another job)? **Show tags?**: Show the tags in the results? **Show comment count?**: Show the number of comments this person has? **Show people who don't have this as preference?**: Only available for shiftpickers [Kappa](/event/planning/settings/members/shiftpicker.md#kappa) or [Sigma](/event/planning/settings/members/shiftpicker.md#sigma). **Show shiftpicker message?**: If you allow people to write a [shiftpicker message](/event/planning/settings/members/shiftpicker.md), display it in the results? **Show number of shifts on this day?**: Show the total number of shifts this person already has on this day? **Show current work time on this day?**: Show the total time this person already has to work on this day. **Order**: How would you like to order the results? The available options are: * **firstname (ascending)**: Sort results alphabetically by first name, A to Z. * **firstname (descending)**: Sort results alphabetically by first name, Z to A. * **last name (ascending)**: Sort results alphabetically by last name, A to Z. * **last name (descending)**: Sort results alphabetically by last name, Z to A. * **number of shifts this day (ascending)**: Sort by the number of shifts a person already has on this day, fewest first. Useful to spread the workload evenly. * **number of shifts this day (descending)**: Sort by the number of shifts a person already has on this day, most first. * **total work time this day (ascending)**: Sort by the total hours a person is already scheduled to work on this day, least first. Useful to find people with the most time still available. * **total work time this day (descending)**: Sort by the total hours a person is already scheduled to work on this day, most first. * **with this as preference**: Show people who have listed this job or station as their preference first. Only available when the shiftpicker is set to [Kappa](/event/planning/settings/members/shiftpicker.md#kappa) or [Sigma](/event/planning/settings/members/shiftpicker.md#sigma) mode. These settings might help your event designate the right jobs to the right people. --- # 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/planning/stations/substations/jobs/people-shifts.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.