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

# Partner Documentation

> How suppliers and auditors use the partner-facing paths implemented in TexasVerified.

# Partner Documentation

TexasVerified implements two partner-facing engagement paths: a supplier console and a separate auditor console.

## Supplier engagement

An authenticated account with the supplier role can open the Supplier Portal. The implemented console lets a supplier:

| Task | Implemented behavior |
| - | - |
| Verify a retailer permit | Use the permit lookup form in the supplier console. |
| File an invoice | Upload it to a selected location's invoice Drive section. |
| Review purchase inquiries | View inbound inquiries and their current status. |
| Route a resale or exemption certificate | Send a supported certificate to a verified retailer for e-signature when DocuSign is configured and the retailer's sales-tax permit is verified as active. |

The certificate flow supports supplier, retailer-owner, and administrator roles. It links the completed document into the participating drives. The interface states that this is documentation support, not tax advice.

## Auditor engagement

An authenticated account with the auditor role is routed to a standalone Auditor Console rather than the retailer portal. The auditor enters the certificate number displayed on a retailer certificate, placard, or public page and supplies a reason for access.

The retailer that owns the location approves, denies, or later revokes the request. An approval can grant a location-scoped set of records and an optional expiry. The implemented default scope covers permits, COAs, and compliance images. Approved locations appear in the auditor console, where prior grant conversations from the legacy chat feature surface as read-only history.

## Programs not yet documented

> [!NOTE]
>
> Affiliate enrollment, commissions, reseller terms, co-marketing benefits, and a process for provisioning supplier or auditor roles are not yet documented because their implementation was not verified in the source repository. No commercial terms or contact workflow should be inferred from this page.


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