> 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/utilizing-stabling-requests.md). # Utilizing Stabling Requests {% embed url="" %} ## **What Are Stabling Requests?** Use stabling requests if it would be helpful for exhibitors and trainers to submit block requests for show items, like stalls, shavings, RV spots, or anything else you're offering, separately from submitting an actual entry. Think of a stabling request as working similarly to an entry. Stabling requests live on a second tab on the Barn Accounts page. Once turned on in your horse show settings, exhibitors will be able to submit stabling requests in addition to their entries. ### Submitting a Stabling Request (Exhibitor Side) 1. On the horse show's public page, click Stabling Request, the same way you'd start adding an entry. 2. Enter the barn, farm, or group name. 3. Attach the trainer, the same trainer expected to be listed on the entries coming in for this horse show. 4. Select from the fees you've configured to be available for stabling requests, configured the same way you'd set up fees for entries. **Reviewing and Accepting Stabling Requests (Secretary Side)** 1. Go to Stabling Requests. 2. Open a submitted request. 3. Click Accept. Accepting a request automatically creates a barn account for that trainer, with the items from the request added directly to the billing section. For example, if a request included three stalls, that barn account will now show three stalls, plus any other fees like shavings or hay. **After You Accept a Request** Once accepted, you'll see an overview screen with the total balance due based on what came in on the request. From there, use the other tabs to split fees out or manage details for the entries tagged to that same trainer. {% embed url="" %} ## **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** Only show fees here that you'd actually want people selecting as part of a barn account or stabling request. For example, most competitions wouldn't expect someone to select a trailer-in fee as part of a barn account, so that fee should be hidden here. Other fees you'll typically want hidden from barn accounts include Office Fee, Medic Fee, Late Fee, and Non-Member Fee. Hiding these ensures exhibitors only see the subset of fees relevant to a stabling request. Be sure to click Save Changes any time you make updates here. **Testing the Public Experience** To confirm everything looks right, open the public view in a new tab and click Stabling. This lets you review exactly what an exhibitor sees when submitting a stabling request, you should only see the fees you intended to make available. If anything looks off, go back to your Public Experience settings, make adjustments, and test again until it matches what you expect on the public side. --- # 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/utilizing-stabling-requests.md?ask=&goal= ``` `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.