> For the complete documentation index, see [llms.txt](https://vendorspace.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vendorspace.gitbook.io/docs/vendor-portal/portal-overview.md).

# Portal overview

The Vendor Portal is your vendors' window into everything related to their participation in your events. It gives them the information they need without requiring a Vendor Space account or any setup on their end.

***

## Portal Tabs

When a vendor opens their portal link, they land on a clean page with two main tabs: **Overview** and **Messages**.

### Overview Tab

The Overview tab gives vendors a snapshot of their participation across all events:

**Quick Stats**

At the top, vendors see four summary cards:

| Stat                | What It Shows                                   |
| ------------------- | ----------------------------------------------- |
| **Events**          | Number of events the vendor is participating in |
| **Orders**          | Total number of orders placed                   |
| **Total Spent**     | Combined total of all paid orders               |
| **Booths Assigned** | Number of booths assigned to the vendor         |

**Your Events**

A list of all events the vendor is registered for, showing:

* Event name and dates
* Event location
* Event status

**Orders & Payments**

A table of all orders, showing:

| Column     | Details                              |
| ---------- | ------------------------------------ |
| **Event**  | Which event the order is for         |
| **Amount** | Order total                          |
| **Status** | Payment status (pending, paid, etc.) |
| **Date**   | When the order was placed            |

**Your Booths**

If the vendor has been assigned booths, each one is displayed as a card showing:

* Booth number
* Booth label (if set)
* Associated event name
* Booth status
* Location notes (if provided)

### Messages Tab

The Messages tab provides a single, continuous chat between the vendor and your organization. There are no separate threads or subjects -- just one ongoing conversation.

* Messages from your organization appear on the left in a muted style
* The vendor's own replies appear on the right in an accent color
* Each message shows the sender name and timestamp
* The vendor can type a reply and send it directly from the portal

When there are unread messages, a dot indicator appears on the Messages tab.

***

## No Account Required

One of the most important things to communicate to your vendors: they do not need to create an account, remember a password, or download an app. The portal link is all they need.

This is especially helpful for vendors who:

* Participate in events infrequently
* Are not comfortable with technology
* Want quick access without extra steps

> **Tip:** When reaching out to vendors for the first time, mention that the portal requires no sign-up. This removes a common barrier and increases response rates.

***

## Mobile-Friendly

The Vendor Portal is fully responsive. Vendors can access it from their phone, tablet, or computer. Everything adjusts automatically to fit their screen.

***

## What Vendors Cannot See

To protect your operations, vendors do not have access to:

* Other vendors' information or booth assignments
* Your internal notes or task lists
* Financial details beyond their own payment
* Your team's messages or internal communication

The portal is designed to give vendors exactly what they need -- nothing more, nothing less.


---

# 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://vendorspace.gitbook.io/docs/vendor-portal/portal-overview.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.