CRM, Leads, Campaigns & Portals

Vendor collaboration and internal control

The Vendor Portal lives under frontend/src/portal/vendor and is served by vendor_portal_controller.go. Like the customer portal it has separate authentication, its own dashboard, and share-via-portal-URL access, but it is invitation-only: a vendor must accept an invitation and set up an account before using it.

Vendor-facing capabilities include:

• View purchase orders assigned to the vendor.
• Acknowledge purchase orders with expected delivery dates.
• Track payment status for their invoices.
• Upload documents such as a W-9, insurance certificates, and invoices, which pass through a document review workflow moving from pending to approved or rejected.

Overseeing both portals is Portal Administration, exposed on the PortalSettingsPage and served by portal_admin_controller.go. Administration covers portal URLs, allowed domains, and portal-user provisioning. Internal staff use it to enable or disable portal access per customer or vendor, send portal invitations, review and approve or reject vendor documents, manage pending invitations, and revoke portal user access.

A typical administrative flow is to send a vendor an invitation, which the vendor accepts to set up their account. The vendor then views and acknowledges assigned purchase orders with expected delivery dates and uploads required documents, which internal staff review and approve or reject. Administration keeps this collaboration controlled through domain restrictions, provisioning, and the ability to revoke access.