> 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/beleid.md). # Policy Policy topics used to categorize requirements, objectives, and risks Policy topics are relevant for categorizing requirements, objectives, and risks arising from the organization’s context.
Uitleg beleid
Uitleg beleid
## Creating a new policy topic After clicking 'new', the name of the policy topic can be entered and it can be indicated whether it concerns company policy or topic-specific policy. Then the HTML editor can be used to draft a policy note or paste one from an existing document. In addition, version history is available to manage changes; here, a table with version number, publication date, and release note can be added.
Aanmaken nieuw beleidsonderwerp
## Editing a policy The text field for policy documents includes version control. How it works — working in draft, starting a publication, reviewing, and the version table — is described in [Version control and publishing](/controlbee-docs/en/versiebeheer-en-publiceren.md). --- # 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/beleid.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.