> 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/manage-event-settings.md).

# Manage Event Settings

The Manage Event Details settings page is where you configure key event information, including your event name, start and end dates, company details, and other essential settings required for Eventflow to function correctly.

### Setting event dates

Start by entering your event start and end dates using the date picker fields. These are required fields to ensure: 

* Automated emails are triggered correctly 
* The event countdown is displayed on the dashboard for exhibitors

### Show countdown timer on dashboard

The countdown timer displays the time remaining until your event start date directly on the Dashboard. This provides a quick visual reference for you and your team when managing event timelines.

If you are managing multiple events within a single EventFlow manual, you may prefer to hide the countdown timer to keep the Dashboard focused and uncluttered.

#### To show or hide the countdown timer

1. Go to **General Settings**.
2. Locate **Show countdown timer on dashboard**.
3. Select one of the following options:
   * **Yes** – Displays the countdown timer on the Dashboard.
   * **No** – Hides the countdown timer from the Dashboard.
4. Click **Save** to apply your changes.

{% hint style="info" %}
**Note**\
Hiding the countdown timer does not affect your event dates or deadlines. It only removes the visual timer from the Dashboard view.
{% endhint %}

For more information about managing your event settings, see:

{% content-ref url="/pages/jVZ2VxTlgLnn9DEH0Gx9" %}
[Multi-event Mode](/eventflow-cms/general-settings/multi-event-mode.md)
{% endcontent-ref %}

### Naming your event

To ensure emails and platform references are accurate, you’ll need to provide the following: 

* Event Name – A concise name used in emails for easy identification. 
* Application Name (Short) – A brief, catchy name for use in the dashboard and emails. (e.g. Eventflow Manual) 
* Application Name (Long) – A more detailed name, typically including specifics like the year or event type. (e.g. Eventflow Exhibitor Manual 2025)

These names are used throughout Eventflow to ensure the application aligns with your event branding for a consistent exhibitor experience.

### Evenflow web address

The read-only Application URL field displays the web address for your event. This should match your production web address once published. 

{% hint style="info" %}
If you need to change this, please contact [support](mailto:undefined).
{% endhint %}

### Event team name

This is used as the sign-off in emails sent via Eventflow. Example: 

> “Glastonbury Festival Team”

### Company & address

Your company name and address are required to legally sign off emails, ensuring compliance with local data protection laws.


---

# 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.eventflowapp.com/eventflow-cms/general-settings/manage-event-settings.md?ask=<question>&goal=<endgoal>
```

`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.