> For the complete documentation index, see [llms.txt](https://knowledge-base.letsgetdigital.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge-base.letsgetdigital.com/getting-started/virtual-event-quick-start-guide.md).

# Virtual Event quick-start guide

Get started, by yourself, in less than 30 minutes! This page describes the quick steps you should take to launch a successful virtual platform.

## 1. Get logged into your environment

Logging into your environment can be done in 2 ways; access the virtual event [via phone](https://knowledge-base.letsgetdigital.com/the-admin-panel/virtual-event/logging-in) or access the virtual event [via desktop ](https://knowledge-base.letsgetdigital.com/the-admin-panel/virtual-event/logging-in)in LGD.

## 2. Fill the navigation menu with the modules you want to use

Go to the navigation menu part of the Admin Panel and add all modules you want to use for the event. If you want to see the result; go to the virtual platform and reload the page. To give you some inspiration, use the[ best practices manual](https://app.gitbook.com/o/-Lnut9LElnJrFCEIBWvQ/s/-M5LNCGpK5lyymcFZU4V/~/changes/2138/lets-get-started/virtual-platform-30min-quickstart/virtual-platform-best-practices).

## 3. Complete the data using the Knowledge Base

For the rest of the knowledge base, you can simply search for each module how the settings can be altered, and what it can do.

To improve the speed of completing the data you can use bulk-importing for some of the data (attendees, companies, sessions, etc.) You can find more information in [this article](https://knowledge-base.letsgetdigital.com/the-admin-panel/settings/import-data).

After you have completed the virtual platform, and you like the result, contact support for a final event check!

**WOW! That's easy, right? And the best thing is that everything can be changed by you 24/7 whenever you want to!**


---

# 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://knowledge-base.letsgetdigital.com/getting-started/virtual-event-quick-start-guide.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.