Send a purchase-contract email | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/send-a-purchase-contract-email Publisher: Pixie Technologies LLC Automation, notifications, security and troubleshooting Send a purchase-contract email Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on. Verify signer/recipients, PDF attachment and SMTP. Audience: Purchasing staff; Permission: Administrator or relevant Purchase capability; Module v1.7.9; Where to goAdmin Area → Purchase → Contracts → open contract → Send Before you start - Use an account with Administrator or relevant Purchase 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 Verify signer/recipients, PDF attachment and SMTP. 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 → Contracts → open contract → Send. - 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 Contract headerContract name, vendor, purchase order, project, department and service category. Commercial termsPayment terms, payment amount, payment cycle, contract value, notes and description/content. SigningSigner, email, signed status, drawn/uploaded signature, send recipients, attach-PDF choice and SMS option where enabled. Rules and limits - Contract actions are governed by purchase_contracts capabilities. - Signature/send flows depend on the stored signer/email and configured email/SMS services. Check it worked - The supported send a purchase-contract email 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 Send a purchase-order email (https://pixiecrm.com/help-centre/send-a-purchase-order-email)Send a purchase debit-note email (https://pixiecrm.com/help-centre/send-a-purchase-debit-note-email)Understand the Purchase Management cron sequence (https://pixiecrm.com/help-centre/understand-the-purchase-management-cron-sequence)Download a Purchase Management file by folder and attachment ID (https://pixiecrm.com/help-centre/download-a-purchase-management-file-by-folder-and-attachment-id)Browse all Purchase Management guides (https://pixiecrm.com/help-centre/category/purchase-management)Expenses Finance (https://pixiecrm.com/help-centre/category/expenses-finance)Invoices Payments (https://pixiecrm.com/help-centre/category/invoices-payments)Contracts Documents (https://pixiecrm.com/help-centre/category/contracts-documents)