> For the complete documentation index, see [llms.txt](https://docs.balkan.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.balkan.id/updates/release-notes/published-access-review-campaigns-can-now-be-deleted.md).
# Published Access Review Campaigns can now be deleted
BalkanID customers in Risk Manager and Administrator roles can now permanently delete published Access Review Campaigns. Customers can now quickly experiment and try different campaign configurations and more effectively maintain their campaign lists.
Access Review Campaigns are an effective way to manage periodic and ad-hoc access reviews. Campaigns provide status and progress report for access reviews. Risk Managers and Administrators can also quickly generate reports for Auditors from a Campaign.
You can delete your campaigns today from the [Campaigns page](https://app.balkan.id/campaigns).
---
# 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.balkan.id/updates/release-notes/published-access-review-campaigns-can-now-be-deleted.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.