> 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/entries/secretary-pov-on-the-exhibitor-online-entry-sign-up-flow.md).

# Secretary POV on the Exhibitor Online Entry Sign-Up Flow

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

## See What Your Exhibitor Sees

As a show organizer, you can click the name of your horse show in the top left at any time to open the public view in a new tab. This is the exact same page your exhibitors and spectators see. From there, click Add Entry to review the online entry flow yourself.

Every step in that flow is customizable using the settings in the show secretary portion of your horse show. Most of these settings live under the Public Experience tab, where you can make tweaks and customizations that change what appears on your entry flow.

For more detail on the specific settings available, see the Public Experience page.


---

# 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/entries/secretary-pov-on-the-exhibitor-online-entry-sign-up-flow.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.