> For the complete documentation index, see [llms.txt](https://help.hippoly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.hippoly.com/using-hippoly/meetings/delete-agenda.md).
# Delete agenda
To be able to delete an agenda, you must be a **Meeting Organiser** or **Meeting Administrator**, and the agenda must be in editing mode.
{% stepper %}
{% step %}
Open the agenda in the Agenda Builder.
{% endstep %}
{% step %}
Ensure the agenda is in **edit mode**. If not, click the `Edit` button at the top left corner of the Agenda Builder.
{% endstep %}
{% step %}
Click the `Trash bin` button at the top right corner.
Delete agenda
{% endstep %}
{% step %}
A confirmation dialog will appear. Click `Delete` to confirm the deletion.
Delete agenda confirmation
{% hint style="warning" %}
**Note:** Once deleted, an agenda cannot be restored, but any **files uploaded** to it will remain. To delete these files, use the Meeting and Files tab in the Meeting panel. Alternatively, you can reattach them to a new agenda.
{% endhint %}
{% endstep %}
{% endstepper %}
---
# 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://help.hippoly.com/using-hippoly/meetings/delete-agenda.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.
