> 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.md).

# General Settings

This is where you manage how your event looks, how it is organised, and how key information is displayed to your team.

From General Settings, you can:

* **Manage branding** – Upload your logo, social icon and login background to align the manual with your event or organisation branding.
* **Manage event details** – Add and update essential event information, including start and end dates.
* **Manage sidebar** – Add, remove and rearrange sidebar menu items to suit your workflow.
* **Terms and variables** – Customise terminology and system variables to match your event’s language.
* **Onboarding** – Create a tailored onboarding experience for new users.

Use General Settings when setting up a new manual or when making structural or branding changes to an existing one.

{% hint style="info" %}
**Tip**\
We recommend reviewing your General Settings before inviting users to ensure your manual reflects the correct event details and terminology.
{% 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 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.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.