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

# User groups

## What are user groups?

User groups define permissions: Who is allowed to edit jobs? Who can view which reports? Who is allowed to grant permissions to other users?

A user can belong to multiple user groups.

## Possible application scenarios<br>

#### User group "Time tracking"

...

#### User group "Accounting"

#### ...

#### User group "Project management"

...

#### User group "Tasks and Address Book"

...

## Administrators

If a user belongs to the "Administrator" group, they thereby have full access to all functions and data of the system.

Administrators can also grant administrator rights to other users.

Administrators can also log in to the system in the role of another user. This is done via "Settings > Users", then call up the corresponding user and click "Log in as this user" there.

{% hint style="info" %}
**Tip**: This function can be helpful when setting up new user groups and wanting to test what a user of that group then has access to
{% endhint %}

####


---

# 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/benutzergruppen.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.