> 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/admin-settings-back-at-it-again.md).

# Admin settings (back at it again)

The fun continues! Roll up your sleeves, because we're going under the hood for this one. This section focuses on all the elements of flaik that define how the core features will work. Most of these items will be difficult to adjust once you start using them, so now is the best time to make your changes. 

**Core Functionality**

* [ ] **Shifts & tasks (Scheduling)**
  * [ ] Remove any shifts or tasks that were not used last season. 
  * [ ] Add new shifts & tasks as needed.
  * [ ] Refine existing setup (naming conventions, color swatches.) 
  * [ ] Review and make any necessary edits to Task type (Group, Block/Hold, Non Teaching, etc.) before the tasks are used. The Task type influences how several instructor metrics calculate and will impact any Metric rule you have set up. 

{% hint style="danger" %}
**We've made some changes for 2025!**\
\
If you use flaik Tags, you'll want to check the "guest view" settings for each task. We've added a toggle for Relive Your Lesson so you can fine-tune which classes send a RYL link to your guests. Make sure to turn it on for the tasks where RYL is desired. 
{% endhint %}

{% hint style="warning" %}
**There are several back-end sync settings accessible only by flaik staff.** If you are making adjustments to the "Sync with POS?" settings within your shifts and tasks, please reach out to <resortsupport@flaik.com> to ensure that the back-end settings align with your intended use.&#x20;
{% endhint %}

#### **Checklist for creating new tasks**

* [ ] If the new task should generate pay, associate it to a paid activity
* [ ] If the new task is for a lesson, make sure it is mapped to a POS product
* [ ] If you use additional report cards (instead of the default set,) make sure this task is associated to the right report card
* [ ] If the new task is a teaching task, make sure it is associated to a scanning mode button (if you will be creating classes with it via scanning.)&#x20;
* [ ] Associate the new task to the relevant lineup within the Lineups feature
* [ ] If using flaik Sales, make sure the new task has the appropriate approval rules

#### **Paid activities (Timekeeping)**

* [ ] Remove any paid activities that were not used last season.

* [ ] Add new paid activities as needed.

* [ ] Refine existing setup (naming conventions, check that color swatches align with your shifts and tasks.)&#x20;

* [ ] Make sure every paid task has the correct paid activity associated.

* [ ] Review last years Business Structures and Pay and/or Job Codes and add any new structures or codes that you've received from your HR/Payroll team.&#x20;

* [ ] **Incentives (Timekeeping)**
  * [ ] Staff incentives - Check paid activity associations, dollar values, and update as needed.
  * [ ] Metric rules - Update metric rules to align with upcoming pay bump strategy (if changing.)
  * [ ] Head counts - Check head count rules, dollar values, and update as needed.


---

# 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/admin-settings-back-at-it-again.md?ask=<question>&goal=<endgoal>
```

`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.