> 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/front-office/rendering-types/commoditized-rendering-types/seat-based/show-a-listing-seat-based.md).

# Show a Listing (Seat-Based)

Instructions for listing pages - Seat-Based rendering type activated

{% hint style="info" %} <mark style="color:blue;">Path: Homepage > All listings > Listing</mark>
{% endhint %}

## Definition <a href="#id-1.16.x-listingpage-sessionbundle-definition" id="id-1.16.x-listingpage-sessionbundle-definition"></a>

Listing pages serve as public interfaces that provide detailed information about available services. These pages also enable users to book services directly. In seat-based listings, availability details are clearly presented and explicitly displayed within a designated section of the listing.

<mark style="color:orange;background-color:yellow;">WHO CAN USE THIS FEATURE?</mark>

All users

## Create a listing <a href="#id-1.16.x-listingpage-sessionbundle-createalisting" id="id-1.16.x-listingpage-sessionbundle-createalisting"></a>

Offerors are the only user types who can create listings. Askers cannot create listings.

The listing creation process is described in the article Session solution: [Create a listting](https://app.gitbook.com/o/azXNS7QsS7i7yvHBE0Vd/s/n4EIoqjZx1xWQIo6LnjB/~/changes/63/v2.0/front-office/rendering-types/commoditized-rendering-types/listing-deposit-all-rendering-types)

## Read a listing <a href="#id-1.16.x-listingpage-sessionbundle-readalisting" id="id-1.16.x-listingpage-sessionbundle-readalisting"></a>

See the following documentation for more information: [Show a listing (Time-Based)](https://app.gitbook.com/o/azXNS7QsS7i7yvHBE0Vd/s/n4EIoqjZx1xWQIo6LnjB/~/changes/63/v2.0/front-office/rendering-types/commoditized-rendering-types/time-based/show-a-listing-time-based)

Additionally, listings bear a “Next 5 availabilities” section (figure 1).

This section displays all the upcoming sessions available in the listing.

Each session block (figure 1) displays:

* The session date
* The session start time and end time
* The session price
* A “Choose” button to add the session to the booking request.

<figure><img src="https://2306631548-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fn4EIoqjZx1xWQIo6LnjB%2Fuploads%2FLqMqllhJArcU4qjG2FAP%2Fimage.png?alt=media&amp;token=58d145e2-8c7f-4ca4-962c-16a80793c34c" alt=""><figcaption><p>Figure 1</p></figcaption></figure>

## Update a listing <a href="#id-1.16.x-listingpage-sessionbundle-updatealisting" id="id-1.16.x-listingpage-sessionbundle-updatealisting"></a>

Only offerors can update their listings via their dashboard. The process is described in the article: [**Edit a listing (Seat-Based)**](https://app.gitbook.com/o/azXNS7QsS7i7yvHBE0Vd/s/n4EIoqjZx1xWQIo6LnjB/~/changes/63/v2.0/front-office/rendering-types/commoditized-rendering-types/seat-based/edit-a-listing-seat-based). Askers cannot update listings.

## Delete a listing <a href="#id-1.16.x-listingpage-sessionbundle-deletealisting" id="id-1.16.x-listingpage-sessionbundle-deletealisting"></a>

Only offerors can delete their listings via their dashboard. The process is described in the article:  [**Edit a listing (Seat-Based)**](https://app.gitbook.com/o/azXNS7QsS7i7yvHBE0Vd/s/n4EIoqjZx1xWQIo6LnjB/~/changes/63/v2.0/front-office/rendering-types/commoditized-rendering-types/seat-based/edit-a-listing-seat-based). Askers cannot delete a listings.

## Related resources <a href="#id-1.16.x-listingpage-sessionbundle-relatedresources" id="id-1.16.x-listingpage-sessionbundle-relatedresources"></a>

**Business rules:**

* [Seat-Based rendering type - Business rules](/v2.0/core-concepts/seat-based-rendering-type.md)


---

# 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://features.scnd.com/v2.0/front-office/rendering-types/commoditized-rendering-types/seat-based/show-a-listing-seat-based.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.