This module allows to create documents for signature inside Odoo using OWL.
auto_awesome What this module does
AI-generated from the code · Odoo 19.0Lets you prepare PDF documents inside Odoo, place signature, text and check fields on them, and send them to partners for electronic signature through a secure portal link.
This module adds a complete electronic signature workflow to Odoo Community.
- You create reusable templates (
sign.oca.template) from a PDF, then place fields on the pages: text, signature or check (sign.oca.field). Each field is assigned to a role (sign.oca.role) that decides which partner must fill it. - From a template you generate a signature request (
sign.oca.request), either one by one with a wizard or in bulk for several records at once. Requests can be linked to any business record through the Object reference. - Signers receive an email with a secure portal link. On the portal they see the document, fill their fields and sign. Required fields must be filled before signing is accepted.
- When every signer has signed, the request automatically moves to Signed. If the company option is enabled, each signer then receives a copy of the final signed PDF.
- Every action (create, configure, view, sign, cancel, add/edit/delete field) is recorded in a log with user, date and IP address. A signature certificate report is available.
- Partners get a button showing how many signature requests they are involved in, and users see a counter of requests waiting for them.
Depends on
Required by other modules
Menus it adds
Models and fields (14)
- res.users · extends an existing model
- res.company · extends an existing modelsign_oca_send_sign_request_copy (Send signers a copy of the final signed document)
- res.partner · extends an existing modelsigner_ids, signer_count
- sign.oca.role · new modelname, domain, default_partner_id (Default partner), expression_partner (Expression), partner_selection_policy
- sign.oca.field · new modelname, field_type, default_value
- sign.oca.request · new modeldata, name, state, active, signed, to_sign, user_id (Responsible), filename, signer_id (Signer), company_id, record_ref (Object), signer_ids (Signers), template_id, ask_location, current_hash, next_item_id, signed_count, signer_count, signatory_data
- sign.oca.template · new modeldata, name, model (Model name), active, filename, item_ids, model_id (Model), request_ids, ask_location, request_count
- res.config.settings · extends an existing modelsign_oca_send_sign_request_copy
- sign.oca.request.log · new modelip, uid, date, action, signer_id, partner_id, request_id, access_token
- sign.oca.template.item · new modelpage, width, height, role_id, field_id, required, position_x, position_y, placeholder, template_id
- sign.oca.request.signer · new modeldata, model, res_id, role_id, latitude, longitude, signed_on, partner_id, request_id, sequence_id, altered_hash, partner_name, signature_hash, inalterable_hash (Inalterability Hash), is_allow_signature, secure_sequence_number (Inalteralbility No Gap Sequence #)
- sign.oca.template.generate · new modelmessage, sign_now, signer_ids, template_id
- sign.oca.template.generate.multi · new modelmodel, message, template_id
- sign.oca.template.generate.signer · new modelrole_id, wizard_id, partner_id
Text generated by AI (DeepSeek) from reading the Odoo 19.0 code on GitHub; it may contain mistakes, so check the code before deciding. The module is very large and only part of the code was read. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 6 confirmed, 3 with no information of 9 versions.
Sources · Odoo 14.0
Confirmed on 2026-11-03 in branch 14.0 of OCA/sign.
terminal Installation and usage
OCA documentation · Odoo 19.0Configuration
Source · Odoo 19.0There is a wizard (sign.oca.template.generate.multi) that can be used for any model needed. If there is a template without a linked model or linked to a model (res.partner for example) an action will be automatically displayed in the tree and form view (only for users with Sign permissions).
Usage
Source · Odoo 19.0Creation of templates
- Access Sign / Templates
- Create a new template
- Add a PDF File
- Access the configuration menu
- You can add a field by doing a right click inside a page
- Click on the field in order to delete or edit some configuration of it
- The template is autosaved
Sign role
- Access Sign / Settings / Roles
- Create a new role (Equipment employee for example)
- You can set the Partner type you need (empty, default or expression).
- With the expression option you can set: {{object.field_name.id}}
- If you create a sign request from template signer will be auto-create according to roles
Sign a document from template
- Access Sign / Templates
- Press the Sign button from a template
- Fill all the possible partners that will sign the document
- You can link the template to a model (maintenance.equipment for example)
- The signature action will be opened.
- There, you can fill all the data you need.
- Once you finish, press the sign button on the top
- When the last signer signs it, the final file will be generated as a PDF
Sign a pending document
- Go to the pencil icon in the upper right corner (systray) of the sign request to access the pending signatures.
- Press the Sign button from signer request
- The signature action will be opened.
- There, you can fill all the data you need.
- Once you finish, press the sign button on the top
- When the last signer signs it, the final file will be generated as a PDF
Sign from template
- Go to any list view or form view (except sign.oca models), e.g.: Contacts
- Select multiple records (3 for example).
- The "Sign from template" action will be available if there are any sign templates created that are not linked to any model and/or any linked to the corresponding model.
- Select a template.
- Click on the "Generate" button.
- 3 requests will be created (each linked to each selected record) BUT no signer will be set.
- Some extra modules (e.g. maintenance_sign_oca) will automatically set the signers for each request.
Sign from portal
- customers who are using portal can sign their documents from portal directly in addition to being able to sign them from emails.
No verified information in OCA: Installation.
Installation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.