Contracts, templates and signatures

Send a purchase contract by email

Follow this guide to choose recipients and optional PDF attachment. 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.

Audience: Purchasing staffPermission: purchase_contracts capabilityModule v1.7.9

Jump to steps

Where to goAdmin Area → Purchase → Contracts → open contract → Send Contract

Before you start

Use an account with purchase_contracts 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

Choose recipients and optional PDF attachment. 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 Contract.
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

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 the system enforces

Contract actions are governed by purchase_contracts capabilities.
Signature/send flows depend on the stored signer/email and configured email/SMS services.

How to confirm it worked

The supported send a purchase contract by 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.

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