> For the complete documentation index, see [llms.txt](https://docs.eventflowapp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eventflowapp.com/eventflow-cms/general-settings/multi-event-mode.md).

# Multi-event Mode

Multi Event Mode is designed for event programmes where multiple events are managed within a single Eventflow manual.

When enabled, you can remove the countdown timer from the dashboard. This is particularly useful for event seasons or programmes where deadlines vary by event and a single countdown is not relevant.

### Disable the countdown timer on the dashboard

To turn off the event countdown timer:

1. Go to **Admin**.
2. Select **Manage Event Details**.
3. Scroll to **Show countdown timer on dashboard**.
4. Select **No**.
5. Click **Save** to apply your changes.

{% @guideflow/guideflow-embed requestedUrl="<https://app.guideflow.com/player/qp742lwijp>" %}

Once disabled, the dashboard will no longer display a countdown timer, allowing teams to focus on managing multiple events without a fixed global deadline.

{% hint style="info" %}
**Note**\
This setting applies across the entire Eventflow manual, making it ideal for multi-event or seasonal programmes.
{% endhint %}


---

# 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://docs.eventflowapp.com/eventflow-cms/general-settings/multi-event-mode.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.