> 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/update-meeting-details.md).

# Update meeting details

If a Meeting is Shared and you want to update **Title**, **Location**, **Date**, **Time** or **Description**, follow these steps.&#x20;

{% stepper %}
{% step %}
Navigate to the Meeting
{% endstep %}

{% step %}
Click the `Pen-icon`  button at the top right corner of the Meeting Panel

<figure><img src="https://2368761383-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5A8sAk8EwFvZz8ID3yYR%2Fuploads%2F1X11l9VErRzehOKugtyt%2Fmeeting-panel-header-edit-icon.png?alt=media&amp;token=4a3e9998-5807-4ee7-9c70-af9831402485" alt="" width="375"><figcaption></figcaption></figure>

{% endstep %}

{% step %}
Make your changes
{% endstep %}

{% step %}
Click the `Update` button in the Meeting Panel footer
{% endstep %}

{% step %}
A confirmation dialog will appear. If you don't want to send out an updated calendar event by mail to the Meeting Participants of any reason, you can turn `Calendar Event Toggle` off.&#x20;

<figure><img src="https://2368761383-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5A8sAk8EwFvZz8ID3yYR%2Fuploads%2FQxLD6LdAuaCSxPW3kAQM%2Fmeeting-update-dialog-schedule.png?alt=media&amp;token=af5189e4-a298-42b3-8916-5e57aa4d5cf7" alt="" width="375"><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Click the `Upate` button in the dialog to confirm your changes.
{% 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/update-meeting-details.md?ask=<question>&goal=<user_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.
