Create Accountor Login
Docs

MountDev Ops Contracts

How MountDev Ops Contracts works, page by page. Updated October 8, 2026

MountDev Ops Contracts documentation | Updated October 8, 2026

Our Commitment

MountDev Ops is built security first. Your business data belongs to you, and you can export all of it at any time. We never use analytics or tracking of any kind inside MountDev Ops.

What Contracts Is

Contracts is where your agreements are written, signed, and kept. You keep templates with fields, start a contract from a template for a CRM company or contact, and send it to be signed online by any number of people in order. Each signer gets a private link that expires; no account or sign-in is needed, and signing unlocks only after they scroll through the whole document. Every signature keeps a full audit trail, and when everyone has signed, each signer gets the signed PDF with its signature certificate. Renewal and end dates send your team reminders.

Contracts is its own app, separate from Proposals. Other apps can start a contract here (Starting a Contract).

It starts with the modules below, and every one of them can be changed, given its own icon, turned off, or deleted on Contracts' Settings page, the last item of its menu, the same as any module (Modules and Fields). Adding Contracts adds CRM too, because contracts are for CRM companies and contacts.

In These Docs

  • Templates: the wording you reuse, its fields, signer roles, and terms.
  • Contracts: the Overview page, a contract's page, signers, and the audit trail.
  • Starting a Contract: from the Overview page, and from other apps.
  • Signing: sending, the signing page, signing in order, the audit trail of each signature, declining, sending again, voiding, and the signed PDF.
  • Renewals and End Dates: reminders, automatic renewals, expiry, and renewing by hand.
  • Contracts Settings: the From address, numbering, how long links work, reminders, who hears about what, and the wording signers agree to.

Starting Modules

  • Templates: name, wording, fields, signer roles, term in months, renewal, days of notice before renewal or end, status (Active or Retired), and notes.
  • Contracts: title, number, status (Draft, Out for Signature, Signed, Declined, Voided, or Expired), company, contact, deal, template, wording, start date, end date, renewal date, renewal (Renews automatically, Renew by hand, or Does not renew), term in months, days of notice, when it was sent and signed, the document fingerprint (SHA-256), where it was started from, and notes.
  • Signatures: one for each signature, with everything the audit trail needs: signer, email, title, kind (Contract Signature, Proposal Signature, or Terms Acceptance), status, contract, company, contact, deal, document, reference, signing order, when it was signed and read to the end, IP address, browser, location, how they signed in, the document fingerprint, the electronic signature consent and the wording agreed to, the terms version, where it was signed, the document as signed, the files, amounts, options chosen, the audit trail, and more details. A signature that has a signing time can never be changed.

Who Can Do What

  • Start contracts, send them, send invitations again, void, and renew (permission contracts.work): owners, admins, and members. Members see and change the contracts their role allows (Roles).
  • Contracts Settings (permission contracts.manage): owners and admins.

For AI Agents

AI agents can see the Overview page, contracts, and templates, set the signers of a draft, start a renewal as a draft, and read Contracts Settings and emails. They never start or send a contract, send an invitation again, void a contract, or change settings, because those email clients or change what a client sees.

Ask Us Anything

We’d love to hear from you!