> For the complete documentation index, see [llms.txt](https://docs.agilecase.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.agilecase.com/user-documentation/dashboard/creating-an-event.md).
# Creating an Event
This lesson will show you how to create an event in AgileCase.
### Fill in event details
After choosing to create an event, fill out the event details.
* The summary allows you to create a title for the event, while the description lets you provide a more in-depth summary. You can also set a location for the event if necessary.
* The Start/End date lets you choose when your event begins and ends. Checking the "This event will last the whole day" box will render the time slot void and have the event cover the whole day.
* The repetition option allows you to set the event to repeat on a daily, weekly, monthly, or annual basis.
* Using the Case option, you can search by case description or number to find the case you want to apply the event to. The calendar option lets you choose which calendar in that case the event will appear in.
* The "Attendees" section allows you to select the users and groups that are invited to the event. Select the user or group you want to add, then click the "+" icon by their name to add them to the event.
Once you have finished filling in the details, click "Save Event" to create the event.
### View event
The event will now be visible under the "Calendar" tab in the relevant case.
---
# 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.agilecase.com/user-documentation/dashboard/creating-an-event.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.