> For the complete documentation index, see [llms.txt](https://features.scnd.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://features.scnd.com/v2.0/core-concepts/seat-based-rendering-type.md).

# Seat-Based Rendering type

* [Why](#id-1.14.x-sessionbundle-businessrules-why)
* [Which context](#id-1.14.x-sessionbundle-businessrules-whichcontext)
* [Interfaces](#id-1.14.x-sessionbundle-businessrules-interfaces)
* [Configurations](#id-1.14.x-sessionbundle-businessrules-configurations)
* [Workflows](#id-1.14.x-sessionbundle-businessrules-workflows)
* [Special rules](#id-1.14.x-sessionbundle-businessrules-specialrules)

## Why <a href="#id-1.14.x-sessionbundle-businessrules-why" id="id-1.14.x-sessionbundle-businessrules-why"></a>

The Seat-Based rendering type allows offerors to define time slots and limit the number of participants for each session.

The Seat-Based rendering type is a policy where the cost of a service is directly related to the number of people who use it.

## Which context <a href="#id-1.14.x-sessionbundle-businessrules-whichcontext" id="id-1.14.x-sessionbundle-businessrules-whichcontext"></a>

This is a common pricing policy in education booking engines (price per student), entertainment industry booking engines (price per ticket), and collective activities booking engines such as yoga lessons (price per participant).

## Interfaces <a href="#id-1.14.x-sessionbundle-businessrules-interfaces" id="id-1.14.x-sessionbundle-businessrules-interfaces"></a>

You can find here all interface documentation related to the Seat-Based rendering type

**Front:**

* [Listing deposit (Seat-Based rendering type)](/v2.0/front-office/rendering-types/commoditized-rendering-types/seat-based/create-a-listing-seat-based.md)
* [Listing page (Seat-Based rendering type)](/v2.0/front-office/rendering-types/commoditized-rendering-types/seat-based/show-a-listing-seat-based.md)
* [Booking confirmation pages (Seat-Based rendering type)](/v2.0/front-office/rendering-types/commoditized-rendering-types/seat-based/book-a-listing-seat-based.md)

**Dashboard:**

* [User KPI (Time-Based, Seat-Based, Flat-Rate, RFP rendering types)](/v2.0/dashboards/user-kpi-homepage/user-kpi-time-based-seat-based-flat-rate-rfc.md)
* [Listings dashboard (Session bundle)](/v2.0/front-office/rendering-types/commoditized-rendering-types/seat-based/edit-a-listing-seat-based.md)

## Workflows <a href="#id-1.14.x-sessionbundle-businessrules-workflows" id="id-1.14.x-sessionbundle-businessrules-workflows"></a>

There is no specific workflow for the Session bundle

## Special rules <a href="#id-1.14.x-sessionbundle-businessrules-specialrules" id="id-1.14.x-sessionbundle-businessrules-specialrules"></a>

The Session bundle must be enabled with the stock bundle.


---

# 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://features.scnd.com/v2.0/core-concepts/seat-based-rendering-type.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.