> For the complete documentation index, see [llms.txt](https://knowledgebase.flaik.com/flaik-knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.flaik.com/flaik-knowledge-base/for-administrators/returning-resort-review/staff-management.md). # Staff Management You'll be updating Staff Management throughout the season, but here are the items you should check before people start rolling in. * [ ] **Make sure Staff ID field is filled out with your staff's IP codes (RTP) or nicknames (Siriusware.)** Staff ID is how flaik can sync scheduling data back to your POS - without this, shifts, tasks, and private assignments will not make it back to your POS system. * [ ] **Make sure Payroll ID field is filled out for all your hourly staff.** This should correspond with the identifier your payroll system uses. If this field is missing or incorrect, your staff won't get paid, and everyone will be mad. * [ ] **Wages! Make sure all your hourly staff have their wages specified in their profiles.** Even if your flaik site is configured to send your payroll system job codes instead of dollar values, it's still useful to update your staff's wages so that gross pay calculations and the Timekeeping dashboards work as intended. * [ ] **Update the fields that are commonly used in filters.** All of these fields are really handy for assigning lessons in Scheduling. **Tip:** the [bulk update tool](/flaik-knowledge-base/for-administrators/first-season-guide/updating-staff-via-bulk-update-from-an-external-file-or-data-source.md) is your friend, here. * [ ] Priority rank * [ ] Max teachable levels * [ ] Staff groups (re-sets each season) and staff tags (carried over) --- # 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://knowledgebase.flaik.com/flaik-knowledge-base/for-administrators/returning-resort-review/staff-management.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.