> 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/first-season-guide/quick-ski-school-setup.md). # Quick Ski School Setup ### Welcome to flaik! We've set up your site and now you can log in. Before you access the main part of the site, you'll need to run through a quick setup process to make sure the critical settings are set. In this article we'll explain these settings in more detail: 1. The Basic Details 2. Employment Types 3. Job Titles 4. Staff Groups To access the clickthrough, click the "Let's get you set up" button. ![](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/2043241209836/original/kkLljjk8sPE2XydDRYZHdJac2DcridTDZQ.png?1626900696) ### 1. The Basic Details In this section, we'll ask you to let us know some of the basics about your resort. * "Resort Name" is how you would like your School's name to be displayed to staff and guests that interact with the flaik system. * This is included in email communications and is visible to instructors and guests. * Often this will be the name of the Snow Sports Department rather than the resort as a whole. The choice is up to you. * "Address" describes the best way for us to reach your school. This isn't displayed in many areas of the site, but if we need to mail you anything, this is what we'll reference first. * Please provide a physical address that could be used for FedEx/UPS and any drop-off information. * Estimated Season Start Date * This will not prevent you from using the features of the site, but it will trigger several cues as you move through the setup process. * You'll see a green flag in the Schedule to identify the day specified here. * Estimated season end date * Don't worry, this won't lock you out of the site if operations continue longer, but it will prompt you to go through the season wrap-up processes. * Nominated flaik Support contact * This should be the person who will be the main contact for the flaik Customer Success team regarding setup and any required support. * This contact will also be displayed to staff members if they have questions about flaik. ![](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/2043241210389/original/ew1X7hHxqCtAjnZfztmG4Krt59s93N72tw.png?1626900832) ### 2. Employment Types * Employment Types refer to the level of commitment a staff member agrees to in their contract. * This is most visible in the Hiring process but also has implications in other areas of the site like Availability and Scheduling. * The Employment Type will be applied to each staff member's employment record in their profile. ![](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/2043241210526/original/aTEBMrYxP8uMV7_WM09FwsTtstl_J-m0KA.png?1626900863) ### 3. Job Titles * Job Titles refer to the various roles you have available in your school. * It is often helpful to align your Job Titles with the levels of permission you would like to grant within the flaik system. ![](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/2043241210700/original/aeVm5Kq7tYfm62V6OKVN2Zr9Gqx5che0WA.png?1626900894) ### 4. Staff Groups * Staff groups are customizable fields that are used to filter in various areas of the site. * These are completely customizable, but generally, we recommend grouping staff using the segmentation you already use within your school. These are often called "Pods", "Areas" or "Bases". * If you have primary locations that staff report to, i.e.different bases, or you separate your staff into Kids vs. Adult instructors, then that's a good place to start with staff groups. ![](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/2043241210762/original/a5lqahAhrS62YNbHzCUvZY7CeUv-rGiaMg.png?1626900907) ### You did it! If you think you have more to add or haven't decided fully on these options, don't worry, you can always edit these selections in "Admin Settings" later on. --- # 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/first-season-guide/quick-ski-school-setup.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.