Contracts
Draft, review, approve, send and sign customer contracts, then track renewals.
Overview
Flow: Draft → (Request Internal Review) → (Submit for Approval) → Approved → Send for Signature → Signed → Active. “Request Internal Review” only moves the contract to legal review inside your company — nothing is emailed. “Submit for Approval” goes to the approvers defined in Administration → Approvals; the contract page shows who is deciding and they approve from their Approvals inbox.
The customer only receives the contract when you click Send for Signature (email with PDF and a secure signing link) or copy the signing link yourself. They can sign or decline on that page; you then counter-sign if required.
When to use contracts
- Selling a service or subscription under written terms.
- Tracking renewal dates.
Prerequisites
Step by step
Screenshot for this step has not been captured yet — run npm run docs:flow.
Lifecycle
A signed contract changes only by amendment or renewal.
Permissions
These permission keys control access (granted to roles in Administration → Roles & Permissions):
- crm.contract.read
- crm.contract.create
- crm.contract.approve
- crm.contract.send
Automation
- Renewal reminders and expiry are handled by a scheduled job.