> 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/berichte-1/team-capacities.md).

# Team capacities

{% embed url="<https://youtu.be/43YMrswSILE>" %}

In this view, I can see the scheduled monthly, weekly, or daily hours of all employees or of a specific team or employees of a certain role (e.g. motion designer and copywriter) across all jobs.

{% hint style="info" %}
The examples here refer to weekly planning. If you want to plan capacities in your company **daily** or **monthly** want to plan, contact our support and we'll switch the module for you:\
<info@dieagenturverwaltung.de>
{% endhint %}

Here it is easy to see which colleagues still have time available and which are overbooked.\
The gray arrows can also be used to page further into the future and back.

<figure><img src="https://4063991107-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-La4YdZ1Gw5iHapqZfIo%2Fuploads%2FRfdDAf9HRREWdE4zkgke%2FBildschirmfoto%202022-12-29%20um%2018.06.43.png?alt=media&amp;token=b0867241-461b-4f52-b183-0aec455f2b5e" alt=""><figcaption></figcaption></figure>

If I click one of the colored boxes, a dialog opens that shows me how the total weekly hours for a specific person are made up.

In this example, we clicked the red field (Rüdiger in week 52) and can see for which jobs Rüdiger is scheduled this week and, if necessary, adjust these values directly:

<figure><img src="https://4063991107-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-La4YdZ1Gw5iHapqZfIo%2Fuploads%2FiNAtkfJ0sMbKLjG36IjY%2FBildschirmfoto%202022-12-29%20um%2018.07.07.png?alt=media&amp;token=419307bb-30a6-4e50-b021-ad336f40c1ec" alt=""><figcaption></figcaption></figure>

## More views of the same data

### Dashboard tile

<figure><img src="https://4063991107-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-La4YdZ1Gw5iHapqZfIo%2Fuploads%2Fl3Ag4f6MOUN8IkxWsT5w%2FBildschirmfoto%202022-12-29%20um%2018.23.25.png?alt=media&amp;token=be11c146-9fd7-4b0f-867f-67053aecf24e" alt=""><figcaption><p>Example of a user scheduled on two jobs</p></figcaption></figure>

### Plan capacities for the job

{% content-ref url="/pages/28326a76cf4973d24509e7845dda1604b0ebfcb4" %}
[Capacity planning](/die-agenturverwaltung-en/projektverwaltung-1/projekte/planning/capacity-planning.md)
{% endcontent-ref %}

### Capacities of an individual user

{% content-ref url="/pages/03fb86a8f7e990922ce15c0f2351752bf59e14bb" %}
[Capacity planning](/die-agenturverwaltung-en/einstellungen-1/benutzerverwaltung/benutzer/capacity-planning.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/berichte-1/team-capacities.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.