Vendors, contacts and administrators

Upload a vendor attachment

Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.

Store a file against the vendor record.

Audience: Purchasing staffPermission: purchase_vendors capabilityModule v1.7.9

Jump to steps

Where to goAdmin Area → Purchase → Vendors → open vendor → Files → Upload

Before you start

Use an account with purchase_vendors capability and confirm the intended record or setting before making a change.
Follow the exact route above. If the screen or action is absent, check module activation, ownership and permissions rather than using another person’s account.
Use controlled test data for configuration, integration, email, AI, payment, portal or automation changes before production-wide use.

What this guide helps you do

Store a file against the vendor record. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow.

Follow these steps

Go to Admin Area → Purchase → Vendors → open vendor → Files → Upload.
Download or inspect the supported template/field requirements before preparing the file.
Select the Import or Upload action and select the intended file only.
Run validation and correct rejected rows, file types or required values.
Complete the import/upload and review the created records, attachments and any error file.

Fields and options

Vendor identityCompany/name, code, tax/VAT, phone, website, category/group, address and status as exposed by the vendor form.

Contacts and accessVendor contacts, vendor administrators, portal status, language and welcome/notification settings where applicable.

Rules and limits

Vendor actions are capability-gated; portal functions also depend on the vendor-portal setting and contact authentication.

Check it worked

The supported upload a vendor attachment flow completes without bypassing permission or validation checks.
The resulting record, setting, status, file, delivery event or external response is visible from the relevant workspace.
Unexpected validation, provider or linked-record errors are investigated before retrying.

Security, privacy and operational checks

Apply least privilege to purchasing, vendor, invoice, payment, return, contract and report permissions.
Verify vendor identity, bank/payment details, tax, currency, totals and approvals before creating financial commitments.
Treat public links, signatures, portal files, attachments and exported reports as controlled business records.
Test settings and automated jobs with controlled records before production-wide use.

Was this guide useful?Your response is stored only in this browser.