Consent that’s tamper-evident by design
Guided portal signing, a SHA-256 tamper-evidence hash, and a complete audit trail — linked directly to the Odoo contact it belongs to. Know exactly who agreed to what, and when.
Signed consent forms end up scattered across scanned PDFs, a paper filing cabinet, or a stand-alone e-signature tool that lives outside Odoo. When a dispute or audit arrives, there is no easy way to prove the document was not altered after signing, that the right person actually signed it, or which version of the disclosure they agreed to.
Digital Consent Form captures a legally-recognized e-signature straight from the Odoo portal, hashes every signed disclosure with SHA-256 so any alteration is instantly detectable, and snapshots the exact disclosure version each signer agreed to. Every request, signature, and audit trail lives right on the contact record it belongs to.
This app speaks your language.
Tell us the language your team works in and we translate this module for you, free of charge — so everyone works in the language they know best.
Request my free translation →No hidden fees. No subscription.
Everything a defensible consent record needs
Every capability below is implemented in the module.
Guided Portal Signing
Signers review and sign disclosures from the Odoo portal with no separate login, using an on-screen draw, initials, or typed signature.
Tamper-Evident SHA-256 Hash
Every signed disclosure is hashed the moment it is signed. A one-click Verify Integrity check recomputes the hash on demand and flags any alteration instantly.
Complete Audit Trail
Signer name, IP address, browser user-agent, and timestamp are captured with every signature and preserved in the record’s chatter history.
Consent Versioning
Publishing a new template version leaves every past request holding the exact disclosure text it was sent with, so you can always prove which version a signer agreed to.
Bulk Send & Automated Reminders
Send a consent request to any number of contacts at once, then let a scheduled action chase unsigned requests automatically until they expire.
Consent Linked to the Contact
A smart button on every Odoo contact shows their consent history and signed status, so staff see coverage without ever leaving the customer record.
Completion Analytics
Pivot and graph views break down request counts and completion rates by template and status, so managers see consent coverage at a glance.
Professional PDF Certificate
Download a formatted, print-ready consent certificate for any signed request, complete with its audit metadata, ready to file or hand to the signer.
White-Label Branding
A single settings toggle removes third-party branding from the portal and PDF certificate, so the signing experience matches your own business identity.
How it works
Publish a disclosure
Write the consent text once as a template, set signature and reminder rules, then publish it so it is ready to send.
Send to one or many
Send a single request, or use the bulk wizard to request consent from an entire contact list in one action.
Signer reviews and signs
The contact opens a secure portal link, reads the disclosure, and signs through a guided, step-by-step flow — no account required.
Verify and report
Every signature is SHA-256 hashed and logged to the contact record, with a printable PDF certificate and dashboard rollup always on hand.
See it in action
From request pipeline to signed, tamper-evident record.
Consent request pipeline with color-coded status badges — draft, sent, signed, declined, and expired — so nothing pending goes unnoticed.
Kanban board of consent requests grouped by status, for a fast visual read of what is outstanding.
A signed consent request: header workflow buttons, statusbar, and the full disclosure text the signer agreed to.
Signature & Audit tab: signer identity, IP address, browser, and the SHA-256 tamper-evidence hash — with an instant tamper check.
Consent template library with version numbers, publish status, and live completion-rate tracking per template.
Template kanban view showing completion progress at a glance, ready to publish a new version when policy changes.
Template editor: publish, deprecate, or version a disclosure, plus reminder and expiration settings.
Bulk send wizard: request consent from any number of contacts in one action, straight from the partner list.
App settings: default reminder cadence, maximum reminder count, and the white-label branding toggle.
Every Odoo contact gets a Consents smart button showing signed and pending consent history without leaving the record.
Professional, print-ready consent certificate generated as a PDF for records or the signer.
Portal “My Consents” page listing a signer’s own requests with status and dates.
Guided portal signing: the signer reviews the disclosure and signs on-screen with a draw, initials, or typed signature.
Signed confirmation page showing the captured signature, SHA-256 tamper-evidence badge, audit summary, and a PDF download link.
Frequently asked
Is the signed consent legally binding?
Digital Consent Form captures a legally-recognized electronic signature together with signer identity, IP address, browser metadata, and a timestamp — the evidence needed to demonstrate valid, attributable consent.
How do you prove a signed form has not been altered?
Every signed disclosure is hashed with SHA-256 at the moment of signing. The Verify Integrity button recomputes the hash on demand — any change to the text or signature after signing is flagged immediately.
What happens when our consent policy changes?
Publish a new template version. Every existing request keeps a snapshot of the exact text and version the signer originally agreed to, so past and future consent stay clearly separated.
Do signers need an Odoo account to sign?
No. Signers open a secure portal link and sign directly — no login or account creation is required.
Get in Touch
Have questions or need customization? Every purchase includes 30 days of free support — we are here to help.
Visit Our Website
www.cerevantix.comExplore our apps, services, and portfolio.
Empowering growth through technology.
Guided, tamper-evident consent capture with a complete audit trail — built natively into Odoo contacts.
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Lines of code | 1455 |
| Technical Name |
cerevantix_digital_consent_form |
| License | OPL-1 |
| Website | https://cerevantix.com |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module