> 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/timekeeping/timekeeping-creating-and-associating-paid-activities/timekeeping-creating-and-associating-paid-activities-4.md).

# Unpaid Tasks

If a task shouldn't have a Paid Activity, use the No Paid Activity option (always available at the bottom of the Paid Activity list regardless of the paid activities that have been created for your resort). Drag it over to the right column as needed.

{% hint style="info" %}
Best practice: all tasks should have a paid activity added, even tasks that aren't paid (which can use the No Paid Activity option)
{% endhint %}

On the main Paid Activities page in flaik there is a light yellow box advising how many Tasks and Training Clinic Categories are yet to be assigned. By always using the No Paid Activity for any of these that are unpaid, it will be easy to see when a new item is added into flaik that needs to be associated to a Paid Activity.&#x20;

<figure><img src="https://3412627069-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdh5JD0cdH4KWbjolN2Aa%2Fuploads%2FoBTfXClWY1nivtWNZa46%2Fimage.png?alt=media&amp;token=63e614c3-a4ff-49b6-8706-c4e62e1d3630" alt=""><figcaption></figcaption></figure>

Make sure to save your work by hitting the Associate paid activities button in the bottom right of the association screen.&#x20;

![](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/2043148081163/original/-OjHZfQ0POdUimJVcW-KgzEioF6gIzxF0g.png?1600288259)


---

# 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/timekeeping/timekeeping-creating-and-associating-paid-activities/timekeeping-creating-and-associating-paid-activities-4.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.
