> 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/flaik-admin-settings-setup/for-sups-managers/ability-levels-and-disciplines.md).

# Ability Levels & Disciplines

Are you interested in how flaik determines which ability level to display when a guest has multiple levels from different disciplines and/or they have differing ability levels in the POS and from report cards?

#### Summary

* The discipline is chosen first.
* Within that discipline, a staff-verified level is shown if it exists;
* Otherwise the point-of-sale level is used.

## Details

#### How a guest's ability level is chosen for display

When a guest has multiple recorded ability levels — across different disciplines (e.g. ski vs. snowboard) and from different sources (verified by staff vs. set at point-of-sale) — the system follows a clear order to decide which single level to show.

#### Step 1: Which discipline?

* If the screen in flaik is tied to a specific discipline (for example, a lesson task that is a ski lesson), the system shows the guest's level for that discipline.
* It does not pull in a level from a different discipline.

If no discipline is specified (for example, a general guest summary), the system picks one for you:

* It prefers a discipline where the guest has a verified level.
* Among the options, it picks the one with the highest ability level.

#### Step 2: Verified or point-of-sale? Once the discipline is decided, within that discipline:

* If a verified level exists, that is shown (and gets the "verified" badge).
* If there is no verified level, the point-of-sale (POS) level is shown as a fallback.

#### What this means in practice

* Verified does not override discipline. If you're looking at a ski task and the guest only has a verified snowboard level, you'll see their ski level (verified or POS) — not the snowboard one.
* Verified beats POS — but only within the same discipline. A verified ski level wins over a POS ski level. It does not win over a different discipline's level.
* The verified badge only appears when the level actually being shown is the verified one.
* Cross-discipline preference for verified only kicks in on screens that don't specify a discipline — therefore, a discipline with a verified level is favoured over one with only a POS level.


---

# 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://knowledgebase.flaik.com/flaik-knowledge-base/flaik-admin-settings-setup/for-sups-managers/ability-levels-and-disciplines.md?ask=<question>&goal=<user_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.
