This module allows you to generate manual and automatic signature requests from project tasks to task customers.
auto_awesome What this module does
AI-generated from the code · Odoo 18.0Automatically sends signature requests to the customer of a project task using a template configured per company. Users can see and open the signature requests linked to a task from the task form.
This module connects project tasks with the OCA signature app. A company can define one signature template for project tasks in the Project settings; the template must be built for the project.task model.
When a task is created with a customer, or when a customer is later added to a task, Odoo automatically creates a signature request from that template and sends it. The request is linked to the task and its project.
On the task form a "Sign Requests" button appears (only for signature users and when at least one request exists) showing how many requests are linked; clicking it opens the list of those requests.
Signature requests now show the related project and task. In the signature request list you can add the Project and Task columns, group requests by project or task, and the request form shows the project when it applies.
Business rules and behaviours shown by the code: - The automatic request is only created if a template is configured for the company and the task has a customer. - The request is sent immediately after being created. - The count of signature requests on a task is computed automatically. - The project and task on a signature request are computed from the linked record and stored.
Access to the task button and to the project/task columns is limited to signature users, project users and signature administrators as defined in the views.
Depends on
Models and fields (4)
- res.company · extends an existing modelproject_task_sign_oca_template_id (Project Task Sign Oca Template)
- project.task · extends an existing modelsign_request_ids (Sign Requests), sign_request_count (Sign request count)
- sign.oca.request · extends an existing modeltask_id (Task), project_id (Project)
- res.config.settings · extends an existing modelproject_task_sign_oca_template_id (Project Task Sign Oca Template)
Text generated by AI (DeepSeek) from reading the Odoo 18.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 5 confirmed, 4 with no information of 9 versions.
Sources · Odoo 18.0
Confirmed on 2026-11-03 in branch 18.0 of OCA/sign.
terminal Installation and usage
OCA documentation · Odoo 18.0Configuration
Source · Odoo 18.0- Go to Sign > Settings > Roles and create a role with the following data:
- Partner type: Expression
- Expression: {{object.partner_id.id}}
- Go to Sign > Templates and create a template with the following data:
- Model: Project Task
- In one of the fields, you must set the previously created role.
- (Optional) Go to Project > Configuration > Settings.
- In the Sign Oca section, define a template to enable automatic task sign requests.
- Use the template previously created.
Usage
Source · Odoo 18.0Creating a Signature Request from a Project Task:
- Go to Projects > Tasks.
- Open an existing task or create a new one (make sure to fill in the partner_id field).
- In the task tree or form view, click on theaction "Sign from template".
- Sign Requests will have been generated (and sent) linked to the selected project and task.
Automatic Signature Request creation:
- Define a template in Project > Configuration > Settings.
- When an customer is assigned to a task, a Sign Request will be created (and sent) automatically.
Viewing Signature Requests:
- Go to Projects > Tasks.
- Open a task with an associated signature request.
- Click on the smart-button Sign Requests.
- Click on any signature request to view its details, status, and progress.
- Alternatively, go to Sign > Requests.
- Use the Group By feature to group requests by Project and/or Task.
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.