> 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/untitled.md). # Customers Die Agenturverwaltung uses three hierarchical levels to represent the client side: **customer** > customer account > job. ![](/files/87ae9d36da440b16c173e853f5a28890e6e7bf10) One or more **customer accounts** can be managed for a customer. \ Within a **customer accounts** there can be one or more jobs.\ This page deals with the middle level: **the customer account**. ## Customers in the job management A customer is the top hierarchy level in the job management. The master data of a customer is stored on a customer, which is then used when creating a new customer account. Each customer has a unique short code that is used for project and invoice numbers and is displayed in the customer master data. Since all customer account and job information comes together on a customer record, customer-wide reports and analyses can be displayed and evaluated here. ## The customer status A customer can be set from the status `active` to `dormant` All customer accounts and jobs of this customer are then considered closed regardless of their status. That means no further work times or external services can be booked to them, and new financial documents such as estimates, credit invoices or invoices can no longer be created for these jobs. The status can be set back to `active` at any time. {% hint style="info" %} **Allow status changes only with certain permissions**\ It can also be defined that a user may only change the status under certain conditions - e.g. only with administrator rights. \ One application scenario would be, for example, to allow only administrators to reopen a dormant customer.\ Contact our customer service if you have such rules in your processes:\ {% 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 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/projektverwaltung-1/untitled.md?ask=&goal= ``` `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.