> 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/benutzer-bearbeiten.md).

# Edit users

### Time tracking settings

#### Functions

For a user to be able to record time, at least one role must be assigned to them, because each time entry documents a user's activity in their role.

You can use the shortcuts above the list to assign either all or no role. Since a user cannot be assigned no role, the first role is selected here.

If there are no roles here yet, first create the Agenturverwaltung price list.

This explains why and how to do it:

{% content-ref url="/pages/c6283a7d4a2931cd4d6b1a6beccbb5824c253dd4" %}
[The price list concept](https://wiki.dieagenturverwaltung.de/die-agenturverwaltung-en/projektverwaltung-1/etats/preisliste.md)
{% endcontent-ref %}

#### Activities

A user can — but does not have to — be assigned tasks for regularly recurring activities. They can then select and use these tasks in their time entries.&#x20;

Using the shortcuts above the list, all or no task can be assigned in one step.

In general, the use of tasks is optional.

What tasks are in detail, and where they are created, is explained here:

{% content-ref url="/pages/42834772b8b095b50b1bb44f01a75cc43d410262" %}
[Activities](https://wiki.dieagenturverwaltung.de/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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://wiki.dieagenturverwaltung.de/die-agenturverwaltung-en/einstellungen-1/benutzerverwaltung/benutzer/benutzer-bearbeiten.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.
