> For the complete documentation index, see [llms.txt](https://wiki.dieagenturverwaltung.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.dieagenturverwaltung.de/die-agenturverwaltung-en/einstellungen-1/benutzerverwaltung/benutzer/time-tracking-settings.md).

# Time tracking settings

## Mandatory: assign functions

In order for a user to record time, at least one function (e.g. Junior consulting, graphic design, frontend development) must be assigned to them as mandatory.

From this function, the corresponding hourly rate used to bill the time in the context of the job is derived.

**Without an assigned function, the user cannot record time.**

A person can also be assigned multiple functions.&#x20;

{% hint style="info" %}
**Example**\
In a small design studio the boss records time both in the function "Creative Direction" (EUR 250 per h) and in the function "Image Editing" (EUR 85 per h) - i.e. in roles behind which different billing hourly rates are stored.
{% endhint %}

If a user has been assigned multiple functions, the topmost function in the list is automatically preselected for them when recording job work times. However, they can change the preselected function.

<figure><img src="/files/03e14c83593e9cfe3f669de8c962db06a447de33" alt=""><figcaption></figcaption></figure>

#### More on the topic:

{% content-ref url="/pages/96240e3033c741dbab2cea1007326612d09d41a7" %}
[The standard price list of agency services](/die-agenturverwaltung-en/onboarding/initial-financial-settings/funktionen.md)
{% endcontent-ref %}

{% content-ref url="/pages/6ad60844b9e6dcb9e9361a7bd64c4a76331d1c90" %}
[Functions](/die-agenturverwaltung-en/einstellungen-1/zeiterfassung/funktionen.md)
{% endcontent-ref %}

## Optional: activities

Activities are optional; they can describe certain recurring tasks. This way time tracking can be simplified because no manual notes need to be added to an entry and you can also select times based on these activities.

{% hint style="info" %}
**Example: activities for author corrections**\
If two activities "Author correction 1" and "Author correction 2" are created, it can be analyzed within a customer, for example, how much time is spent on repeated corrections initiated by the customer. These time expenditures can then also be compared between customers.
{% endhint %}

{% hint style="info" %}
**Examples of activities as recurring events**\
\- Internal meeting\
\- Call with customer\
\- Monday round\
\- Travel
{% endhint %}

<figure><img src="/files/3573656e604108319b64a245cb9a1b801f26e740" alt=""><figcaption></figcaption></figure>

#### More on the topic:

{% content-ref url="/pages/42834772b8b095b50b1bb44f01a75cc43d410262" %}
[Activities](/die-agenturverwaltung-en/einstellungen-1/zeiterfassung/taetigkeiten.md)
{% endcontent-ref %}


---

# 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://wiki.dieagenturverwaltung.de/die-agenturverwaltung-en/einstellungen-1/benutzerverwaltung/benutzer/time-tracking-settings.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.
