> For the complete documentation index, see [llms.txt](https://conferencetap.gitbook.io/knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://conferencetap.gitbook.io/knowledge-base/organizers/getting-started/how-to-add-and-remove-features-from-your-event.md).

# How to add and remove features from your event

To add and remove features, go to the event admin page, then go to the Details section, and then go to the Features tab.

![](/files/ORKzKngP1lmQWZRFdkPS)

From here, you can add and remove features from your event - just use the checkbox and they will be instantly added or removed.

Adding and removing these features will affect the visibility of the tabs for attendees in the event.

A quick description of each feature:

* **Expo**: this feature allows sponsors to have their own expo booth and collect leads
* **1:1 Virtual Networking Match:** this features in the “people” tab of the app allows users to be randomly matched and have a short conversation with others at the event
* **Lounge:** this feature allows attendees to create their own virtual video rooms to chat with others at the event.


---

# 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://conferencetap.gitbook.io/knowledge-base/organizers/getting-started/how-to-add-and-remove-features-from-your-event.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.