> 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-paid-activity-groups.md).

# Paid Activity Categories

**Paid Activity Categories** are used to organize your Paid Activities. <br>

**Paid Activity Categories** do not necessarily need to correlate to your Scheduling Product Categories or Class Types.&#x20;

Paid Activity Categories  are designed to help navigate between your different Paid Activities when Supervisors or Payroll Administrators need to add Paid Activities to a Timesheet manually, when associating Paid Activities to Scheduling Products, Training Clinic Types, and Class Types in Admin Settings.&#x20;

Change the settings for Paid Activity Categories  by navigating to the Admin Settings - > Products Settings - > Timekeeping - > Paid Activity Categories .

In Edit mode, you can:

* Add a Paid Activity Categories&#x20;
* Delete a Paid Activity Categories&#x20;
* Modify a Paid Activity Categories 's name and color

We suggest keeping things simple, but you can create as many Paid Activity Categories  as you'd like.

Some examples of Paid Activity Categories are:

* Classes
* Clinics
* Non-Teaching Activities
* Privates.&#x20;

You may wish to further separate the "Classes" Paid Activity Group into:&#x20;

* Adults&#x20;
* Kids
* Ski
* Snowboard

<figure><img src="https://3412627069-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdh5JD0cdH4KWbjolN2Aa%2Fuploads%2FEt1y6FFpEuzISByZuFQw%2Fimage.png?alt=media&amp;token=5aa2ada0-2cef-47cb-9525-f866ef9a0dde" alt=""><figcaption></figcaption></figure>


---

# 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-paid-activity-groups.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.
