> For the complete documentation index, see [llms.txt](https://docs.viverse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.viverse.com/playcanvas-toolkit/building-with-playcanvas-toolkit/sitting.md).
# Sitting
Learn how to implement Sitting functionality in your project
***
## About
PlayCanvas Toolkit comes with no-code solutions for all sorts of interactive experiences, and one of those types is virtual conference rooms. The promising idea of VIVERSE is that interactive 3D Worlds can be used not only for entertainment, but as lush 3D environments for virtual meetings as well!
The Seat is a concept designed to facilitate that. It's a special trigger that shows a dedicated Seat Icon, which upon click results in Player taking a seat at particular spot of the world.
## Usage
All Sitting functionality is implemented by a single `viverseSit` component. Here is how you can integrate it into your project:
{% columns %}
{% column width="66.66666666666666%" %}
{% stepper %}
{% step %}
### Create Seat Entity
* Create a new Entity in your Scene
* Click **Add Viverse Component** button and select **Interaction > Sit**
* If you did everything correctly - you should see a **viverseSit** script attached to your Entity, and a green trigger indicating Seat area
{% endstep %}
{% step %}
### Launch and Test
* Adjust Seat position and rotation in your Scene, and hit Launch
* When approaching Seat Entity you should see **Hint Icon.** If it's not the case — please check whether `Show Hint Icon` is enabled
* Adjust `Inner` and `Outer Range` to control at what distance the **Hint Icon** starts fading in or out. Don't forget to relaunch your Scene for any changes to take an effect!
{% endstep %}
{% endstepper %}
{% endcolumn %}
{% column width="33.33333333333334%" %}
{% endcolumn %}
{% endcolumns %}
{% hint style="info" %}
While **Hint Icon** is a convenient way to interact with Seat Entities, it's not the only way! You can disable Hint Icon and use your custom Trigger / Action pair instead, for example `Trigger (OnSelect)` → `Action (Seat)`. For more details, please refer to [Actions](/playcanvas-toolkit/building-with-playcanvas-toolkit/actions.md) usage.
{% 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.viverse.com/playcanvas-toolkit/building-with-playcanvas-toolkit/sitting.md?ask=&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.
