Sending and Withdrawing
Part of the MountDev Ops Proposals documentation. Updated October 7, 2026
MountDev Ops Proposals documentation | Updated October 7, 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.
Sending
Send to Client on a proposal's page (action proposals.send, permission proposals.send):
- To: the client's email (filled in from the proposal), and an optional note for the email.
- The draft becomes this version, frozen exactly as sent, with a fingerprint (SHA-256) of the document. Any version sent before it is replaced, and its link stops working.
- A private link is made for this version. It needs no sign-in, it is signed so it cannot be guessed or changed, and it expires: it can be answered until the Valid Until day, and still opened for 60 more days (see Proposal Settings).
- The email waits one minute. Undo (action
proposals.send.undo) takes it back before it goes out: the version is a draft again, and anything it replaced comes back. Only the person who sent it can undo it. - To send, Proposal Settings needs a From address, and the proposal needs a title, a section or a line, and a Valid Until date of today or later.
The email states why it was sent, and its link carries UTM tags.
Withdrawing
Withdraw (action proposals.withdraw) takes back a proposal waiting on the client: its link stops working and it can no longer be accepted. The reason is for your records only. You can revise it and send it again.
For AI Agents
AI agents never send, undo, or withdraw a proposal. Those stay with people.