Handbook / Across everything
Your own mail server, so proposals and invoices arrive from you and replies come back to you.
Twenty-two transactional templates cover everything that happens: invitations and password resets, proposals, change orders, invoices and overdue reminders, payment receipts, purchase orders, project and work order assignments, RFIs raised and answered, submittal reviews, punch assignments, applications for payment, daily site reports, and being named in a note.
Documents go out as PDF attachments, generated at the moment of sending and read back from the file store, so the copy attached is the copy on file.
- Put your mail server inSettings → email delivery. Host, port, and whether it is STARTTLS or implicit TLS.
- Send yourself a testIt tells you exactly what the server said if it refuses.
- Turn delivery onUntil you do, messages are still written and kept - nothing is silently lost.
- Choose what sendsPer-notification switches, so a company sends only what it wants to send.
The outbox keeps every message with a preview of exactly what the client received, the delivery error if it failed, whether it was opened, and a one-click retry. When a client says they never got it, that is the page to open.
SMTP passwords are encrypted at rest and never returned to the browser - the settings form shows dots, and leaving them alone leaves the stored password alone.
Undoing things
| What happened | The way back |
|---|---|
| Sent to the wrong address | Send it again to the right one. Nothing recalls an email. |
| Message failed | The outbox shows why. Fix it and retry from there. |
| Too much noise | Turn individual notifications off in settings rather than turning delivery off entirely. |
Access: Company settings.