# Vendor Portal
A workflow configuration that gives vendors access to a dedicated purchase-order workflow. This is not a Page Builder block — it is an **audience mode** you set on a workflow, combined with standard blocks (such as Transactions Advanced) configured to scope records to the vendor entity.
Vendors log in, see the purchase orders issued to them, and can take configured actions — such as acknowledging receipt or confirming fulfilment.
## Available in
* Workflows configured with the **Vendor** user restriction (set on the Transactions Advanced block)
## When to use
* You want vendors to have a self-service portal where they can see their open purchase orders.
* Your purchase-order workflow needs a vendor-facing view separate from your internal team's view.
* You need vendors to confirm, acknowledge, or update the status of POs without contacting your team directly.
## Before you start
* **Who can do this:** Client admins who can edit workflows and page builder configurations.
* Vendor users must have NetSuite login credentials with the appropriate vendor role.
* The **Transactions Advanced** block on the page must have the **Vendor** user restriction enabled.
* Your NetSuite Admin must confirm the workflow's order type is set to Purchase Order and that vendor records exist in NetSuite.
## How it works
1. The vendor logs in to the SphericalBRM portal with their NetSuite credentials.
2. The workflow loads scoped to that vendor's records. Each vendor sees only their own purchase orders — records belonging to other vendors are not accessible.
3. The vendor can filter and search by PO number, date, or status using the Transactions Advanced block, and drill into any order for line-item detail.
4. Any Action Buttons configured on the page give the vendor self-service actions such as confirming receipt or requesting a change.
{% hint style="info" %}
Vendor scoping is controlled by enabling the **Vendor** restriction on the Transactions Advanced block. This automatically limits record lookups to the vendor entity that is logged in.
{% endhint %}
## What to configure
A vendor portal uses standard Page Builder blocks — the key setting is enabling vendor scoping on the Transactions Advanced block:
* **Transactions Advanced — Vendor restriction** — open the Transactions Advanced block settings and enable the **Vendor** option under User Restrictions. This scopes the transaction list to the logged-in vendor's records only.
* **Order type** — set the workflow's order type to Purchase Order so vendors see POs rather than sales orders.
* **Page layout** — design the page using standard blocks (Order Lines, Transaction Record, Action Button, etc.) as you would for any audience, scoped to purchase-order fields.
* **Actions** — use Action Button to add vendor-facing actions (for example, "Confirm Receipt" or "Request Change").
## Common issues
* **Vendor sees no orders** — confirm the vendor's NetSuite record is linked correctly and the **Vendor** restriction is enabled on the Transactions Advanced block.
* **Wrong orders appearing** — check that the workflow's order type is set to Purchase Order (not Sales Order or Cash Sale).
## Related
Transactions Advanced
The transaction list block used to display purchase orders in a vendor portal.
---
# Agent Instructions: 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:
```
GET https://docs.in8sync.com/client-admin-guide/active-workflows/getting-started/transaction-components/vendor-portal.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.