> For the complete documentation index, see [llms.txt](https://docs.controlbee.nl/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.controlbee.nl/controlbee-docs/en/profiel/bedrijfsbeheer/actie-types.md). # Action types The types of actions and the fields shown for them The administrator can find here an overview of the action types used within the company. Examples include deviation, improvement point, change and task.
Overzicht actie types
## Create action types When creating an action type, you can select which optional fields should be displayed for that type. In addition, a descriptive text can be added under 'field help text'. That help text is shown in grey when editing actions.
Aanmaken actie types
Aanmaken actie types
## Edit or delete Existing action types can be edited and deleted by clicking the three dots.
Bewerken of verwijderen van actie types
--- # 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://docs.controlbee.nl/controlbee-docs/en/profiel/bedrijfsbeheer/actie-types.md?ask=&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.