> 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/plannen/belanghebbenden.md). # Stakeholders Organizations and individuals that have an influence on or are affected by the organization Stakeholders are identified because of the (possible) impact they have on the organization’s ability to consistently deliver products and services. Stakeholders are organizations and individuals that influence, or are influenced by, activities, products or services. Think of employees who expect data to be handled confidentially, or the government that expects the organization to comply with laws and regulations.
Uitleg belanghebbenden
## Create new stakeholders A user can create new stakeholders by entering the name, recording expectations, and specifying the method of communication.
Aanmaken nieuwe belanghebbenden
## Export stakeholder overview An overview of stakeholders can be exported in xlsx format.
Exporteren overzicht belanghebbenden
## Edit and delete stakeholder When you click through to a stakeholder, you can easily edit or delete the name, expectations, and method of communication.
Bewerken en verwijderen belanghebbende
--- # 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/plannen/belanghebbenden.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.