> 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/how-vendors-access-the-portal.md).

# How vendors access the portal

Vendors do not need a Vendor Space account to view their information or interact with you. Every vendor gets a unique, secure link that takes them straight to their portal -- no passwords, no sign-up forms, no friction.

***

## Token-Based Access

Each vendor portal link contains a secure token that identifies the vendor and their associated event. This means:

* **No login required.** Vendors click the link and land directly on their portal.
* **Each link is unique.** A vendor's link only shows their information -- they cannot see other vendors' details.
* **Links are reusable.** The same link works every time the vendor needs to check their portal.

***

## How Vendors Receive Their Link

Vendors get their portal link in several ways:

### 1. Through a Payment Link Email

When you send a vendor a payment link, the email includes access to their portal. After completing payment, vendors can continue using that same link to view their booth details, messages, and event information.

### 2. Through a Message Notification Email

When you send a vendor a message through the Messages page or their company profile, the vendor receives an email notification with a link to the portal's Messages tab. This is often the first way vendors discover their portal.

### 3. Through a Direct Link You Share

You can also share a vendor's portal link manually. This is useful when:

* A vendor needs to check their information but cannot find the original email.
* You want to give a vendor access before sending a payment link.
* A vendor contacts you asking how to view their details.

To find and share a vendor's portal link:

1. Go to **Vendors** in the sidebar.
2. Click on the vendor's name.
3. Copy the **Portal Link** from their profile.
4. Send it to the vendor via email, text, or any other channel you prefer.

***

## Security and Privacy

| Feature                   | How It Works                                                                   |
| ------------------------- | ------------------------------------------------------------------------------ |
| **Unique tokens**         | Each link is cryptographically generated and tied to one vendor company        |
| **Vendor-specific view**  | Vendors only see their own information, never other vendors' data              |
| **No shared credentials** | There are no passwords that could be guessed or leaked                         |
| **Company-scoped**        | Portal access shows only the vendor's own events, orders, booths, and messages |

> **Tip:** If a vendor reports that their link is not working, you can always copy a fresh portal link from their vendor profile and send it to them directly.

***

## Frequently Asked Questions About Portal Access

**Can a vendor bookmark their portal link?** Yes. The link remains valid, so vendors can bookmark it and return anytime.

**What if I want to revoke a vendor's access?** Removing a vendor from your event will deactivate their portal link.

**Do vendors need to install anything?** No. The portal works in any modern web browser on desktop or mobile. No apps or plugins required.


---

# 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/how-vendors-access-the-portal.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.