> For the complete documentation index, see [llms.txt](https://hub.fruitsalad.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.fruitsalad.ai/rooms/introduction.md).

# Introduction

Welcome to FruitSalad's Collaborative Rooms!

{% hint style="info" %}
We also offer this solution via our affiliate boardroomx.io
{% endhint %}

**Unlock Limitless Collaboration** Our rooms are dynamic spaces designed for up to 100 people, offering ultra large-scale collaboration with up to 1,000 instances. Perfect for teamwork, learning, and large-scale projects.

**Features:**

* **Communication**: Engage via audio, video, and text.
* **Avatars**: Pick a default or create your own with ReadyPlayerMe, express emotions, and navigate through walking, jumping, or running.
* **Access Anywhere**: Join from your browser on mobile, desktop, or headset.
* **Enhanced Collaboration**: Share screens, experience adaptive graphics, interact with embedded webpages, and use the whiteboard.
* **Host Controls**: Manage your room effectively with options to kick, mute individuals or all, and broadcast audio across instances.
* **Secure Authentication**: Easy access with email OTP, and memory for repeat logins.

Discover a new dimension of collaborative learning and teamwork in FruitSalad's Rooms.


---

# 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://hub.fruitsalad.ai/rooms/introduction.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.
