> 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/admin-settings-product-settings/bookings-overview/bookings-admin-settings/approval-rules.md).
# Approval Rules
The configuration of Aprroval Rules dictate the behavior of Supervisor Approval and the underlying rules of when an Instructor is allowed to book lessons. These rules get attached to Tasks, so that a scheduled task on an Instructors schedule has specific behaviors. There are default core rules for use and you can define custom rules to empower instructors autonomy for booking lessons without inundating your capacity or abiility to adjust schedules.
### Default rules
We have created 3 default rules as we know there will be some tasks you never wants to be booked over, some you will always approve and some that will always need approval. You cannot edit or delete these rules.
* Always approve
* Behavior: Allows an Instructor to book a private request lesson over this conflicting task.
* Always require supervisor approval
* Behavior: Allows an Instructor to book a private request lesson over this conflicting task, but the booking is sent to Supervisor for review prior to the guest, allowing the Supervisor to approve or reject the booking.
* *DEFAULT: This rule is default for all task conflicts unless otherwise set in Task-Override Rules.*
* Always block
* Behavior: Prevents an Instructor to book a private request lesson over this conflicting task.
{% hint style="info" %}
Always block may be relevant for multi-day programs that you want the same instructor each day. Attaching always block to program tasks would prevent instructors from booking over this task.
{% endhint %}
### Custom rules
Here you can create up to 5 custom time-based rules to suit your operations. You can then assign these rules to tasks in Task-override rules. For each rule you can select how far out from a lesson you’d like to block lesson, and how far out you’d like to auto approve them. If these selections don’t match, we’ll require supervisor approval for the period in between.
{% hint style="info" %}
We encourage the use of custom rules. These can protect school capacity, while still allowing for upsells when schedule adjustments can be suitable.
{% endhint %}
## To start defining approval rules:
Navigate to Admin Settings -> Product Settings -> flaik sales -> Approval rules
## To edit approval rules:
On the right side, click Edit
### Default rules
These rules are fixed and cannot be edited.
### Custom rules
Custom rules leverage all the default rule behaviors with timeframes.
1. Define a Block period by a number at a interval of Hours, Days, or Weeks:
2. Define a Auto Approve period by a number at a interval of Hours, Days, or Weeks:
3. The difference between Block and Auto Approve will require Supervisor Approval.
Click "Add approval rule" to create new rule or changes the values of existing rule:
Approval rules - Settings Page - Custom Rules
## To finish approval rules:
Click Save if you want to continue
---
# 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/admin-settings-product-settings/bookings-overview/bookings-admin-settings/approval-rules.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.
