> 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/projektverwaltung-1/notizen-in-der-projektverwaltung.md).

# Notes in job management

On the three hierarchy levels of project management (customer, customer account and job) you can in the "Notes" tab for the respective record **create notes and optionally share them with your team.**

![](https://4063991107-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-La4YdZ1Gw5iHapqZfIo%2F-LyTW9Af84I81t8SNhwq%2F-LyTakRJd7F_sTy20uf8%2FBildschirmfoto%202020-01-13%20um%2012.10.34.png?alt=media\&token=f009dcc7-efd0-4a25-b12a-af1f835c590b)

To **create a new note**, simply type your note text into the "New note" field, set the visibility of the entry and click the save button.

You can create any number of notes with different visibilities. In the **"Visible to" field** you can either select one or more users or release the note to all users by selecting the "All" entry.

Notes can be edited by all users who can view the note. This way you can always keep the notes up to date as a team.

{% hint style="info" %}
Do you want to create a personal note that only you can see?

Then simply select your name in the "Visible to" field. \
Other users of Die Agenturverwaltung will not be able to see this note.
{% endhint %}

{% hint style="info" %}
Notes are not viewable on the linked hierarchy levels. \
That means a note on the job is not visible on the linked customer account or in other jobs of the customer account.
{% 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/projektverwaltung-1/notizen-in-der-projektverwaltung.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.
