> For the complete documentation index, see [llms.txt](https://docs.charted.com/ap-automation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.charted.com/ap-automation/charted-features/advanced-vendor-onboarding/vendor-onboarding-queue.md).
# Vendor Onboarding Queue
Manage onboarding and send forms in bulk, with enhanced visibility on the onboarding pipeline
## Advanced Vendor Onboarding Queue
The Advanced Vendor Onboarding (AVO) Queue gives your team a single dashboard to initiate and complete onboarding and capture form updates going forward. It groups every vendor by the stage they're in and lets you act on vendors individually or in bulk.
### How to Enable
If you can't see the new **Queue** tab in the left hand navigation bar under Vendor Onboarding, ensure the **View Vendor Onboarding Dashboard** permission is set. All admins can view the new dashboard without the permssion set.
If you're not an admin, ask your admin to complete the steps below.
1. Click **Settings** (the gear icon in the top right), then **Permissions**.
2. Select **View Vendor Onboarding Dashboard**, then add the role or employee that needs access.
{% hint style="info" %}
The new queue requires the AVO bundle to be licensed and installed in your account. If you can't see the 'View Vendor Onboarding Dashboard' permission as an admin, then the bundle isn't installed for account. Contact your Customer Success Manager or for next steps.
{% endhint %}
### Using the Vendor Onboarding Queue
Once the permission is enabled, a new **Vendor Onboarding** section appears in the navigation bar. Click **Queue** to open it:
The queue shows vendors pending onboarding (Stage = Onboarding) and completed vendors who have outstanding forms sent or in review (Stage = Updating). You can filter on the stage column to determine which vendors are updating vs onboarding for the first time.
#### The five stages
Five tiles run across the top of the dashboard, laid out in the order a vendor moves through onboarding. Each tile represents a stage and its recommended next action:
* **Ready to Onboard:** New vendors land here, ready to begin onboarding.
* *Recommended action:* Click **Start Onboarding**.
* **Ready to Send Form:** These vendors haven't been sent a form yet.
* *Recommended action:* Click **Send Form** and choose the form you want to send. The vendor must have an email address on file, vendors without one are filtered out.
* **Awaiting Response:** The form has been sent, but the vendor hasn't completed it yet.
* *Recommended action:* If it's been a while, send the vendor a [reminder](https://docs.charted.com/ap-automation/charted-features/advanced-vendor-onboarding#toc118817654).
* **Needs Review:** The vendor has submitted the form, and it's ready for your review.
* *Recommended action:* Review the form response.
* **Ready to Complete Onboarding:** At least one form has been applied to the vendor.
* *Recommended action:* Confirm all forms are reviewed (accepted or rejected) and that there are no pending form submissions ([unpublish](#unpublishing-forms) all forms that are no longer required). Then hit then click **Complete Onboarding** using the bulk action.
### Bulk Actions
You can also run two actions across multiple vendors at once from the dashboard: **Start Onboarding** and **Send Form**.
{% hint style="info" %}
Bulk onboarding on a large batch of vendors may take some time, leave the window open until the loading bar is complete.
{% endhint %}
#### Start Onboarding
Moves any selected vendor from **Ready to Onboard** into the next stage, **Ready to Send Form**.
#### Send Form
Sends a form of your choice to eligible vendors. Any vendor with an **In Progress** status is eligible to receive a form, though the recommended path is to send forms to vendors in the **Ready to Send Form** stage.
{% hint style="info" %}
Sending form requires an email attached to the vendor record. Vendors with blank email addresses will be null.
{% endhint %}
#### Complete Onboarding
Complete onboarding pulls in all vendors in the Ready to Complete Onboarding stage. If multiple forms were sent, it's recommended to [unpublish](#unpublishing-forms) all pending forms. Complete Onboarding in bulk to move vendors from **In Progress** to **Completed.**
### Opening a Vendor Record in NetSuite
Click a vendor's name in the queue to jump straight to their NetSuite Vendor record. To take actions (like Start Onboarding, Send Form, and Complete Onboarding) individually on vendors, you'll have to go to the Vendor record
Refer to our Advanced Vendor Onboarding [guide](https://docs.charted.com/ap-automation/charted-features/advanced-vendor-onboarding#toc118817651) for more information on individual actions.
### Customizing the Queue
You can show and hide columns, as needed, by using the Show/Hide Column toggle in the top right of the queue.
### Updating Vendors
Once a vendor has onboarded, the Onboarding Status will update to Completed on the NetSuite Vendor Record. If you send a form to the completed vendor record, or of the vendor record has any outstanding forms that require review or vendor submission, the vendor will re-enter the Queue with a stage of 'Updating'.
### Unpublishing Forms
Since all outstanding forms must be reviewed or completed for the Updating Vendor to clear out of the queue, if there are multiple forms that don't require review, it's recommended to **Unpublish** outstanding forms once the vendor is done updating. You can upublish by going to the **Vendor Record** in NetSuite > **Forms** > **Unpublish**.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.charted.com/ap-automation/charted-features/advanced-vendor-onboarding/vendor-onboarding-queue.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
