> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ticketspotapp.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Set up market events and visitor registration

> Create a recurring market, choose free visitor RSVP or a display-only listing, and keep vendor applications separate from visitor admission.

Use **Market** for a regular public market or similar gathering. It starts with weekly **Free RSVP** and no event-wide capacity limit. It does not create a vendor application process, allocate stalls, or approve sellers.

## Template starting point

| Setting | Initial choice |
| - | - |
| Schedule | Weekly |
| Admission | Free RSVP |
| First offer | No admission charge (RSVP) |
| Capacity | Blank / no event-wide cap |
| Attendees choose a time | Not enabled |

These are editable suggestions, not recommended prices or venue limits. Replace the dates, price, and capacity with your own. See [how onboarding works](./overview#complete-onboarding).

## Choose the onboarding answers

Open **Create Event** in the selected workspace.

1. Select **Market** and name the market.
2. Review **Weekly**, the operating weekdays, start/end times, and **Repeats until**. Choose another schedule when needed.
3. Leave **Free RSVP** for visitor registrations. Capacity starts blank; enter a limit if your venue needs one.

<Note>**Create my event** may publish immediately when the requirements are met. Use **Continue later** to finish setup as a draft. Review any plan or publishing message before sharing the event.</Note>

## Finish the event settings

| Where to go | What to configure |
| - | - |
| **Event Details → Event Setup** | Keep RSVP/simple registration when you want a visitor list. Choose [Display Only](/event-management/eventdetails#display-only) if the public should see the listing without registering. |
| **Dates & Times** | Check recurring dates and any special opening times or closures. |
| **Capacity and Tickets** | No event-wide cap does not remove ticket quantities, order rules, or account allowances. Review the resulting registration limits. |
| **Venue & Location** | Provide the market location, hours, and visitor arrival information. |
| **Widget and communications** | Show upcoming market dates using a [calendar layout](/branding-and-design/layout), and enable confirmations only for the registration workflow you use. |

## Visitor admission is separate from vendor registration

If vendors need to apply, use a separate clearly named event/form and configure its questions and approval process. If you sell bookable booths, use a suitable seating chart and ticket/category mappings; see [booths and advanced layouts](/seating-charts/advanced-layouts). The Market template does not turn visitor RSVPs into vendor records. Keep the links and wording for visitors and vendors distinct.

## Check the attendee experience

* Confirm visitors see either RSVP or a listing-only page, as intended.
* Compare the next two market dates and their hours.
* Verify any visitor capacity and that a vendor link goes to its separate application or booking flow.

Review the event’s saved status and [publish/share controls](/event-management/manage-events) when it is ready. Return to [all event types](./overview) to compare starting points.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.