> 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-instructors/paid-training-hours.md).

# Paid Training Budget Hours

Learn about paid training hours if this has been setup by your resort.

If your resort has setup a paid training budget you can view your budget and how much is remaining in your profile in the Training tab.

<figure><img src="https://3412627069-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdh5JD0cdH4KWbjolN2Aa%2Fuploads%2F66AUKJLCvJAg9dDk1VSC%2Fsummary.png?alt=media&amp;token=c090b32d-69ba-42d8-949a-aafff62bab76" alt="" width="375"><figcaption></figcaption></figure>

There are three types of training pay: full pay, partial pay, or no pay. In My Timesheets if their has been a partial pay or no pay applied you will be inform on the training paid activity, see image below. The first paid activity is full pay, 2nd paid activity is a partial pay, and 3rd paid activity is no pay applied.

<figure><img src="https://3412627069-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdh5JD0cdH4KWbjolN2Aa%2Fuploads%2FBUhBRlyDjEjOF1SftBx0%2Fmobile%20summary.png?alt=media&amp;token=148f906f-3796-437a-9d30-8cc78261c152" alt="" width="375"><figcaption></figcaption></figure>

If you have any questions about your budget and the way you have used your paid training hours, please get in touch with the leadership team at your snowsports school.


---

# 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-instructors/paid-training-hours.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.
