Share a purchase request with vendors
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Generate/use the vendor share flow and recipients.
Where to goAdmin Area → Purchase → Purchase Request → open request → Share Request
Before you start
- Use an account with purchase_request capability and status capability where applicable 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
Generate/use the vendor share flow and recipients. 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 → Purchase Request → open request → Share Request.
- Go to the source record and verify its recipient, status, totals and attachments.
- Select the Send, Email, Share or Request action described in the guide.
- Select recipients and attachment/signature options shown by the form.
- Submit once and verify the activity, delivery metadata, public link or approval request created by the module.
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.
Request headerRequest code/name, requester, type, department, project, related sales estimate/invoice, currency and rate.
Request linesItems, description, quantity, unit, tax, price, discount, subtotal and total.
SourcingSelected vendors, attachments, public share/request-for-quotation actions and approval status.
Rules and limits
- Vendor actions are capability-gated; portal functions also depend on the vendor-portal setting and contact authentication.
- Purchase-request status changes use the dedicated purchase_request status capability in addition to record access.
- Department can be mandatory when pur_department_required_condition is enabled.
Check it worked
- The supported share a purchase request with vendors 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.
Related guides
Was this guide useful?Your response is stored only in this browser.