> 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-the-playcanvas-toolkit-legacy-v3/no-code-tools/seat.md).
# Seat
This document provides a guide that can be used to add a seat to objects in VIVERSE project. This allows the avatar to sit down.
***
### Seat
#### Add functionality to allow avatar to sit down
| | |
| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| When the avatar enters the **SeatHintFarAwayTriggerSphere**, the **SeatHintFarAway** icon (white dot) shows above the seat. | When the avatar enters the **SeatHintTriggerSphere**, the **SeatHint** button (sitting person icon) shows above the seat. |
| | |
| When the avatar clicks on the **SeatHint** button, the avatar sits down. | |
{% stepper %}
{% step %}
#### Add the chair
A. In this example, the chairs and table have been created in the scene under a single entity.
B. Click the **Edit Viverse Extension** button.
{% endstep %}
{% step %}
#### Add the Seat module
A. In the VIVERSE extension, select the **Seat** plugin for the **Select plugins** dropdown.
B. Select the **Seat** module and add it.
C. Add a value to the **number of seats** field.
{% endstep %}
{% step %}
#### Adjust the sitting boundary
A. The **Seat** is automatically generated.
B. Adjust the **Radius** on the **Collision** component to modify the sitting boundary.
{% endstep %}
{% step %}
#### View the SeatHintFarAway icon
A. The **SeatHintFarAway** icon is a white dot that is automatically generated and hovers above each seat.
{% endstep %}
{% step %}
#### Adjust the boundary for the SeatHintFarAway icon
A. The **SeatHintFarAwayTriggerSphere** is automatically generated.
B. Adjust the **Radius** on the **Collision** component to modify the distance away before the **SeatHintFarAway** icon displays. Also ensure the height of the collider is above ground level, so the player capsule collider is sure to intersect with it.
{% endstep %}
{% step %}
#### View the SeatHint button
A. The **SeatHint** button has an icon of a sitting person. The button is automatically generated and hovers above each seat. When clicked, the avatar will sit.
{% endstep %}
{% step %}
#### Adjust the boundary for the SeatHint button
A. The **SeatHintTriggerSphere** is automatically generated.
B. Adjust the **Radius** on the **Collision** component to modify the distance away before the **SeatHint** icon displays.
{% endstep %}
{% endstepper %}
---
# 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-the-playcanvas-toolkit-legacy-v3/no-code-tools/seat.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.
| 
|
| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| When the avatar enters the **SeatHintFarAwayTriggerSphere**, the **SeatHintFarAway** icon (white dot) shows above the seat. | When the avatar enters the **SeatHintTriggerSphere**, the **SeatHint** button (sitting person icon) shows above the seat. |
| 
| |
| When the avatar clicks on the **SeatHint** button, the avatar sits down. | |
{% stepper %}
{% step %}
#### Add the chair
A. In this example, the chairs and table have been created in the scene under a single entity.
B. Click the **Edit Viverse Extension** button.
