> For the complete documentation index, see [llms.txt](https://help.horsespot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.horsespot.com/product-docs/show-day-tools/barn-accounts/stabling-requests-settings.md).

# Stabling Requests Settings

{% embed url="<https://www.loom.com/share/30c158346e2146d6a42502d9c5bc8aca>" %}

## **Turning On Stabling Requests**

This guide covers how to enable stabling requests and configure which fees exhibitors see when submitting one.

### Enabling Stabling Requests

1. Go to Settings > General > Public Experience.
2. Scroll down to the Show Fees section.
3. Check the box to allow exhibitors to select their show fees.
4. Check the box to allow exhibitors to create barn accounts/stabling requests.

Checking this second box gives you the option to configure fees specifically for barn accounts.

### Configuring Which Fees Show for Barn Accounts

1. Review the list of fees now available to configure for barn accounts.
2. For each fee that doesn't make sense as part of a barn account or stabling request (for example, Trailer-In, Office Fee, Medic Fee, Late Fee, or Non-Member Fee), set it to Hidden.
3. Leave visible only the fees you'd actually want people selecting as part of a stabling request.
4. Click Save Changes to apply your updates.

### Testing the Public Experience

1. Open the public view of your show in a new browser tab.
2. Click Stabling.
3. Confirm you only see the fees you intended to make available (for example, four fees instead of every fee on the show).
4. If anything looks off, go back to your Public Experience settings and adjust the Hidden/Changeable/Required settings for the fee in question.
5. Save your changes, then repeat steps 1 to 3 to confirm the public side now matches what you expect.


---

# 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://help.horsespot.com/product-docs/show-day-tools/barn-accounts/stabling-requests-settings.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.