# General Configurations

<figure><img src="https://lh5.googleusercontent.com/2VTZvkIf2zLf8W9WbAS4yOElFHPwBiuBlAdo52OBXVv1UFo8gTZEG-mEm-CQ_5CjeBgdFoXW2evaj8a_NNtSzq1pLJDbYK3nl1QylyqJdEuPC_L-tT3s6y5FyJPcJFja8c5VPMlsQ7qATrqFGP1oNdg" alt=""><figcaption></figcaption></figure>

**Let’s understand the working of each field:**&#x20;

1. **Event name:** A name given to the event (this also shows up in the event URL). Keep it short and simple is a good idea.
2. **Banner URL:** The banner is a display image that show up on the landing page of the event where participants interact with the campaign.&#x20;
3. **Start Date:** The time and date when the event will start.&#x20;
4. **End Date:** The time and date when the event will finish.&#x20;
5. **Tags:** Tags are wide categories of different fields in the blockchain space, like DeFi, gaming, Ethereum, etc. (you can choose what best resonates with your project). Fyre uses these tags to reach out to users who have participated in past events created under similar tags.&#x20;
6. **Notifications:** If an admin/organizer keeps the notification toggle switched on, Fyre sends push notifications of the event to our existing user base on the creation of the event.&#x20;


---

# Agent Instructions: 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:

```
GET https://docs.fyre.hypersign.id/admin-dashboard/events/configurations/general-configurations.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.