> For the complete documentation index, see [llms.txt](https://wiki.roaddirect.co.nz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.roaddirect.co.nz/eboard/calendar/staff-picker.md). # Staff picker The staff picker displays a list of users who are not deleted, not disabled, recorded as "Available for TTM" and have "Completed Internal Health & Safety". The list is grouped into "Permanent Staff", then "Casual/Temporary Staff" and finally "Not Available". The "Permanent" and "Casual/Temporary" staff groups are based on the "Casual/Temporary" checkbox in the "Contractual Details" section of the User dialog. The "Not Available" section is based on users who have leave booked as "All Day" on the day which the picker is used. Staff who have notes recorded against them will display a black i icon next to their name, which can be hovered to see the notes. Staff who have already been assigned to a job for a given day will display a black tick next to their name. Staff who have leave/unavailability recorded against them for a given day will display a yellow exclamation mark icon next to their name, which can be hovered to see additional information. --- # 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://wiki.roaddirect.co.nz/eboard/calendar/staff-picker.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.