> 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/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](/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 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://docs.controlbee.nl/en/plannen/beleid.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.