Share vendor items
Follow this guide to use the supported item-sharing action. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.
Where to goAdmin Area → Purchase → Vendor Items → open mapping → Share
Before you start
- Use an account with purchase_items or purchase_vendor_items 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 you’ll accomplish
Use the supported item-sharing action. 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 → Vendor Items → open mapping → Share.
- 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 to review
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.
Item masterCommodity/item code, description, group/subgroup, unit, purchase price, tax and purchase eligibility.
Vendor-item mappingVendor, group and selected item list, shared visibility and vendor-specific values where exposed.
Files/importAttachments, spreadsheet import rows, validation errors and generated barcode/code.
Rules the system enforces
- Vendor actions are capability-gated; portal functions also depend on the vendor-portal setting and contact authentication.
- Item and vendor-item operations use separate capability groups.
- Spreadsheet imports can create an error file for rejected rows; review it before retrying.
How to confirm it worked
- The supported share vendor items 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.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.