centersl/odoo-docs
1
0
Fork 0
mirror of https://github.com/odoo/documentation.git synced 2026-03-27 14:10:23 +07:00
Code Issues Packages Projects Releases Wiki Activity

[IMP] sign: updates for 19.0

Browse Source 
task-5106515

closes odoo/documentation#15321

Signed-off-by: Siobhan McGonigle (mcsi) <mcsi@odoo.com>
This commit is contained in:
mcsi-odoo
2025-10-20 16:41:32 +02:00
parent aeaf4b9856
commit cc839a4e5d
75 changed files with 1561 additions and 451 deletions
Download Patch File Download Diff File Expand all files Collapse all files

437
content/applications/productivity/sign.rst
View File

@@ -1,410 +1,47 @@
:nosearch:
:show-content:
:hide-page-toc:
====
Sign
====
**Odoo Sign** allows you to send, sign, and approve documents online, using electronic signatures.
.. toctree::
:titlesonly:
An **electronic signature** shows a person's agreement to the content of a document. Just like a
handwritten signature, the electronic one represents a legal bounding by the terms of the signed
document.
sign/request_signatures
sign/sign_document
sign/security_authentication
sign/configuration
sign/validity
With Sign, you can upload any PDF file and add fields to it. These fields can be automatically
filled in with the user's details present in your database.
**Odoo Sign** allows you to sign, send, and approve documents online using electronic signatures.
Just like a handwritten signature, an electronic signature represents a person's agreement to the
content of a document. Signatures generated using the Sign app are considered as :doc:`valid
electronic signatures <sign/validity>` in the European Union and the United States of America, and
meet the requirements for electronic signatures in most countries.
With Sign, you can:
- :ref:`prepare documents for signing <sign/prepare-document>` by one or more signers using
drag-and-drop fields
- send :ref:`one-off documents for signing <sign/request-signatures/one-off>` from the Sign app
or from an Odoo record
- create and use :ref:`templates <sign/request-signatures/templates>` to
send frequently used documents for signing from the Sign app or from an Odoo record
- create :ref:`document envelopes <sign/prepare-document/create-envelope>` to send multiple
documents in a single signature request or sign multiple documents at the same time
- :ref:`sign documents that have been prepared using Odoo Sign
<sign/sign-document/signature-request>`
- :ref:`sign non-prepared documents <sign/sign-document/pdf-document>` from the Sign app, from
the chatter of an Odoo record, or from the :doc:`Documents <documents>` app
- configure :ref:`auto-complete fields <sign/fields/auto-fill>` that populate with data from your
database during signing
- define :ref:`advanced configuration for signers <sign/prepare-document/signer-settings>` to
require authentication (via SMS, Aadhaar eSisgn, or itsme®), allow delegation, or, for templates,
assign a fixed signer
.. seealso::
- `Odoo Sign: product page <https://www.odoo.com/app/sign>`_
- `Odoo Tutorials: Sign [video] <https://www.odoo.com/slides/sign-61>`_
Validity of electronic signatures
=================================
Documents signed via the Sign app are valid electronic signatures in the European Union and the
United States of America. They also meet the requirements for electronic signatures in most
countries. The legal validity of electronic signatures generated by Odoo depends on your country's
legislation. Companies doing business abroad should also consider other countries' electronic
signature laws.
.. important::
The below information has no legal value; it is only provided for general informational purposes.
As laws governing electronic signatures rapidly evolve, we cannot guarantee that all information
is up-to-date. We advise contacting a local attorney for legal advice regarding electronic
signature compliance and validity.
European Union
--------------
The `eIDAS regulation <http://data.europa.eu/eli/reg/2014/910/oj>`_ establishes the framework for
electronic signatures in the `27 member states of the European Union
<https://europa.eu/european-union/about-eu/countries_en>`_. It distinguishes three types of
electronic signatures:
#. Simple electronic signatures
#. Advanced electronic signatures
#. Qualified electronic signatures
Odoo generates the first type, **simple electronic signatures**; these signatures are legally valid
in the EU, as stated in the eIDAS regulation.
Electronic signatures may not be automatically recognized as valid. You may need to bring
supporting evidence of a signature's validity. While the Sign app provides a simple electronic
signature, some supporting evidence is automatically collected during the signature process, such
as:
#. Email and SMS validation (if enabled)
#. Strong identity proof through itsme® (available in Belgium and the Netherlands)
#. Timestamped, IP and geographically traceable access logs to the documents and their associated
signatures
#. Document traceability and inalterability (any alteration made to a signed document is detected by
Odoo with the use of cryptographic proofs)
.. note::
:doc:`Documentation for Germany <sign/germany>`
United States of America
------------------------
The `ESIGN Act (Electronic Signatures in Global and National Commerce Act)
<https://www.fdic.gov/regulations/compliance/manual/10/X-3.1.pdf>`_, at the interstate and
international levels, and the `UETA (Uniform Electronic Transactions Act)
<https://www.uniformlaws.org/committees/community-home/librarydocuments?communitykey=2c04b76c-2b7d-4399-977e-d5876ba7e034&tab=librarydocuments>`_,
at the state level, provide the legal framework for electronic signatures. Note that `Illinois
<https://www.ilga.gov/legislation/ilcs/ilcs5.asp?ActID=89&>`_ and `New York
<https://its.ny.gov/electronic-signatures-and-records-act-esra>`_ have not adopted the UETA, but
similar acts instead.
Overall, to be recognized as valid, electronic signatures have to meet five criteria:
#. The signer must show a clear **intent to sign**. For example, using a mouse to draw a signature
can show intent. The signer must also have the option to opt out of the electronic document.
#. The signer must first express or imply their **consent to conduct business electronically**.
#. **The signature must be clearly attributed**. In Odoo, metadata, such as the signer's IP address,
is added to the signature, which can be used as supporting evidence.
#. **The signature must be associated with the signed document**, for example, by keeping a record
detailing how the signature was captured.
#. Electronically signed documents need to be **retained and stored** by all parties involved; for
example, by providing the signer either a fully-executed copy or the possibility to download a
copy.
Other countries
---------------
- :doc:`Algeria <sign/algeria>`
- :doc:`Angola <sign/angola>`
- :doc:`Argentina <sign/argentina>`
- :doc:`Australia <sign/australia>`
- :doc:`Azerbaijan <sign/azerbaijan>`
- :doc:`Bangladesh <sign/bangladesh>`
- :doc:`Brazil <sign/brazil>`
- :doc:`Canada <sign/canada>`
- :doc:`Chile <sign/chile>`
- :doc:`China <sign/china>`
- :doc:`Colombia <sign/colombia>`
- :doc:`Dominican Republic <sign/dominican_republic>`
- :doc:`Ecuador <sign/ecuador>`
- :doc:`Egypt <sign/egypt>`
- :doc:`Ethiopia <sign/ethiopia>`
- :doc:`Guatemala <sign/guatemala>`
- :doc:`Hong Kong <sign/hong_kong>`
- :doc:`India <sign/india>`
- :doc:`Indonesia <sign/indonesia>`
- :doc:`Iran <sign/iran>`
- :doc:`Iraq <sign/iraq>`
- :doc:`Israel <sign/israel>`
- :doc:`Japan <sign/japan>`
- :doc:`Kazakhstan <sign/kazakhstan>`
- :doc:`Kenya <sign/kenya>`
- :doc:`Kuwait <sign/kuwait>`
- :doc:`Malaysia <sign/malaysia>`
- :doc:`Mexico <sign/mexico>`
- :doc:`Morocco <sign/morocco>`
- :doc:`New Zealand <sign/new_zealand>`
- :doc:`Nigeria <sign/nigeria>`
- :doc:`Norway <sign/norway>`
- :doc:`Oman <sign/oman>`
- :doc:`Pakistan <sign/pakistan>`
- :doc:`Peru <sign/peru>`
- :doc:`Philippines <sign/philippines>`
- :doc:`Qatar <sign/qatar>`
- :doc:`Russia <sign/russia>`
- :doc:`Saudi Arabia <sign/saudi_arabia>`
- :doc:`Singapore <sign/singapore>`
- :doc:`South Africa <sign/south_africa>`
- :doc:`South Korea <sign/south_korea>`
- :doc:`Switzerland <sign/switzerland>`
- :doc:`Thailand <sign/thailand>`
- :doc:`Turkey <sign/turkey>`
- :doc:`Ukraine <sign/ukraine>`
- :doc:`United Arab Emirates <sign/united_arab_emirates>`
- :doc:`United Kingdom <sign/united_kingdom>`
- :doc:`Uzbekistan <sign/uzbekistan>`
- :doc:`Vietnam <sign/vietnam>`
Send a document to sign
=======================
One-time signature
------------------
You can click :guilabel:`Upload a PDF to sign` from your dashboard for a one-time signature. Select
your document, open it, and drag and drop the required :ref:`fields <sign/fields>` in your document.
You can modify the :ref:`role <sign/role>` assigned to a field by clicking on it and selecting the
one you want.
When ready, click :guilabel:`Send`, and fill in the required fields. Once sent, your document
remains available. Go to :menuselection:`Documents --> All Documents` to see your document
and the status of the signatures.
.. image:: sign/signature-status.png
:alt: Signature status
Validity dates and reminders
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
You can set **validity dates** on limited-duration agreement documents or send **automatic email
reminders** to obtain signatures on time. From your dashboard, click :guilabel:`Send` on your
document. On the new page, go to the :guilabel:`Options` section, fill in the
:guilabel:`Valid Until` field, toggle the :guilabel:`Reminder` switch, and click the value to edit
the default number of days between reminders.
.. image:: sign/reminder.png
:alt: Set the number of days between reminders
Templates
---------
You can create document templates when you have to send the same document several times. From your
dashboard, click :guilabel:`Upload a PDF template`. Select the document and add the required
:ref:`fields <sign/fields>`. You can modify the :ref:`role <sign/role>` of a field by clicking on it
and selecting the one you want.
Click :guilabel:`Template Properties` to add :guilabel:`Tags` to your template, define a
:guilabel:`Signed Document Workspace`, add :guilabel:`Signed Document Tags`, set a
:guilabel:`Redirect Link` that will be available in the signature confirmation message received
after the signature, or define :guilabel:`Authorized Users` if you want to restrict the use of your
template to specific authorized users or groups.
Your templates are visible by default on your dashboard. You can click :guilabel:`Send` to quickly
send a document template to a signer or :guilabel:`Sign Now` if you are ready to sign your document
immediately.
.. tip::
You can **create a template from a document that was previously sent**. To do so, go to
:menuselection:`Documents --> All Documents`. On the document you want to retrieve, click on the
the vertical ellipsis (:guilabel:`⋮`), then :guilabel:`Template`. Click on the vertical ellipsis
(:guilabel:`⋮`) again, then :guilabel:`Restore`. Your document now appears on your dashboard next
to your other templates.
.. _sign/role:
Roles
=====
Each field in a Sign document is related to a role corresponding to a specific person. When a
document is being signed, the person assigned to the role must fill in their assigned fields and
sign it.
Roles are available by going to :menuselection:`Sign --> Configuration --> Roles`.
It is possible to update existing roles or to create new roles by clicking on :guilabel:`New`.
Choose a :guilabel:`Role Name`, add an :guilabel:`Extra Authentication Step` to confirm the
identity of the signing person, and if the document can be reassigned to another contact, select
:guilabel:`Change Authorized` for the role. A :guilabel:`Color` can also be chosen for the role.
This color can help understand which roles are responsible for which field when configuring a
template.
Secured identification
----------------------
As the owner of a document, you may request an :guilabel:`Extra Authentication Step` through
:ref:`SMS verification <sign/sms>` or via :ref:`Itsme® <sign/itsme>` (available in Belgium and the
Netherlands). Both authentication options require :ref:`credits <iap/buying_credits>`. If you do not
have any credits left, the authentication steps will be skipped.
.. seealso::
- :doc:`In-App Purchase (IAP) <../essentials/in_app_purchase>`
- :doc:`SMS pricing and FAQ <../marketing/sms_marketing/pricing_and_faq>`
.. _sign/sms:
SMS verification
~~~~~~~~~~~~~~~~
Go to :menuselection:`Sign --> Configuration --> Roles`. Click in the :guilabel:`Extra
Authentication Step` column for the role, and select :guilabel:`Unique Code Via SMS`.
.. note::
Before being able to send SMS Text Messages, you need to register your phone number. To do so, go
to :menuselection:`Sign --> Configuration --> Settings` and click :guilabel:`Buy credits` under
:guilabel:`Authenticate by SMS`.
Go to the document to sign, add the field for which the SMS verification is required, for example,
the :guilabel:`Signature` field, and click :guilabel:`Send`. On the new page, select the
:guilabel:`customer` and click :guilabel:`Send`.
The person signing the document fills in the :guilabel:`Signature` field, then :guilabel:`Sign`, and
clicks :guilabel:`Validate & Send Completed Document`. A :guilabel:`Final Validation` page pops up
where to add their phone number. One-time codes are sent by SMS.
.. image:: sign/sms-verification.png
:alt: Add a hash to your document
.. note::
- This feature is enabled by default.
- As soon as the :guilabel:`Extra Authentication Step` applies to a role, this validation step is
requested for any field assigned to this role.
.. _sign/itsme:
Itsme®
~~~~~~
Itsme® authentication can be used to allow signatories to provide their identity using itsme®. This
feature is only available in **Belgium** and the **Netherlands**.
The feature can be enabled in :guilabel:`Sign Settings` and applies automatically to the
:guilabel:`Customer (identified with itsme®)` role. To enable it for other roles, go to
:menuselection:`Sign --> Configuration --> Roles`. Click in the :guilabel:`Extra Authentication
Step` column for the role, and select :guilabel:`Via itsme®`.
Go to the document that needs to be signed and add the :guilabel:`Signature` field. Switch to any
role configured to use the feature, and click :guilabel:`Validate` and :guilabel:`Send`.
.. image:: sign/itsme-identification.png
:alt: select customer identified with itsme®
Upon signing the document, the signer completes the :guilabel:`Signature` field and proceeds by
clicking on :guilabel:`Validate & Send Completed Document`, triggering a
:guilabel:`Final verification` page where authentication via itsme® is required.
.. _sign/Aadhaar:
Aadhaar eSign
~~~~~~~~~~~~~
Aadhaar eSign allows signers in India to digitally sign documents using their Aadhaar number and
:abbr:`OTP (One Time Password)` verification. This provides a secure and legally valid way to
complete signatures directly within Odoo Sign.
To enable Aadhar eSign, go to :menuselection:`Sign --> Configuration --> Settings` and enable
:guilabel:`Sign with Aadhar eSign`.
To request signer authentication through Aadhaar eSign:
- Upload or edit an existing PDF.
- On the left panel, click the :icon:`fa-ellipsis-vertical` :guilabel:`(vertical ellipsis)` icon
next to the signer that should authenticate with Aadhaar eSign and click
:icon:`fa-pencil-square-o` :guilabel:`Edit`.
- In the pop-up, select :guilabel:`Via Aadhaar eSign` under :guilabel:`Authentication` and
click :guilabel:`Save`.
Upon signing the document, an extra :guilabel:`Final verification` page will be displayed
where authentication via Aadhaar is required.
.. note::
The digital certification from eMudhra is available in the downloaded document.
Signatory hash
==============
Each time someone signs a document, a **hash** - a unique digital signature of the operation - is
generated to ensure traceability, integrity, and inalterability. This process guarantees that any
changes made after a signature is affixed can be easily detected, maintaining the document's
authenticity and security throughout its lifecycle.
A visual security frame displaying the beginning of the hash is added to the signatures. Internal
users can hide or show it by turning the :guilabel:`Frame` option on or off when signing the
document.
.. image:: sign/sign-hash.png
:alt: Adding the visual security frame to a signature.
.. _sign/field-types:
Tags
====
Tags can be used to categorize and organize documents, allowing users to quickly search for and
filter documents based on specific criteria.
You can manage tags by going to :menuselection:`Configuration --> Tags`. To create a tag, click
:guilabel:`New`. On the new line, add the :guilabel:`Tag Name` and select a :guilabel:`Color Index`
for your tag.
To apply a tag to a document, use the dropdown list available in your document.
.. note::
You can modify the tags of a signed document by going to :menuselection:`Documents --> All
Documents`, clicking the vertical ellipsis (:guilabel:`⋮`) on your document, then
:guilabel:`Details`, and modifying your :guilabel:`Tags`.
Sign order
==========
When a document needs to be signed by different parties, the signing order lets you control the
order in which your recipients receive it for signature.
After uploading a PDF with at least two signature fields with two different roles and clicking
:guilabel:`Send`, toggle the :guilabel:`Specify Signing Order` switch and search for the signer's
name or email information to add them. You can decide on the signing order by typing **1** or **2**
in the first column.
.. image:: sign/specify-signing-order.png
:alt: Toggle the switch to specify the signing order.
Each recipient receives the signature request notification only once the previous recipient has
completed their action.
.. _sign/fields:
Field types
===========
Fields are used in a document to indicate what information must be completed by the signers. You can
add fields to your document simply by dragging and dropping them for the left column into your
document.
Various field types can be used to sign documents (placeholder, autocompletion, etc.). By
configuring your own field types, also known as signature item types, the signing process can be
even faster for your customers, partners, and employees.
To create and edit field types, go to :menuselection:`Sign --> Configuration --> Settings -->
Edit field types`.
You can select an existing field by clicking on it, or you can :guilabel:`Create` a new one. First,
edit the :guilabel:`Field Name`. Then, select a :guilabel:`Field Type`:
- :guilabel:`Signature`: users are asked to enter their signature either by drawing it, generating
an automatic one based on their name, or uploading a local file (usually an image).
Each subsequent :guilabel:`Signature` field type then reuses the data entered in the first field.
- :guilabel:`Initial`: users are asked to enter their initials, in a similar way to the
:guilabel:`Signature` field.
- :guilabel:`Text`: users enter text on a single line.
- :guilabel:`Multiline Text`: users enter text on multiple lines.
- :guilabel:`Checkbox`: users can tick a box (e.g., to mark their approval or consent).
- :guilabel:`Selection`: users choose a single option from a variety of options.
The :guilabel:`Auto-fill Partner Field` setting is used to automatically fill in a field during the
signature process. It uses the value of one of the fields on the contact (`res.partner`) model of
the person signing the document. To do so, enter the contact model field's technical name.
.. tip::
To know the technical name of a field, enable developer mode and hover your mouse on the question
mark next to the field.
.. note::
Auto-completed values are suggestions and can be modified as required by the person signing the
document.
The size of the fields can also be changed by editing the :guilabel:`Default Width` and
:guilabel:`Default Height`. Both sizes are defined as a percentage of the full page expressed as a
decimal, with 1 equalling the full page's width or height. By default, the width of new fields you
create is set to 15% (0.150) of a full page's width, while their height is set to 1.5% (0.015) of a
full page's height.
Next, write a :guilabel:`Tip`. Tips are displayed inside arrows on the left-hand side of the user's
screen during the signing process to help them understand what the step entails (e.g., "Sign here"
or “Fill in your birthdate”). You can also use a :guilabel:`Placeholder` text to be displayed inside
the field before it is completed.
.. image:: sign/tip-placeholder.png
:alt: Tip and placeholder example in Odoo Sign

180
content/applications/productivity/sign/configuration.rst Normal file
View File

@@ -0,0 +1,180 @@
=============
Configuration
=============
.. _sign/configuration/settings:
Settings
========
Sign's general settings, available via :menuselection:`Sign --> Configuration --> Settings`, allow
you to:
- add :ref:`Default Terms & Conditions <sign/configuration/settings-t-and-c>` to the signature
request email
- :guilabel:`Manage template access`; once enabled, it is possible to restrict access to a template
to specific user groups when :ref:`creating or editing the template
<sign/request-signatures/templates>`
- enable the following additional authentication methods, manage the service, and buy credits:
- :ref:`Aadhaar eSign <sign/security/authentication-aadhaar>` (available in India)
- :ref:`itsme® <sign/security/authentication-itsme>` (available in the EU, the UK, Norway, and
Iceland)
- manage authentication via SMS and :ref:`buy credits <in_app_purchase/credits>`
- upload a `.p12` or `.pfx` file containing a personal digital certificate, allowing you to add a
:ref:`cryptographic, or digital, signature <sign/security/cryptographic>` to a document
.. _sign/configuration/settings-t-and-c:
Default terms and conditions
----------------------------
Terms and conditions allow a business to standardize the legal relationship with its clients, define
obligations and expectations, manage risk, and protect its interests by setting clear rules for
aspects such as liability and dispute resolution.
To add default terms and conditions to signature requests:
#. Go to :menuselection:`Sign --> Configuration --> Settings` and enable :guilabel:`Sign Default
Terms & Conditions`.
#. Choose the desired option:
- :guilabel:`Terms in Email`: This option is selected by default and places the terms and
conditions at the bottom of the signature request email. Add your terms and conditions to the
text box.
- :guilabel:`Terms as Web Page`: This option displays the terms and conditions on a web page; the
link to that page is then added as a link in the signature request email. Click
:guilabel:`Save`, then click :guilabel:`Update Terms`. Add your terms and conditions to the
text box, then click :guilabel:`Save`. Click :guilabel:`Preview` to see how the terms and
conditions will be displayed.
.. tip::
In the text box, type `/` to open the :ref:`powerbox <essentials/html_editor/commands>`, then
use commands to insert headings, bulleted lists, etc.
#. Click :guilabel:`Save`.
.. note::
It is also possible to manually attach files, such as terms and conditions, when
:ref:`configuring a signature request <sign/configure-signature-request>`. For :ref:`templates
<sign/request-signatures/templates>`, files can be attached by default in the
:guilabel:`Communication` section of the template :guilabel:`Configuration` when creating or
editing the template.
.. _sign/configuration/fields:
Fields
======
Fields are :ref:`added to documents <sign/prepare-document/add-fields>` to indicate what information
must be completed by the signers. Various fields are available by default. These fields can be
:ref:`edited and additional fields can be created <sign/fields/create-edit-fields>` if needed.
.. _sign/fields/create-edit-fields:
Create and edit fields
----------------------
To create or edit a field:
#. Go to :menuselection:`Sign --> Configuration --> Fields`.
#. Click :guilabel:`New` to create a new field or click on a field to open and edit it.
#. Complete or edit the following fields:
- :guilabel:`Field Name`: Enter or edit the field name. This is visible in the list of fields in
the left panel when a document is being :ref:`prepared for signature <sign/prepare-document>`.
- :guilabel:`Type`: Choose the relevant :ref:`field type <sign/fields/field-types>` from the
dropdown; there are nine possible field types.
- :guilabel:`Placeholder`: Optionally, specify a placeholder text that provides the signer with a
hint or example :ref:`during the signing process <sign/sign-document/signature-request>`. If
this field is left blank, the :guilabel:`Field Name` is used as placeholder text.
- :guilabel:`Tip`: Add a tip that will be displayed inside an arrow to the left
of the document during the signing process to help the signer understand what action to take
(e.g., "Sign here").
- For :guilabel:`Text` fields only, optionally change the default :guilabel:`Field Size` from
:guilabel:`Regular Text` to :guilabel:`Short Text` or :guilabel:`Long Text`.
.. note::
The size of any field can be modified manually when :ref:`adding the field to a document
<sign/prepare-document/add-fields>`.
- For :guilabel:`Text` and :guilabel:`Multiline Text` fields only, optionally use the
:guilabel:`Linked to` field to :ref:`configure auto-completion <sign/fields/auto-fill>` so the
field can be auto-completed during the signing process.
.. _sign/fields/field-types:
Field types
~~~~~~~~~~~
- :guilabel:`Signature`: Signers enter their signature either by generating an automatic
signature based on their name, drawing it using their mouse, or uploading a local file (usually an
image). Each subsequent :guilabel:`Signature` field in a document reuses the data entered in the
first field.
- :guilabel:`Initial`: Signers enter their initials, in a similar way to the :guilabel:`Signature`
field.
- :guilabel:`Text` and :guilabel:`Multiline Text`: Signers can enter text on a single line or on
multiple lines, respectively. These field types can be :ref:`configured to be auto-completed
<sign/fields/auto-fill>` during the signing process.
- :guilabel:`Checkbox`: Signers can tick a box (e.g., to confirm they accept the terms and
conditions).
- :guilabel:`Radio`: Signers can select a single option from a series of options (defined when the
field is :ref:`added to the document <sign/prepare-document/add-fields>`) by clicking the radio
button beside the desired option.
- :guilabel:`Selection`: Signers can select a single option from a series of options (defined when
the field is :ref:`added to the document <sign/prepare-document/add-fields>`) via a dropdown
menu.
- :guilabel:`Strikethrough`: Signers can reject certain phrases by clicking the strikethrough field,
which adds a visible line through the text.
- :guilabel:`Stamp`: Signers can add a company stamp (defined when the
field is :ref:`added to the document <sign/prepare-document/add-fields>`).
.. _sign/fields/auto-fill:
Configure auto-complete fields
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
To reduce the need for manual input and ensure accurate and consistent information, it is possible
to have certain fields automatically completed with data from your database :ref:`during the signing
process <sign/sign-document/signature-request>`. This is done by linking a Sign field to a field
from a specific :doc:`Odoo model <../../studio/models_modules_apps>`.
To enable auto-completion for a Sign field:
#. Go to :menuselection:`Sign --> Configuration --> Fields`.
#. Open the relevant field.
#. From the dropdown beside :guilabel:`Linked to` select the model, e.g., *Contact*, that contains
the field you want to link to.
#. Click beside :guilabel:`Linked Field`, then use the field selector to select the relevant field,
e.g., Email.
.. note::
When a document containing this field is being signed, the field is auto-completed. By default,
field can still be edited after auto-completion. However, this can be prevented by editing the
field *after it has been added to the document* and setting it to :guilabel:`Read-only`.
.. example::
In the example, the :icon:`fa-envelope` :guilabel:`Email` field in the Sign app is linked to the
:guilabel:`Email` field in the *Contact* model. When the contact completes the document, their
email address, as it appears in their record in the Odoo database, is automatically added to the
document.
.. image:: configuration/auto-complete.png
:alt: Configuring a field to be auto-completed
.. _sign/configuration/tags:
Tags
====
Tags can be used to categorize and organize documents and templates within the Sign app, allowing
users to quickly search for and filter documents and templates based on specific criteria.
To create a new tag:
#. Go to :menuselection:`Sign --> Configuration --> Tags`.
#. Click :guilabel:`New`.
#. On the new line that is added at the bottom of the list of tags, type the :guilabel:`Tag Name`
and select a :guilabel:`Color Index` for your tag.

BIN
content/applications/productivity/sign/configuration/auto-complete.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 12 KiB

BIN
content/applications/productivity/sign/itsme-identification.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 20 KiB

BIN
content/applications/productivity/sign/reminder.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 3.3 KiB

645
content/applications/productivity/sign/request_signatures.rst Normal file
View File

@@ -0,0 +1,645 @@
===================
Request a signature
===================
Via the Odoo Sign app or directly from an Odoo record, you can:
- request the signature of one or more signers on :ref:`a one-off document or envelope of
multiple one-off documents <sign/request-signatures/one-off>`
- :ref:`use templates <sign/request-signatures/templates>` to request the signature of one or more
signers on frequently used documents
Once a document or :ref:`document envelope <sign/prepare-document/create-envelope>` has been fully
signed, i.e., completed and signed by all signers, the signed document(s) and the :ref:`certificate
of completion <sign/security/certificate-of-completion>` are sent via email to the requestor, and to
any contacts added in :guilabel:`CC` when the signature request was :ref:`configured
<sign/configure-signature-request>`.
.. _sign/request-signatures/one-off:
One-off documents
=================
.. _sign/request-signatures/one-off-app:
From the Sign app
-----------------
To request the signature of a one-off document or :ref:`document envelope
<sign/prepare-document/create-envelope>` from the Sign app:
#. Go to :menuselection:`Sign --> Documents --> My Documents` or :menuselection:`--> All Documents`,
click :guilabel:`Upload PDF`, then select and open the relevant `.pdf` document(s).
If the document needs to be imported from the :doc:`Documents <../documents>` app, click the
:icon:`fa-cog` :guilabel:`(Actions)` icon beside the name of the view, then
:menuselection:`Import from Documents`.
.. tip::
If you are creating a document envelope that includes one document saved in the Documents app,
import that document *before* :ref:`adding subsequent documents
<sign/prepare-document/create-envelope>`.
#. :ref:`Prepare the document(s) for signing <sign/prepare-document>` by adding the relevant
fields; add additional signers and/or documents, if relevant.
#. Click :guilabel:`Send`.
#. Complete the relevant fields of the :ref:`New Signature Request
<sign/configure-signature-request>` window.
#. If you are:
- one of the signers and you are ready to sign the document directly, click :guilabel:`Sign Now`,
then :ref:`complete and sign the document(s) <sign/sign-document/signature-request>`.
- not one of the signers or a signing order has been defined and you need to sign the document
*after* other signers, click :guilabel:`Send`.
.. _sign/request-signatures/one-off-record:
From an Odoo record
-------------------
To request the signature of a one-off document or :ref:`document envelope
<sign/prepare-document/create-envelope>` from an Odoo record:
#. With the relevant record open, click the :icon:`fa-cog` :guilabel:`(Actions)` icon in the
upper-left corner, then :icon:`fa-file-text` :guilabel:`Request Signature`.
#. In the :guilabel:`New Signature Request` window, click :guilabel:`Upload PDF`, select the
relevant `.pdf` document(s), then click :guilabel:`Open`.
#. :ref:`Prepare the document(s) for signing <sign/prepare-document>` by adding the relevant
fields; add additional signers and/or documents, if relevant.
#. Click :guilabel:`Send`.
#. Complete the relevant fields of the :ref:`New Signature Request
<sign/configure-signature-request>` window.
.. note::
When sending a signature request from an Odoo record, the related customer (or the relevant
party) is automatically added as a signer.
#. If you are:
- one of the signers and you are ready to sign the document directly, click :guilabel:`Sign Now`,
then :ref:`complete and sign the document(s) <sign/sign-document/signature-request>`.
- not one of the signers or a signing order has been defined and you need to sign the document
*after* other signers, click :guilabel:`Send`.
.. note::
Once a document or :ref:`document envelope <sign/prepare-document/create-envelope>` has been
fully signed, the signed document(s) and the certificate of completion are also added to the
record's chatter.
.. _sign/request-signatures/templates:
Templates
=========
When the same single document or :ref:`envelope of multiple documents
<sign/prepare-document/create-envelope>` needs to be used regularly, creating and using a template
can save time and streamline the workflow. Templates are prepared for signing in the same way as
one-off documents, by adding the necessary fields, signers, documents, and tags, as relevant.
.. _sign/templates/create:
Create a template
-----------------
To create a template:
#. Go to :menuselection:`Sign --> Templates`.
#. Click :guilabel:`Upload PDF`, then select and open the relevant `.pdf` document(s). If the
document needs to be imported from the :doc:`Documents <../documents>` app, click the
:icon:`fa-cog` :guilabel:`(Actions)` icon beside the name of the view, then
:menuselection:`Import from Documents`.
.. tip::
If you need to upload multiple documents, i.e., create a :ref:`document envelope
<sign/prepare-document/create-envelope>`, and one of the documents is saved in the Documents
app, import that document *before* :ref:`adding subsequent documents
<sign/prepare-document/create-envelope>`.
Once you have created the template, you can start :ref:`editing it <sign/templates/edit>`.
.. _sign/templates/edit:
Edit a template
---------------
A template can be edited at any time, provided it has *not yet been used* to send a signature
request.
To edit a template, go to :menuselection:`Sign --> Templates` and click on the relevant template to
open it. Alternatively, hover over the template, click the :icon:`fa-ellipsis-v`
:guilabel:`(vertical ellipsis)` icon in the top-right corner of the card, then click
:guilabel:`Edit`.
.. note::
When you open a template that has already been used to send a signature request, the template is
in *visualization mode*. Clicking :icon:`fa-pencil` :guilabel:`Edit Template` in this case
creates a copy of the template, which can then be edited.
.. image:: request_signatures/visualization-mode.png
:alt: Viewing a template that has been used to send a signature request
Edit the template:
- :ref:`Prepare the document(s) for signing <sign/prepare-document>` by adding or editing fields,
and, if relevant, adding or removing signers and/or documents.
- Optionally, :ref:`define or edit settings for specific signers
<sign/prepare-document/signer-settings>`, such as requiring additional authentication, allowing a
signer to delegate signing, or assigning a fixed signer.
- Optionally, define or edit general settings for the template by clicking the :icon:`fa-cog`
:guilabel:`(cog)` icon beside the template name, then clicking :icon:`fa-cog`
:menuselection:`Configuration`:
- By default, the **name of the template** is the name of the document that was uploaded, or, in
the case of a :ref:`document envelope <sign/prepare-document/create-envelope>`, the name of the
first document uploaded. If desired, edit the name of the template.
- :guilabel:`Tags`: Add :ref:`tags <sign/configuration/tags>` to categorize the
template.
- :guilabel:`Model`: Select the :doc:`Odoo model <../../studio/models_modules_apps>` to which the
template is linked to restrict the template to :ref:`signatures requests made from records of
that model <sign/templates/use-odoo-record>`. Leave the field empty to make the template
available from any model.
- :guilabel:`Redirect Link`: Add a url to which the user is redirected after signing the document,
e.g., to a *Thank you* page, or to your company's homepage.
- :guilabel:`Documents folder`: Define in which :ref:`folder in the Documents app
<documents/folders>` the documents using this template should be saved once fully signed.
- :guilabel:`Documents tags`: Determine which :ref:`Documents-app tags <documents/tags>` should be
assigned to documents using this template once fully signed.
- :guilabel:`Authorized Users`: Determine which specific users are authorized to view and use
this template.
- :guilabel:`Valid for`: Set a default number of days after which signature requests using this
template expire; enter `0` if signature requests should not expire.
.. note::
The validity date of a signature request can always be modified when :ref:`configuring the
signature request <sign/configure-signature-request>`.
- In the :guilabel:`Communication` tab, type a default text that will be added when a signature
request using this template is sent via email; the text can still be edited before sending.
.. tip::
Type `/` to open the :ref:`powerbox <essentials/html_editor/commands>`, then use commands to
insert headings, bulleted lists, documents, images, etc.
- If :guilabel:`Manage template access` is enabled in the :ref:`main Sign settings
<sign/configuration/settings>`, it is also possible to configure the following fields:
- :guilabel:`Authorized Groups`: Define user groups whose members are authorized to view and use
this template.
- :guilabel:`Responsible` user: By default, this is set to the user who created the template,
but a different user can be selected.
.. _sign/templates/use:
Use templates
-------------
Templates can be used when initiating a signature request :ref:`from the Sign app
<sign/templates/use-sign-app>` or directly :ref:`from an Odoo record
<sign/templates/use-odoo-record>`.
.. _sign/templates/use-sign-app:
From the Sign app
~~~~~~~~~~~~~~~~~
When using a template, there are two ways a signature request can be sent from the Sign app:
- **via direct email** to one or more specific signers; or
- **via a shareable link**, provided the document or document envelope has *only one signer*. This
option is useful when multiple individuals need to sign a personal copy of a document that
requires a single signature, e.g., a non-disclosure agreement.
.. note::
Each time a template is used to send a signature request via direct email, and each time a
recipient of a link signs a document, a new document is created within Odoo Sign and appears in
:menuselection:`Sign --> All Documents`.
To send a signature request using a template to one or more specific signers from the Sign app:
#. Go to :menuselection:`Sign --> Templates` to see all existing templates.
#. From the Kanban or list view, click :guilabel:`Send` on the line of the relevant template.
Alternatively, from the Kanban view, click on a template to open it, then click :guilabel:`Send`.
#. Complete the relevant fields of the :ref:`New Signature Request
<sign/configure-signature-request>` window.
#. If you are:
- one of the signers and you are ready to sign the document directly, click :guilabel:`Sign Now`,
then :ref:`complete and sign the document(s) <sign/sign-document/signature-request>`.
- not one of the signers or a signing order has been defined and you need to sign the document
*after* other signers, click :guilabel:`Send`.
To copy a link to a templated document or document envelope:
#. Go to :menuselection:`Sign --> Templates` to see all existing templates.
#. From the Kanban or list view, click :guilabel:`Share` on the line of the relevant template.
Alternatively, from the Kanban view, click on a template to open it, then click
:guilabel:`Share`.
#. Optionally, update the :guilabel:`Valid Until` date if the signature request link should expire;
leave this blank if the signature request does not expire.
#. Click :icon:`fa-clone` to copy the link to your clipboard.
.. tip::
- After a link has been shared, a :guilabel:`Shared` tag appears on the card of the relevant
template in the :guilabel:`Templates` Kanban view.
- To stop sharing a link, from the :guilabel:`Templates` Kanban view, click
:guilabel:`Share` on the line of the relevant template, then click :guilabel:`Stop sharing`.
Alternatively, hover over the relevant template, click the :icon:`fa-ellipsis-v`
:guilabel:`(vertical ellipsis)` icon in the top-right corner of the card, then click
:guilabel:`Stop sharing`.
.. _sign/templates/use-odoo-record:
From an Odoo record
~~~~~~~~~~~~~~~~~~~
To send a signature request using a template from an Odoo record:
#. With the relevant record open, click the :icon:`fa-cog` :guilabel:`(Actions)` icon in the
upper-left corner, then :icon:`fa-file-text` :guilabel:`Request Signature`.
#. In the :guilabel:`New Signature Request` window, select the relevant :guilabel:`Template` from
the dropdown.
#. Complete the relevant fields of the :ref:`New Signature Request
<sign/configure-signature-request>` window.
#. If you are:
- one of the signers and you are ready to sign the document directly, click :guilabel:`Sign Now`,
then :ref:`complete and sign the document(s) <sign/sign-document/signature-request>`.
- not one of the signers or a signing order has been defined and you need to sign the document
*after* other signers, click :guilabel:`Send`.
.. note::
- Templates linked to the current :doc:`Odoo model <../../studio/models_modules_apps>` can be
selected, as well as templates that are not linked to any model.
- When sending a signature request from an Odoo record, the related customer (or the relevant
party) is automatically added as a signer.
- Once a document or :ref:`document envelope <sign/prepare-document/create-envelope>` has been
fully signed, the signed document(s) and the certificate of completion are also added to the
record's chatter.
.. _sign/templates/manage:
Manage templates
----------------
Manage templates by going to :menuselection:`Sign --> Templates`. By default, templates are shown in
a Kanban view, with cards shown horizontally.
.. tip::
- Remove the :guilabel:`My Favorites` :ref:`filter <search/preconfigured-filters>` to view all
document templates in the database.
- A panel on the left side allows the view to be filtered by :ref:`tag
<sign/configuration/tags>`, if the displayed templates have been assigned tags. Click the
:icon:`oi-panel-right` icon to close or open the panel.
For each template, the following information is shown:
- the name of the template
- the month and year in which the template was created
- the avatar of the :guilabel:`Responsible` user for the template; this is by default the user who
created the template, but this can be changed in the configuration settings of the template if
:guilabel:`Manage template access` is enabled in the :ref:`main Sign settings
<sign/configuration/settings>`
- any tags assigned to the template
- the number of documents created using the template for which a signature request is
:guilabel:`In Progress`
- the number of documents created using the template that have been fully :guilabel:`Signed`
.. tip::
Templates you created yourself are automatically marked as favorites for quicker access. To
favorite templates created by others, click the :icon:`fa-star` :guilabel:`(star)` in front of
the template name.
Hovering over the template's card reveals a :icon:`fa-ellipsis-v` :guilabel:`(vertical ellipsis)`
icon in the top-right corner. Click the icon to:
- :ref:`Edit a template <sign/templates/edit>` that has *not yet been used* to send a signature
request. Alternatively, click on a template to open it for editing.
- :guilabel:`Duplicate` a template. The duplicated template can then be
:ref:`edited <sign/templates/edit>` as needed.
- :guilabel:`Archive` a template that is not currently needed.
- Select a :guilabel:`Color` to add a colored bar to the left side of a card to visually
differentiate it.
.. _sign/prepare-document:
Prepare a document for signing
==============================
To prepare any document for signing, :ref:`add the relevant fields
<sign/prepare-document/add-fields>` for each signer.
It is also possible to:
- :ref:`add additional documents <sign/prepare-document/create-envelope>`
- :ref:`configure and add signers <sign/prepare-document/signers>`
- :ref:`add tags <sign/prepare-document/add-tags>`
.. _sign/prepare-document/add-fields:
Add fields to a document
------------------------
To add a field to a document, drag it from the left panel and drop it in the appropriate place in
the document.
.. note::
Various fields are available by default. These fields can be :ref:`edited and additional fields
can be created <sign/fields/create-edit-fields>` if needed.
Fields of the following :ref:`field types <sign/fields/field-types>` require some additional
configuration when they are added to a document:
- :guilabel:`Initial`: When this field is added to a multi-page document, a pop-up message asks if
the field should be added to all pages of the document, or only the current page.
- :guilabel:`Radio`: By default, two radio buttons are added; there must always be a minimum of two
options. To increase or decrease the number of options, click on one of the radio buttons, then
under :guilabel:`Options`, use the :icon:`fa-caret-up` :guilabel:`(increase)` or
:icon:`fa-caret-down` :guilabel:`(decrease)` icons as needed. Each radio button can be
repositioned independently by clicking and dragging it.
- :guilabel:`Selection`: To define options, type each option on a new line in the
:guilabel:`Options` text box, ensuring you have pressed `Enter` after each option. To delete
options, remove the corresponding text from the text box.
- :guilabel:`Strikethrough`: To use this field to allow signers to reject a certain phrase or
phrases, position the field on top of the relevant text by dragging it. Ensure that the field is
not :guilabel:`Mandatory` to allow the signer to freely decide which phrases to reject.
Once a field has been added, it is possible to:
- **Reposition the field**: Hover over the field until the :icon:`fa-hand-paper-o`
:guilabel:`(hand)` icon appears, then click and drag the field to the desired position.
- **Change the size of the field**: Hover over the bottom edge, right edge, or bottom-right corner
to reveal resize arrows. Drag the vertical or horizontal resize arrows to adjust the height or
width, respectively, or drag the diagonal resize arrows to scale both dimensions
simultaneously.
- **Modify certain attributes of the field**: Click on the field to open it, make the necessary
changes, then click :guilabel:`Save`.
Depending on the :ref:`field type <sign/fields/field-types>`, attributes that can be modified
include:
- the :guilabel:`Placeholder` text, i.e., the temporary text the signer sees before starting to
complete the field
- whether or not a field is a :guilabel:`Mandatory field`
- whether or not a field that is :ref:`configured to be auto-completed
<sign/fields/auto-fill>` is :guilabel:`Read-only`
- the horizontal alignment of the text within the field
.. note::
Any changes made to the attributes of a field after adding the field to a document apply *to
the current document only*. To make permanent changes to the field, :ref:`edit the field
<sign/fields/create-edit-fields>`.
- **Remove a field**: Click on the field to open it, then click :icon:`fa-trash` :guilabel:`(remove)`
to remove the field from the document.
- **Duplicate a field**: Click on the field to open it, then click :icon:`fa-clone`
:guilabel:`(duplicate)` to create a copy of the field. Alternatively, use your regular keyboard
shortcuts to copy and paste a field.
.. tip::
To reposition or duplicate multiple fields at once, select the fields by drawing a selection
area around them with your mouse. Then:
- to reposition the fields, hover over one of the selected fields until the
:icon:`fa-hand-paper-o` :guilabel:`(hand)` icon appears, then click and drag the fields to
the desired position.
- to copy and paste the fields, use your regular keyboard shortcut to copy the fields, place
your cursor where you want to paste the fields, then use your regular keyboard shortcut to
paste them.
.. _sign/prepare-document/create-envelope:
Document envelopes
------------------
A document envelope allows for multiple documents to be signed at the same time or sent for signing
in a single signature request. It is possible to create a one-off document envelope or a
:ref:`template <sign/request-signatures/templates>` based on a document envelope.
To create a document envelope *during* the initial file upload, after clicking
:guilabel:`Upload PDF`, select the relevant `.pdf` documents and click :guilabel:`Open`.
.. tip::
If, when creating a document envelope via the Sign app, you need to include one document saved
in the Documents app, import that document *before* adding subsequent documents. To do so,
click the :icon:`fa-cog` :guilabel:`(Actions)` icon beside the name of the view, then
:guilabel:`Import from Documents`.
To add one or more documents *after* the initial file upload:
#. Open the initial document or document envelope, then click :guilabel:`Add` in the
:guilabel:`Documents` section.
#. Select the relevant `.pdf` document(s), then click :guilabel:`Open`.
.. tip::
To change the order in which documents are presented to the signer, click the
:icon:`fa-ellipsis-v` :guilabel:`(vertical ellipsis)` icon beside the relevant document in the
:guilabel:`Documents` section, then click :icon:`fa-arrow-up` :guilabel:`Move Up` or
:icon:`fa-arrow-down` :guilabel:`Move Down` as appropriate. To remove a document from the
envelope, click :icon:`fa-trash` :guilabel:`Delete`.
.. image:: request_signatures/multiple-documents.png
:alt: Document envelope with two documents
.. _sign/prepare-document/signers:
Add and configure signers
-------------------------
By default, a document or document envelope has one signer. Additional :ref:`signers can be added
<sign/prepare-document/add-signers>` and :ref:`advanced configuration can be defined
<sign/prepare-document/signer-settings>` for one or more signers.
.. _sign/prepare-document/add-signers:
Add signers
~~~~~~~~~~~
To add additional signers to a document or document envelope:
#. Open the document or document envelope, then click :guilabel:`Add` in the :guilabel:`Signers`
section.
#. Optionally, edit the name of the signer by hovering over the name, e.g., `Signer 2`, clicking the
:icon:`fa-pencil` :guilabel:`(pencil)` icon, then typing the new name.
.. image:: request_signatures/edit-signer.png
:alt: Editing the name of signers
.. tip::
- Each signer is assigned a unique color and all fields associated with a specific signer have
the same background color.
- When a document or document envelope has multiple signers, it is possible to define the
order in which signers receive and sign when :ref:`configuring the signature request
<sign/configure-signature-request>`.
.. _sign/prepare-document/signer-settings:
Signer settings
~~~~~~~~~~~~~~~
To define additional configuration for signers, click the :icon:`fa-ellipsis-v` :guilabel:`(vertical
ellipsis)` icon on the row of the signer.
For each signer, the following options are available:
- :guilabel:`Authentication`: Require the signer to :ref:`authenticate using a specific
authentication method <sign/security/authentication>`.
- :guilabel:`Can delegate`: Enable this option to allow the signer to delegate signing to another
person. The person to whom signing is delegated then signs the document in their own name.
- :guilabel:`Assign to`: Assign a specific contact as signer by selecting them from the dropdown.
.. _sign/prepare-document/add-tags:
Add tags
--------
To add :ref:`tags <sign/configuration/tags>` to a document or document envelope *before sending a
signature request*, select the relevant tags from the :guilabel:`Tags` dropdown in the upper-right
corner above the document.
Tags can also be added to, or removed from, a document :ref:`after a signature request has been sent
<sign/request-signatures/manage-update-tags>`.
.. _sign/configure-signature-request:
Configure the signature request
===============================
After :ref:`preparing a one-off document or document envelope for signing <sign/prepare-document>`
or selecting a template, click :guilabel:`Send`, then configure the signature request in the
:guilabel:`New Signature Request` window.
For each signer, select a contact or type an email address. Optionally, enable :ref:`Signing Order
<sign/configure-request/signing-order>` to control the order in which the document or document
envelope is signed.
It is also possible to:
- :ref:`set a Valid Until date <sign/configure-request/validity>` after which the signature request
expires
- :ref:`set Reminders <sign/configure-request/validity>` to be sent at fixed intervals
- enable :guilabel:`Add certificate on each page` to add the reference of the :ref:`certificate of
completion <sign/security/certificate-of-completion>` to each page of the document(s)
- have one or more parties notified when the document is fully signed by adding the relevant
contact(s) or email address(es) in the :guilabel:`CC` field
- add a message to the signature request email
.. tip::
When :ref:`creating a template <sign/request-signatures/templates>`, it is
possible to define a default message to be added to the signature request; this can still be
edited before sending.
- add attachments to the signature request via the :icon:`fa-paperclip` :guilabel:`(paperclip)` icon
at the bottom of the window, or, to add an attachment saved in the Documents app, click the
Documents app icon
- schedule the sending of the signature request via the :icon:`fa-clock-o` :guilabel:`(clock)` icon
.. _sign/configure-request/signing-order:
Signing order
-------------
When a document or document envelope needs to be signed by multiple parties, and the order of
signing is important, it is possible to define the :guilabel:`Signing order` when configuring the
signature request. This controls the order in which your recipients receive the document(s) for
signature.
To define a signing order:
#. In the :guilabel:`New Signature Request` window, enable :guilabel:`Signing Order`.
#. Change the order by editing the number beside each signer, e.g., changing a `3` to a `2` in the
first column.
The signer indicated in position `1` receives the signature request first, and each recipient
receives the request only once the previous recipient has signed the document.
.. example::
In the example, the AB & Co Legal contact will receive the signature request first, the AB & Co
CEO second, and Mitchell Admin last.
.. image:: request_signatures/signing-order.png
:alt: Configuring signing order by editing the signer number
:scale: 80%
.. _sign/configure-request/validity:
Validity dates and reminders
----------------------------
For documents that need to be signed within a certain timeframe, you can indicate the last possible
signing date using the :guilabel:`Valid Until` field when configuring the signature request. After
this date, the document is no longer accessible via the link in the signature request email.
.. image:: request_signatures/reminders.png
:alt: Set the number of days between reminders
If the signature request does not expire, leave this field blank.
.. note::
When using a :ref:`template <sign/request-signatures/templates>` for which a default validity
period has been defined, the :guilabel:`Valid Until` date is updated automatically in the
signature request email; this date can be changed if desired.
To set automatic reminders, enable :guilabel:`Reminders`, then define the interval, in days, at
which reminders should be sent until the document has been signed by the signer.
.. _sign/request-signatures/manage:
Manage signature requests and signed documents
==============================================
All signature requests that have been sent are visible in :menuselection:`Sign --> Documents --> All
Documents`. The list view and Kanban view offer different possiblities:
In the list view:
- see the overall :guilabel:`Status` of the signature request, e.g., :guilabel:`To Sign`,
:guilabel:`Signed`, :guilabel:`Cancelled`
- :icon:`fa-refresh` :guilabel:`Resend` a signature request manually
- :icon:`fa-pencil-square-o` :guilabel:`Sign` a document or document envelope
- :icon:`fa-download` :guilabel:`Download` the fully signed document(s)
- for a cancelled signature request, click :icon:`fa-info` :guilabel:`Details` to see the details of
the cancelled request
.. tip::
Click the :icon:`oi-settings-adjust` :guilabel:`(slider)` icon in the upper-right corner to see
more information for each request, such as each document included, tags, and, in the case of
documents sent using a template, the :doc:`Odoo model <../../studio/models_modules_apps>` the
template is linked to.
In the Kanban view:
- see the status of individual signers, per signature request:
- when a signer has fully signed the document(s), the checkbox is ticked, the signer's name
appears in green, and the date of the signature is added after the name
- when a signature request is cancelled, the signers name appears in red with a :icon:`fa-times`
:guilabel:`(cross)` beside it, followed by the date on which the signature request was cancelled
- see any tags added to the document(s)
- click the :icon:`fa-clock-o` :guilabel:`(clock)` icon to schedule an activity related to the
signature request
- click the :icon:`fa-ellipsis-v` :guilabel:`(vertical ellipsis)` icon in the top-right of the card
to reveal more options:
- see the :guilabel:`Details` of the signature request, including the expiry date, if relevant,
whether or not reminders have been set, activity logs, and more
- :guilabel:`Cancel` a signature request that *has not been* fully signed
- :guilabel:`Archive` a signature request
- select a color dot to add a a colored bar to the left side of a card to visually differentiate
it
.. _sign/request-signatures/manage-update-tags:
Update the tags of a sent or signed document
--------------------------------------------
To add tags to, or remove tags from, a document or document envelope for which a signature request
has already been sent:
#. Go to :menuselection:`Sign --> Documents --> All Documents`, then switch to the Kanban view.
#. Hover over the relevant card, click the :icon:`fa-ellipsis-v` :guilabel:`(vertical ellipsis)` in
the top-right corner of the card, then click :guilabel:`Details`.
#. Beside the :guilabel:`Tags` field, add new tags by selecting them from the dropdown or delete
tags by clicking the :icon:`fa-times` :guilabel:`(cross)` on the tag.

BIN
content/applications/productivity/sign/request_signatures/edit-signer.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 3.2 KiB

BIN
content/applications/productivity/sign/request_signatures/multiple-documents.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 7.0 KiB

BIN
content/applications/productivity/sign/request_signatures/reminders.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 3.6 KiB

BIN
content/applications/productivity/sign/request_signatures/signing-order.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 6.7 KiB

BIN
content/applications/productivity/sign/request_signatures/visualization-mode.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 3.9 KiB

265
content/applications/productivity/sign/security_authentication.rst Normal file
View File

@@ -0,0 +1,265 @@
===========================
Security and authentication
===========================
Various security features are integrated into Odoo Sign by default, such as:
- :ref:`email verification <sign/security/authentication>`, whereby the signer receives a unique
link to the document or :ref:`envelope of multiple documents
<sign/prepare-document/create-envelope>` via an email sent directly to their email address
- a :ref:`signatory hash <sign/security/hash>` that links the signer's identity to the exact content
of the document at the moment of signing
- a :ref:`certificate of completion <sign/security/certificate-of-completion>` that provides
details of the signing process
Additional security can be ensured by:
- requiring other methods of :ref:`secured identification <sign/security/authentication>`, such as
SMS, Aadhaar eSign (India) or itsme® (European Union, United Kingdom, Norway and Iceland)
- using a :ref:`cryptographic signature <sign/security/cryptographic>` by means of a digital
certificate issued by a Certificate Authority (CA) or generated yourself
.. _sign/security/hash:
Signatory hash
==============
When someone signs a document, a *hash*, i.e., a unique digital signature of the operation, is
generated to link the signer's identity to the exact content of the document at the moment of
signing. This process guarantees that any changes made after a signature has been added can be
easily detected, maintaining the document's authenticity and integrity throughout its lifecycle.
A visual security frame displaying the beginning of the hash is added to signatures and initials.
.. image:: security_authentication/hash-frame.png
:alt: Adding the visual security frame to a signature.
:scale: 80%
.. tip::
Internal users can hide or show it by turning the :guilabel:`Frame` option on or off when
:ref:`adding their signature or initials to the document
<sign/sign-document/initials-signature>`.
The signatory hash of each signer is provided on the :ref:`certificate of completion
<sign/security/certificate-of-completion>` that is generated when a document is fully signed.
.. _sign/security/certificate-of-completion:
Certificate of completion
=========================
Each time a document or document envelope is fully signed, i.e., completed and signed by all
signers, a certificate of completion is generated and sent to all signers via email, along with the
fully signed document(s).
.. note::
When documents are :doc:`signed via an Odoo record's chatter <sign_document>`, or when a
signature request initiated from an Odoo record is fully completed (whether a :ref:`one-off
document <sign/request-signatures/one-off-record>` or :ref:`using a template
<sign/templates/use-odoo-record>`), the certificate of completion is also added to the chatter,
along with the fully signed document(s).
This certificate contains details of the signing process that support the validity of the signatures
and provide proof that the document has not been altered after signing.
.. image:: security_authentication/certificate-of-completion.png
:alt: Certificate of completion
:scale: 60%
The following information is provided:
- :guilabel:`Document Details`, which include when the signature request was created and by who,
the file name of the `.pdf` document or documents that were signed, the number of signers, and a
unique reference hash that can optionally be added to each page of a signed document.
- A list of :guilabel:`Participants` who have signed the document, including the verification method
and a unique :ref:`signatory hash <sign/security/hash>` that ensures traceability and integrity.
- Timestamped, IP, and geographically traceable records of :guilabel:`Signing Events` and
:guilabel:`Access Logs`.
As well as being sent via email, a signed document's certificate of completion can be downloaded at
any time via the Sign app:
#. Go to :menuselection:`Sign --> All Documents` and switch to the Kanban view.
#. Click the :icon:`fa-ellipsis-v` :guilabel:`(vertical ellipsis)` icon in the top-right of the card
of a document, then click :guilabel:`Details`.
#. Click :guilabel:`Download` then :guilabel:`Certificate`.
.. _sign/security/authentication:
Secured identification
======================
When a signature request is sent via email, the signer accesses the document by clicking on a unique
link contained in the email. This default verification step serves as confirmation that the signer
controls the email address associated with the signature request.
It is also possible to require additional authentication for one or more signers via one of the
following methods:
- :ref:`Unique Code via SMS <sign/security/authentication-sms>`
- :ref:`Via Aadhar eSign <sign/security/authentication-aadhaar>` (available in India)
- :ref:`Via itsme® <sign/security/authentication-itsme>` (available in the European Union, the
United Kingdom, Norway and Iceland)
.. important::
These authentication methods require :ref:`buying credits <in_app_purchase/credits>`. If you do
not have any credits left, authentication is skipped.
.. seealso::
- :doc:`In-App Purchase (IAP) <../../essentials/in_app_purchase>`
- :doc:`SMS pricing and FAQ <../../marketing/sms_marketing/pricing_and_faq>`
.. _sign/security/authentication-sms:
Unique code via SMS
-------------------
With authentication via SMS, signers receives a one-time code by SMS, which they enter when
prompted during the signing process to identify themselves.
This feature is enabled by default in Sign's :ref:`general settings <sign/configuration/settings>`.
.. note::
Before being able to send SMS messages, you need to register your mobile phone number. To do so,
go to :menuselection:`Sign --> Configuration --> Settings` and, under :guilabel:`Authenticate by
SMS`, click :guilabel:`Manage Service & Buy Credits`. On the next screen, click
:icon:`fa-arrow-right` :guilabel:`Register` then proceed to register your phone number.
To require signer authentication via SMS:
#. With the document or document envelope open, in the left panel, click the :icon:`fa-ellipsis-v`
:guilabel:`(vertical ellipsis)` icon next to the relevant signer, then click :guilabel:`Edit`.
#. In the pop-up, select :guilabel:`Unique Code via SMS` as :guilabel:`Authentication`.
#. Click :guilabel:`Save`.
Upon signing the document, an extra :guilabel:`Final Validation` window is displayed where the
signer enters first their phone number, then the one-time code received.
.. image:: security_authentication/sms-verification.png
:alt: Pop-up where signer enters phone number and one-time code
.. _sign/security/authentication-aadhaar:
Aadhaar eSign
-------------
Aadhaar eSign allows signers in **India** to digitally sign documents using their Aadhaar number and
OTP (One Time Password) verification. This provides a secure and legally valid way to complete
signatures directly within Odoo Sign.
.. important::
In Odoo Sign, Aadhaar eSign can only be used for signature requests containing a single document.
Additionally, only one signer per document can be required to authenticate via Aadhaar eSign, and
this party must be the last party to sign the document.
This method is therefore most suitable for a single document with a single signer, or where the
first signer is the party sending the signature request.
To enable authentication with Aadhaar eSign, go to :menuselection:`Sign --> Configuration -->
Settings`, then enable :guilabel:`Sign with Aadhar eSign`.
To require signer authentication via Aadhaar eSign:
#. With the document or document envelope open, in the left panel, click the :icon:`fa-ellipsis-v`
:guilabel:`(vertical ellipsis)` icon next to the relevant signer.
#. In the pop-up, select :guilabel:`Via Aadhaar eSign` under :guilabel:`Authentication`.
#. Click :guilabel:`Save`.
Upon signing the document, an extra :guilabel:`Final verification` page is displayed where
authentication via Aadhaar is required.
.. note::
The digital certification from eMudhra is available in the downloaded document.
.. _sign/security/authentication-itsme:
Itsme®
------
Itsme® authentication allows signers in **the European Union**, **the United Kingdom**, **Iceland**
and **Norway** to prove their identity.
To enable authentication with itsme®, go to :menuselection:`Sign --> Configuration
--> Settings`, then enable :guilabel:`Identify with itsme®`.
To require signer authentication via itsme®:
#. With the document or document envelope open, in the left panel, click the :icon:`fa-ellipsis-v`
:guilabel:`(vertical ellipsis)` icon next to the relevant signer.
#. In the pop-up, select :guilabel:`Via itsme®` under :guilabel:`Authentication`.
#. Click :guilabel:`Save`.
Upon signing the document, an extra :guilabel:`Final verification` page is displayed where
authentication via itsme® is required.
.. _sign/security/cryptographic:
Cryptographic signature
=======================
Odoo Sign allows you to use your own digital certificate to sign documents. A digital certificate
uses cryptography, which relies on secure mathematical algorithms, to ensure a signed document's
authenticity and integrity.
Authenticity is ensured as your verified identity is linked to the signature, while integrity is
ensured as the document cannot be altered without invalidating, or 'breaking', the cryptographic
signature.
A digital certificate is stored in a file such a `.p12` or `.pfx` file. This is a secure container
that contains:
- a *private key* that applies a unique cryptographic signature to a document; and
- identifying information about the signer and a *public key* that is shared with the recipient for
signature validation
The file is always protected by a password, which is never stored in plain text. Odoo uses this
password to decrypt the private key at the moment a document is signed.
.. _sign/security/cryptographic-obtain-create:
Obtain or create a digital certificate
--------------------------------------
Most businesses obtain their digital certificate from a trusted Certificate Authority (CA). In many
cases, the :abbr:`CA (Certificate Authority)` provides the `.p12` or `.pfx` file directly, along
with its password.
It is also possible to generate a certificate yourself. `Adobe Acrobat
<https://helpx.adobe.com/be_en/acrobat/desktop/protect-documents/manage-digital-ids/create-self-signed-id.html>`_
and `Microsoft <https://support.microsoft.com/en-us/office/obtain-a-digital-certificate-and-create-a-digital-signature-e3d9d813-3305-4164-a820-2e063d86e512>`_,
for example, allow the creation of digital certificates.
.. note::
Self-generated digital certificates do not provide the same level of trust as a certificate
obtained from a trusted :abbr:`CA (Certificate Authority)`. However, they can be useful if you
need to provide a digital signature urgently or for less official situations.
Once you have obtained or created a digital certificate, you can then :ref:`upload it to your Odoo
database <sign/security/cryptographic-upload>`.
.. _sign/security/cryptographic-upload:
Upload a digital certificate in Odoo
------------------------------------
To upload a digital certificate in Odoo:
#. Go to :menuselection:`Sign --> Configuration --> Settings`.
#. Under :guilabel:`Cryptographic signature`, click the :guilabel:`Signing certificate` dropdown and
click :guilabel:`Create`.
#. In the pop-up, complete the relevant fields:
- :guilabel:`Name`: Enter a name for the certificate.
- :guilabel:`Certificate`: Click :guilabel:`Upload your file`, then select the relevant
certificate file in `.p12` or `.pfx` format.
- :guilabel:`Certificate Password`: Enter the certificate password for the uploaded file; it must
be minimum six characters. This password is used to decrypt the private key during the signing
process.
#. Click :guilabel:`Save`.
.. note::
- After the certificate has been uploaded, two read-only fields are auto-completed: the
:guilabel:`Validity` date, i.e., the date on which it starts to be valid, and the
:guilabel:`Serial number` that will be added to signed documents.
- In a multi-company environment, one certificate can be uploaded per company.

BIN
content/applications/productivity/sign/security_authentication/certificate-of-completion.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 64 KiB

BIN
content/applications/productivity/sign/security_authentication/hash-frame.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 15 KiB

0
content/applications/productivity/sign/sms-verification.png → content/applications/productivity/sign/security_authentication/sms-verification.png
View File

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 4.5 KiB

After

Width:  |  Height:  |  Size: 4.5 KiB

BIN
content/applications/productivity/sign/sign-hash.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 34 KiB

197
content/applications/productivity/sign/sign_document.rst Normal file
View File

@@ -0,0 +1,197 @@
===============
Sign a document
===============
Depending on the situation, you may need to sign:
- a single document or :ref:`envelope of multiple documents
<sign/prepare-document/create-envelope>` that you or another person :ref:`prepared for electronic
signature using Odoo Sign <sign/sign-document/signature-request>`; or
- one or more `.pdf` documents that have :ref:`not been prepared for electronic signature
<sign/sign-document/pdf-document>` by the sender
.. _sign/sign-document/signature-request:
Sign a document prepared using Odoo Sign
========================================
Documents prepared using Odoo Sign contain a series of fields to indicate what information must be
completed by the signer(s).
.. note::
Fields with a colored background are mandatory, while fields with a dotted border and a white
background are optional. Fields that have been :ref:`auto-completed
<sign/sign-document/auto-complete>` and set to read-only have a solid border and a white
background; these fields are populated as soon as the document is opened.
.. example::
In the example below, the :guilabel:`Name` and :guilabel:`Signature` fields are mandatory,
while the :guilabel:`Job title` field is optional. The :guilabel:`Email` field has been
auto-completed and set to read-only.
.. image:: sign_document/field-characteristics.png
:alt: Examples of mandatory, optional, and read-only fields
:scale: 80%
To sign a document prepared using Odoo Sign:
#. Click on each field to enter the requested information, or, to be guided through the fields in
order, click the :guilabel:`Click to start` arrow, click on the indicated field to enter the
requested information, then use the arrows to progress through the document.
.. note::
- Fields set to be auto-completed but *not* read-only are populated when clicked or when
arriving at the field using the navigational arrows; these fields can still be edited.
- When completing an :guilabel:`Initial` or :guilabel:`Signature` field, you may need to
:ref:`define the visual representation of your initials/signature
<sign/sign-document/initials-signature>`.
#. When all required fields have been completed, click :guilabel:`Validate & Send Completed
Document` at the bottom of the document.
If there are :ref:`multiple documents <sign/prepare-document/create-envelope>` to sign, click
:guilabel:`Next` at the bottom of the document, enter the requested information for the next and
any subsequent documents. Once all documents have been signed, click :guilabel:`Validate & Send
Completed Document`.
After signing the document:
- If other signers still need to sign the document, a message informs you of this. Click
:guilabel:`Next signatory`.
- If you are the only or last signer, you can :guilabel:`Download` the document directly.
- If you are an internal user, a list shows any other documents awaiting your signature; you
can then :guilabel:`Sign` or :guilabel:`View` the documents.
Once a document or document envelope has been fully signed, i.e., signed by all signers, the signed
document(s) and the :ref:`certificate of completion <sign/security/certificate-of-completion>` are
sent via email to the signers and to any other parties defined by the sender.
.. _sign/sign-document/auto-complete:
Auto-completed fields
---------------------
In Odoo Sign, certain field types can be :ref:`configured to be auto-completed
<sign/fields/auto-fill>` using data about the signer, e.g., name or email address, that is stored in
the sender's Odoo database.
Depending on the configuration, these fields can be read-only or can still be edited after
auto-completion.
.. _sign/sign-document/initials-signature:
Define initials and signature
-----------------------------
If you are an:
- **internal user**, the first time you use Odoo Sign to complete an :guilabel:`Initial` or
:guilabel:`Signature` field, you need to define how your initials or signature appear. Thereafter,
your initials/signature are stored for future use.
- **external user**, you need to define how your initials or signature appear the first time you
complete such a field in a document or document envelope prepared using Odoo Sign.
To define how your initials/signature should appear after clicking the relevant field in a document:
#. In the :guilabel:`Adopt Your Signature` window, enter your full name.
#. Choose whether to:
- use the :guilabel:`Auto`-generated initials/signature, and select your desired font from the
:icon:`fa-font` :icon:`fa-caret-down` :guilabel:`(font)` dropdown;
- :guilabel:`Draw` your own initials/signature using your mouse; or
- :guilabel:`Load` an image file of your initials/signature.
.. image:: sign_document/hash-frame.png
:alt: Options for adopting a signature plus hash frame option
:scale: 80%
.. tip::
Internal users can choose to keep or turn off the security :guilabel:`Frame` that contains the
beginning of the :ref:`signatory hash <sign/security/hash>`, i.e., the unique digital
signature of the operation.
#. Click :guilabel:`Sign all` to add the initials/signature to all instances in the current document
or click :guilabel:`Sign` to only add the initials/signature to the current instance in the
current document.
If there are multiple documents to sign within the same document envelope, the defined
initials/signature can thereafter be added directly by clicking the relevant field.
.. _sign/sign-document/pdf-document:
Sign an unprepared .pdf document
================================
When you are asked to sign a `.pdf` document that has not been prepared for electronic signature,
this typically involves adding your name, date, and signature to the document. Depending on how the
document has been shared with you, you can sign the document electronically in Odoo:
- from the Sign app
- from a record's chatter
- from the :doc:`Documents <../documents>` app
.. tip::
To be able to sign documents via the Documents app, ensure that :ref:`the Sign action
is enabled <sign/sign-document/enable-sign-option>` for the folder in which the document is
stored.
To sign a document in Odoo:
#. Open the document:
- From the Sign app: Go to :menuselection:`Sign --> Documents --> My Documents` or
:menuselection:`--> All Documents`, click :guilabel:`Upload PDF`, select the relevant `.pdf`
document(s), then click :guilabel:`Open`.
- From a record's chatter or from the Documents app: Click on the `.pdf` document to open it,
then click :guilabel:`Sign` in the upper-right corner.
#. :ref:`Add the relevant fields <sign/prepare-document/add-fields>` to the document, then click
:guilabel:`Sign Now`.
#. In the :guilabel:`New Signature Request` window, ensure you are selected as the signer.
Optionally:
- to add the reference of the :ref:`certificate of completion
<sign/security/certificate-of-completion>` to each page of the document(s), enable
:guilabel:`Add certificate on each page`
- to have one or more parties notified when the document is fully signed, add the relevant
contact(s) or email address(es) in the :guilabel:`CC` field
#. Click :guilabel:`Sign Now`.
.. tip::
When signing a document that contains only :ref:`auto-completed fields
<sign/fields/auto-fill>`, e.g., name, email, etc., click :guilabel:`Download` to immediately
download a fully signed version, without having to complete the fields manually.
#. :ref:`Complete and sign the document(s) <sign/sign-document/signature-request>`.
The signed document(s) and the certificate of completion are sent to you, and to any contacts
mentioned in the :guilabel:`CC` field, via email; to download the signed document immediately, click
:guilabel:`Download`.
.. note::
- After signing, a list of any other documents awaiting your signature is shown. You can then
:guilabel:`Sign` or :guilabel:`View` the documents.
- If the document was signed from a record's chatter, the signed document and the related
certificate of completion are added to the chatter.
.. _sign/sign-document/enable-sign-option:
Enable the Sign option in Documents
===================================
Enabling the :guilabel:`Sign` option for a :ref:`folder or sub-folder in the Documents app
<documents/folders>` allows any document saved in that folder to be signed without having to leave
the Documents app.
.. note::
This option can be particularly useful if you receive documents directly in Documents folders
thanks to :ref:`email aliases set on certain folders <documents/email-aliases>`, e.g., sales
contracts sent to the alias `salescontracts@yourcompany.com`.
To enable the :guilabel:`Sign` option:
#. In the Documents app, with the relevant folder or sub-folder open, click the :icon:`fa-cog`
:guilabel:`(Actions)` icon beside the name of the folder.
#. Click :icon:`fa-cog` :menuselection:`Actions on Select -->` :icon:`fa-caret-right`
:menuselection:`Sign`.

BIN
content/applications/productivity/sign/sign_document/field-characteristics.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 6.5 KiB

BIN
content/applications/productivity/sign/sign_document/hash-frame.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 15 KiB

BIN
content/applications/productivity/sign/signature-status.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 6.2 KiB

BIN
content/applications/productivity/sign/specify-signing-order.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 4.0 KiB

BIN
content/applications/productivity/sign/tip-placeholder.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 13 KiB

132
content/applications/productivity/sign/validity.rst Normal file
View File

@@ -0,0 +1,132 @@
=================================
Validity of electronic signatures
=================================
The legal validity of electronic signatures generated by Odoo depends on your country's legislation.
Documents signed using the Sign app are considered legally valid in the :ref:`European Union
<sign/validity/eu>` and the :ref:`United States of America <sign/validity/united-states>`. They also
meet the requirements for electronic signatures in
:ref:`most countries <sign/validity/other-countries>`.
Companies doing business abroad should also consider other countries' electronic signature laws.
.. important::
The below information has no legal value; it is only provided for general informational purposes.
As laws governing electronic signatures rapidly evolve, we cannot guarantee that all information
is up-to-date. We advise contacting a local attorney for legal advice regarding electronic
signature compliance and validity.
.. _sign/validity/eu:
European Union
--------------
The `eIDAS regulation <http://data.europa.eu/eli/reg/2014/910/oj>`_ establishes the framework for
electronic signatures in the `27 member states of the European Union
<https://europa.eu/european-union/about-eu/countries_en>`_. It distinguishes three types of
electronic signatures:
#. Simple electronic signatures
#. Advanced electronic signatures
#. Qualified electronic signatures
Odoo generates the first type, **simple electronic signatures**; these signatures are legally valid
in the EU, as stated in the eIDAS regulation.
Electronic signatures may not be automatically recognized as valid. You may need to bring
supporting evidence of a signature's validity. While the Sign app provides a simple electronic
signature, some supporting evidence is automatically collected during the signature process, such
as:
#. Email validation and SMS validation (if enabled)
#. Strong identity proof through itsme® (if enabled)
#. Timestamped, IP and geographically traceable access logs to the documents and their associated
signatures
#. Document traceability and inalterability (any alteration made to a signed document is detected by
Odoo with the use of cryptographic proofs)
.. seealso::
:doc:`Documentation for Germany <validity/germany>`
.. _sign/validity/united-states:
United States of America
------------------------
The `ESIGN Act (Electronic Signatures in Global and National Commerce Act)
<https://www.fdic.gov/regulations/compliance/manual/10/X-3.1.pdf>`_, at the interstate and
international levels, and the `UETA (Uniform Electronic Transactions Act)
<https://www.uniformlaws.org/committees/community-home/librarydocuments?communitykey=2c04b76c-2b7d-4399-977e-d5876ba7e034&tab=librarydocuments>`_,
at the state level, provide the legal framework for electronic signatures. Note that `Illinois
<https://www.ilga.gov/legislation/ilcs/ilcs5.asp?ActID=89&>`_ and `New York
<https://its.ny.gov/electronic-signatures-and-records-act-esra>`_ have not adopted the UETA, but
similar acts instead.
Overall, to be recognized as valid, electronic signatures have to meet five criteria:
#. The signer must show a clear **intent to sign**. For example, using a mouse to draw a signature
can show intent. The signer must also have the option to opt out of the electronic document.
#. The signer must first express or imply their **consent to conduct business electronically**.
#. **The signature must be clearly attributed**. In Odoo, metadata, such as the signer's IP address,
is added to the signature, which can be used as supporting evidence.
#. **The signature must be associated with the signed document**, for example, by keeping a record
detailing how the signature was captured.
#. Electronically signed documents need to be **retained and stored** by all parties involved; for
example, by providing the signer either a fully-executed copy or the possibility to download a
copy.
.. _sign/validity/other-countries:
Other countries
---------------
- :doc:`Algeria <validity/algeria>`
- :doc:`Angola <validity/angola>`
- :doc:`Argentina <validity/argentina>`
- :doc:`Australia <validity/australia>`
- :doc:`Azerbaijan <validity/azerbaijan>`
- :doc:`Bangladesh <validity/bangladesh>`
- :doc:`Brazil <validity/brazil>`
- :doc:`Canada <validity/canada>`
- :doc:`Chile <validity/chile>`
- :doc:`China <validity/china>`
- :doc:`Colombia <validity/colombia>`
- :doc:`Dominican Republic <validity/dominican_republic>`
- :doc:`Ecuador <validity/ecuador>`
- :doc:`Egypt <validity/egypt>`
- :doc:`Ethiopia <validity/ethiopia>`
- :doc:`Guatemala <validity/guatemala>`
- :doc:`Hong Kong <validity/hong_kong>`
- :doc:`India <validity/india>`
- :doc:`Indonesia <validity/indonesia>`
- :doc:`Iran <validity/iran>`
- :doc:`Iraq <validity/iraq>`
- :doc:`Israel <validity/israel>`
- :doc:`Japan <validity/japan>`
- :doc:`Kazakhstan <validity/kazakhstan>`
- :doc:`Kenya <validity/kenya>`
- :doc:`Kuwait <validity/kuwait>`
- :doc:`Malaysia <validity/malaysia>`
- :doc:`Mexico <validity/mexico>`
- :doc:`Morocco <validity/morocco>`
- :doc:`New Zealand <validity/new_zealand>`
- :doc:`Nigeria <validity/nigeria>`
- :doc:`Norway <validity/norway>`
- :doc:`Oman <validity/oman>`
- :doc:`Pakistan <validity/pakistan>`
- :doc:`Peru <validity/peru>`
- :doc:`Philippines <validity/philippines>`
- :doc:`Qatar <validity/qatar>`
- :doc:`Russia <validity/russia>`
- :doc:`Saudi Arabia <validity/saudi_arabia>`
- :doc:`Singapore <validity/singapore>`
- :doc:`South Africa <validity/south_africa>`
- :doc:`South Korea <validity/south_korea>`
- :doc:`Switzerland <validity/switzerland>`
- :doc:`Thailand <validity/thailand>`
- :doc:`Turkey <validity/turkey>`
- :doc:`Ukraine <validity/ukraine>`
- :doc:`United Arab Emirates <validity/united_arab_emirates>`
- :doc:`United Kingdom <validity/united_kingdom>`
- :doc:`Uzbekistan <validity/uzbekistan>`
- :doc:`Vietnam <validity/vietnam>`

2
content/applications/productivity/sign/algeria.rst → content/applications/productivity/sign/validity/algeria.rst
View File

@@ -4,7 +4,7 @@
Odoo Sign legality in Algeria
=============================
:doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant
:doc:`Odoo Sign <../../sign>` is your trusted partner for secure, efficient, and legally compliant
electronic signatures in Algeria.
Legal framework for electronic signatures in Algeria

2
content/applications/productivity/sign/angola.rst → content/applications/productivity/sign/validity/angola.rst
View File

@@ -4,7 +4,7 @@
Odoo Sign legality in Angola
============================
:doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant
:doc:`Odoo Sign <../../sign>` is your trusted partner for secure, efficient, and legally compliant
electronic signatures in Angola.
Legal framework for electronic signatures in Angola

2
content/applications/productivity/sign/argentina.rst → content/applications/productivity/sign/validity/argentina.rst
View File

@@ -4,7 +4,7 @@
Odoo Sign legality in Argentina
===============================
:doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant
:doc:`Odoo Sign <../../sign>` is your trusted partner for secure, efficient, and legally compliant
electronic signatures in Argentina.
Legal framework for electronic signatures in Argentina

2
content/applications/productivity/sign/australia.rst → content/applications/productivity/sign/validity/australia.rst
View File

@@ -4,7 +4,7 @@
Odoo Sign legality in Australia
===============================
:doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant
:doc:`Odoo Sign <../../sign>` is your trusted partner for secure, efficient, and legally compliant
electronic signatures in Australia.
Legal framework for electronic signatures in Australia

2
content/applications/productivity/sign/azerbaijan.rst → content/applications/productivity/sign/validity/azerbaijan.rst
View File

@@ -4,7 +4,7 @@
Odoo Sign legality in Azerbaijan
================================
:doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant
:doc:`Odoo Sign <../../sign>` is your trusted partner for secure, efficient, and legally compliant
electronic signatures in Azerbaijan.
Legal framework for electronic signatures in Azerbaijan

2
content/applications/productivity/sign/bangladesh.rst → content/applications/productivity/sign/validity/bangladesh.rst
View File

@@ -4,7 +4,7 @@
Odoo Sign legality in Bangladesh
================================
:doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant
:doc:`Odoo Sign <../../sign>` is your trusted partner for secure, efficient, and legally compliant
electronic signatures in Bangladesh.
Legal framework for electronic signatures in Bangladesh

2
content/applications/productivity/sign/brazil.rst → content/applications/productivity/sign/validity/brazil.rst
View File

@@ -4,7 +4,7 @@
Odoo Sign legality in Brazil
============================
:doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant
:doc:`Odoo Sign <../../sign>` is your trusted partner for secure, efficient, and legally compliant
electronic signatures in Brazil.
Legal framework for electronic signatures in Brazil

2
content/applications/productivity/sign/canada.rst → content/applications/productivity/sign/validity/canada.rst
View File

@@ -4,7 +4,7 @@
Odoo Sign legality in Canada
============================
:doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant
:doc:`Odoo Sign <../../sign>` is your trusted partner for secure, efficient, and legally compliant
electronic signatures in Canada.
Legal framework for electronic signatures in Canada

2
content/applications/productivity/sign/chile.rst → content/applications/productivity/sign/validity/chile.rst
View File

@@ -4,7 +4,7 @@
Odoo Sign legality in Chile
===========================
:doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant
:doc:`Odoo Sign <../../sign>` is your trusted partner for secure, efficient, and legally compliant
electronic signatures in Chile.
Legal framework for electronic signatures in Chile

2
content/applications/productivity/sign/china.rst → content/applications/productivity/sign/validity/china.rst
View File

@@ -4,7 +4,7 @@
Odoo Sign legality in China
===========================
:doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant
:doc:`Odoo Sign <../../sign>` is your trusted partner for secure, efficient, and legally compliant
electronic signatures in China.
Legal framework for electronic signatures in China

2
content/applications/productivity/sign/colombia.rst → content/applications/productivity/sign/validity/colombia.rst
View File

@@ -4,7 +4,7 @@
Odoo Sign legality in Colombia
==============================
:doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant
:doc:`Odoo Sign <../../sign>` is your trusted partner for secure, efficient, and legally compliant
electronic signatures in Colombia.
Legal framework for electronic signatures in Colombia

2
content/applications/productivity/sign/dominican_republic.rst → content/applications/productivity/sign/validity/dominican_republic.rst
View File

@@ -4,7 +4,7 @@
Odoo Sign legality in the Dominican Republic
============================================
:doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant
:doc:`Odoo Sign <../../sign>` is your trusted partner for secure, efficient, and legally compliant
electronic signatures in the Dominican Republic.
Legal framework for electronic signatures in the Dominican Republic

2
content/applications/productivity/sign/ecuador.rst → content/applications/productivity/sign/validity/ecuador.rst
View File

@@ -4,7 +4,7 @@
Odoo Sign legality in Ecuador
=============================
:doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant
:doc:`Odoo Sign <../../sign>` is your trusted partner for secure, efficient, and legally compliant
electronic signatures in Ecuador.
Legal framework for electronic signatures in Ecuador

2
content/applications/productivity/sign/egypt.rst → content/applications/productivity/sign/validity/egypt.rst
View File

@@ -4,7 +4,7 @@
Odoo Sign legality in Egypt
===========================
:doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant
:doc:`Odoo Sign <../../sign>` is your trusted partner for secure, efficient, and legally compliant
electronic signatures in Egypt.
Legal framework for electronic signatures in Egypt

2
content/applications/productivity/sign/ethiopia.rst → content/applications/productivity/sign/validity/ethiopia.rst
View File

@@ -4,7 +4,7 @@
Odoo Sign legality in Ethiopia
==============================
:doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant
:doc:`Odoo Sign <../../sign>` is your trusted partner for secure, efficient, and legally compliant
electronic signatures in Ethiopia.
Legal framework for electronic signatures in Ethiopia

2
content/applications/productivity/sign/germany.rst → content/applications/productivity/sign/validity/germany.rst
View File

@@ -4,7 +4,7 @@
Odoo Sign legality in Germany
=============================
:doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant
:doc:`Odoo Sign <../../sign>` is your trusted partner for secure, efficient, and legally compliant
electronic signatures in Germany.
Legal framework for electronic signatures in Germany

2
content/applications/productivity/sign/guatemala.rst → content/applications/productivity/sign/validity/guatemala.rst
View File

@@ -4,7 +4,7 @@
Odoo Sign legality in Guatemala
===============================
:doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant
:doc:`Odoo Sign <../../sign>` is your trusted partner for secure, efficient, and legally compliant
electronic signatures in Guatemala.
Legal framework for electronic signatures in Guatemala

2
content/applications/productivity/sign/hong_kong.rst → content/applications/productivity/sign/validity/hong_kong.rst
View File

@@ -4,7 +4,7 @@
Odoo Sign legality in Hong Kong
===============================
:doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant
:doc:`Odoo Sign <../../sign>` is your trusted partner for secure, efficient, and legally compliant
electronic signatures in Hong Kong.
Legal framework for electronic signatures in Hong Kong

2
content/applications/productivity/sign/india.rst → content/applications/productivity/sign/validity/india.rst
View File

@@ -4,7 +4,7 @@
Odoo Sign legality in India
===========================
:doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant
:doc:`Odoo Sign <../../sign>` is your trusted partner for secure, efficient, and legally compliant
electronic signatures in India.
Legal framework for electronic signatures in India

2
content/applications/productivity/sign/indonesia.rst → content/applications/productivity/sign/validity/indonesia.rst
View File

@@ -4,7 +4,7 @@
Odoo Sign legality in Indonesia
===============================
:doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant
:doc:`Odoo Sign <../../sign>` is your trusted partner for secure, efficient, and legally compliant
electronic signatures in Indonesia.
Legal framework for electronic signatures in Indonesia

2
content/applications/productivity/sign/iran.rst → content/applications/productivity/sign/validity/iran.rst
View File

@@ -4,7 +4,7 @@
Odoo Sign legality in Iran
==========================
:doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant
:doc:`Odoo Sign <../../sign>` is your trusted partner for secure, efficient, and legally compliant
electronic signatures in Iran.
Legal framework for electronic signatures in Iran

2
content/applications/productivity/sign/iraq.rst → content/applications/productivity/sign/validity/iraq.rst
View File

@@ -4,7 +4,7 @@
Odoo Sign legality in Iraq
==========================
:doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant
:doc:`Odoo Sign <../../sign>` is your trusted partner for secure, efficient, and legally compliant
electronic signatures in Iraq.
Legal framework for electronic signatures in Iraq

2
content/applications/productivity/sign/israel.rst → content/applications/productivity/sign/validity/israel.rst
View File

@@ -4,7 +4,7 @@
Odoo Sign legality in Israel
============================
:doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant
:doc:`Odoo Sign <../../sign>` is your trusted partner for secure, efficient, and legally compliant
electronic signatures in Israel.
Legal framework for electronic signatures in Israel

2
content/applications/productivity/sign/japan.rst → content/applications/productivity/sign/validity/japan.rst
View File

@@ -4,7 +4,7 @@
Odoo Sign legality in Japan
===========================
:doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant
:doc:`Odoo Sign <../../sign>` is your trusted partner for secure, efficient, and legally compliant
electronic signatures in Japan.
Legal framework for electronic signatures in Japan

2
content/applications/productivity/sign/kazakhstan.rst → content/applications/productivity/sign/validity/kazakhstan.rst
View File

@@ -4,7 +4,7 @@
Odoo Sign legality in Kazakhstan
================================
:doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant
:doc:`Odoo Sign <../../sign>` is your trusted partner for secure, efficient, and legally compliant
electronic signatures in Kazakhstan.
Legal framework for electronic signatures in Kazakhstan

2
content/applications/productivity/sign/kenya.rst → content/applications/productivity/sign/validity/kenya.rst
View File

@@ -4,7 +4,7 @@
Odoo Sign legality in Kenya
===========================
:doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant
:doc:`Odoo Sign <../../sign>` is your trusted partner for secure, efficient, and legally compliant
electronic signatures in Kenya.
Legal framework for electronic signatures in Kenya

2
content/applications/productivity/sign/kuwait.rst → content/applications/productivity/sign/validity/kuwait.rst
View File

@@ -4,7 +4,7 @@
Odoo Sign legality in Kuwait
============================
:doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant
:doc:`Odoo Sign <../../sign>` is your trusted partner for secure, efficient, and legally compliant
electronic signatures in Kuwait.
Legal framework for electronic signatures in Kuwait

2
content/applications/productivity/sign/malaysia.rst → content/applications/productivity/sign/validity/malaysia.rst
View File

@@ -4,7 +4,7 @@
Odoo Sign legality in Malaysia
==============================
:doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant
:doc:`Odoo Sign <../../sign>` is your trusted partner for secure, efficient, and legally compliant
electronic signatures in Malaysia.
Legal framework for electronic signatures in Malaysia

2
content/applications/productivity/sign/mexico.rst → content/applications/productivity/sign/validity/mexico.rst
View File

@@ -4,7 +4,7 @@
Odoo Sign legality in Mexico
============================
:doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant
:doc:`Odoo Sign <../../sign>` is your trusted partner for secure, efficient, and legally compliant
electronic signatures in Mexico.
Legal framework for electronic signatures in Mexico

2
content/applications/productivity/sign/morocco.rst → content/applications/productivity/sign/validity/morocco.rst
View File

@@ -4,7 +4,7 @@
Odoo Sign legality in Morocco
=============================
:doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant
:doc:`Odoo Sign <../../sign>` is your trusted partner for secure, efficient, and legally compliant
electronic signatures in Morocco.
Legal framework for electronic signatures in Morocco

2
content/applications/productivity/sign/new_zealand.rst → content/applications/productivity/sign/validity/new_zealand.rst
View File

@@ -4,7 +4,7 @@
Odoo Sign legality in New Zealand
=================================
:doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant
:doc:`Odoo Sign <../../sign>` is your trusted partner for secure, efficient, and legally compliant
electronic signatures in New Zealand.
Legal framework for electronic signatures in New Zealand

2
content/applications/productivity/sign/nigeria.rst → content/applications/productivity/sign/validity/nigeria.rst
View File

@@ -4,7 +4,7 @@
Odoo Sign legality in Nigeria
=============================
:doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant
:doc:`Odoo Sign <../../sign>` is your trusted partner for secure, efficient, and legally compliant
electronic signatures in Nigeria.
Legal framework for electronic signatures in Nigeria

2
content/applications/productivity/sign/norway.rst → content/applications/productivity/sign/validity/norway.rst
View File

@@ -4,7 +4,7 @@
Odoo Sign legality in Norway
============================
:doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant
:doc:`Odoo Sign <../../sign>` is your trusted partner for secure, efficient, and legally compliant
electronic signatures in Norway.
Legal framework for electronic signatures in Norway

2
content/applications/productivity/sign/oman.rst → content/applications/productivity/sign/validity/oman.rst
View File

@@ -4,7 +4,7 @@
Odoo Sign legality in Oman
==========================
:doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant
:doc:`Odoo Sign <../../sign>` is your trusted partner for secure, efficient, and legally compliant
electronic signatures in Oman.
Legal framework for electronic signatures in Oman

2
content/applications/productivity/sign/pakistan.rst → content/applications/productivity/sign/validity/pakistan.rst
View File

@@ -4,7 +4,7 @@
Odoo Sign legality in Pakistan
==============================
:doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant
:doc:`Odoo Sign <../../sign>` is your trusted partner for secure, efficient, and legally compliant
electronic signatures in Pakistan.
Legal framework for electronic signatures in Pakistan

2
content/applications/productivity/sign/peru.rst → content/applications/productivity/sign/validity/peru.rst
View File

@@ -4,7 +4,7 @@
Odoo Sign legality in Peru
==========================
:doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant
:doc:`Odoo Sign <../../sign>` is your trusted partner for secure, efficient, and legally compliant
electronic signatures in Peru.
Legal framework for electronic signatures in Peru

2
content/applications/productivity/sign/philippines.rst → content/applications/productivity/sign/validity/philippines.rst
View File

@@ -4,7 +4,7 @@
Odoo Sign legality in the Philippines
=====================================
:doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant
:doc:`Odoo Sign <../../sign>` is your trusted partner for secure, efficient, and legally compliant
electronic signatures in the Philippines.
Legal framework for electronic signatures in the Philippines

2
content/applications/productivity/sign/qatar.rst → content/applications/productivity/sign/validity/qatar.rst
View File

@@ -4,7 +4,7 @@
Odoo Sign legality in Qatar
===========================
:doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant
:doc:`Odoo Sign <../../sign>` is your trusted partner for secure, efficient, and legally compliant
electronic signatures in Qatar.
Legal framework for electronic signatures in Qatar

2
content/applications/productivity/sign/russia.rst → content/applications/productivity/sign/validity/russia.rst
View File

@@ -4,7 +4,7 @@
Odoo Sign legality in Russia
============================
:doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant
:doc:`Odoo Sign <../../sign>` is your trusted partner for secure, efficient, and legally compliant
electronic signatures in Russia.
Legal framework for electronic signatures in Russia

2
content/applications/productivity/sign/saudi_arabia.rst → content/applications/productivity/sign/validity/saudi_arabia.rst
View File

@@ -4,7 +4,7 @@
Odoo Sign legality in Saudi Arabia
==================================
:doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant
:doc:`Odoo Sign <../../sign>` is your trusted partner for secure, efficient, and legally compliant
electronic signatures in Saudi Arabia.
Legal framework for electronic signatures in Saudi Arabia

2
content/applications/productivity/sign/singapore.rst → content/applications/productivity/sign/validity/singapore.rst
View File

@@ -4,7 +4,7 @@
Odoo Sign legality in Singapore
===============================
:doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant
:doc:`Odoo Sign <../../sign>` is your trusted partner for secure, efficient, and legally compliant
electronic signatures in Singapore.
Legal framework for electronic signatures in Singapore

2
content/applications/productivity/sign/south_africa.rst → content/applications/productivity/sign/validity/south_africa.rst
View File

@@ -4,7 +4,7 @@
Odoo Sign legality in South Africa
==================================
:doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant
:doc:`Odoo Sign <../../sign>` is your trusted partner for secure, efficient, and legally compliant
electronic signatures in South Africa.
Legal framework for electronic signatures in South Africa

2
content/applications/productivity/sign/south_korea.rst → content/applications/productivity/sign/validity/south_korea.rst
View File

@@ -4,7 +4,7 @@
Odoo Sign legality in South Korea
=================================
:doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant
:doc:`Odoo Sign <../../sign>` is your trusted partner for secure, efficient, and legally compliant
electronic signatures in South Korea.
Legal framework for electronic signatures in South Korea

2
content/applications/productivity/sign/switzerland.rst → content/applications/productivity/sign/validity/switzerland.rst
View File

@@ -4,7 +4,7 @@
Odoo Sign legality in Switzerland
=================================
:doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant
:doc:`Odoo Sign <../../sign>` is your trusted partner for secure, efficient, and legally compliant
electronic signatures in Switzerland.
Legal framework for electronic signatures in Switzerland

2
content/applications/productivity/sign/thailand.rst → content/applications/productivity/sign/validity/thailand.rst
View File

@@ -4,7 +4,7 @@
Odoo Sign legality in Thailand
==============================
:doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant
:doc:`Odoo Sign <../../sign>` is your trusted partner for secure, efficient, and legally compliant
electronic signatures in Thailand.
Legal framework for electronic signatures in Thailand

2
content/applications/productivity/sign/turkey.rst → content/applications/productivity/sign/validity/turkey.rst
View File

@@ -4,7 +4,7 @@
Odoo Sign legality in Turkey
============================
:doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant
:doc:`Odoo Sign <../../sign>` is your trusted partner for secure, efficient, and legally compliant
electronic signatures in Turkey.
Legal framework for electronic signatures in Turkey

2
content/applications/productivity/sign/ukraine.rst → content/applications/productivity/sign/validity/ukraine.rst
View File

@@ -4,7 +4,7 @@
Odoo Sign legality in Ukraine
=============================
:doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant
:doc:`Odoo Sign <../../sign>` is your trusted partner for secure, efficient, and legally compliant
electronic signatures in Ukraine.
Legal framework for electronic signatures in Ukraine

2
content/applications/productivity/sign/united_arab_emirates.rst → content/applications/productivity/sign/validity/united_arab_emirates.rst
View File

@@ -4,7 +4,7 @@
Odoo Sign legality in the United Arab Emirates
==============================================
:doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant
:doc:`Odoo Sign <../../sign>` is your trusted partner for secure, efficient, and legally compliant
electronic signatures in the United Arab Emirates.
Legal framework for electronic signatures in the United Arab Emirates

2
content/applications/productivity/sign/united_kingdom.rst → content/applications/productivity/sign/validity/united_kingdom.rst
View File

@@ -4,7 +4,7 @@
Odoo Sign legality in the United Kingdom
========================================
:doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant
:doc:`Odoo Sign <../../sign>` is your trusted partner for secure, efficient, and legally compliant
electronic signatures in the United Kingdom.
Legal framework for electronic signatures in the United Kingdom

2
content/applications/productivity/sign/uzbekistan.rst → content/applications/productivity/sign/validity/uzbekistan.rst
View File

@@ -4,7 +4,7 @@
Odoo Sign legality in Uzbekistan
================================
:doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant
:doc:`Odoo Sign <../../sign>` is your trusted partner for secure, efficient, and legally compliant
electronic signatures in Uzbekistan.
Legal framework for electronic signatures in Uzbekistan

2
content/applications/productivity/sign/vietnam.rst → content/applications/productivity/sign/validity/vietnam.rst
View File

@@ -4,7 +4,7 @@
Odoo Sign legality in Vietnam
=============================
:doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant
:doc:`Odoo Sign <../../sign>` is your trusted partner for secure, efficient, and legally compliant
electronic signatures in Vietnam.
Legal framework for electronic signatures in Vietnam

54
redirects/19.0.txt
View File

@@ -1,3 +1,57 @@
# applications/sign
applications/productivity/sign/algeria.rst applications/productivity/sign/validity/algeria.rst
applications/productivity/sign/angola.rst applications/productivity/sign/validity/angola.rst
applications/productivity/sign/argentina.rst applications/productivity/sign/validity/argentina.rst
applications/productivity/sign/australia.rst applications/productivity/sign/validity/australia.rst
applications/productivity/sign/azerbaijan.rst applications/productivity/sign/validity/azerbaijan.rst
applications/productivity/sign/bangladesh.rst applications/productivity/sign/validity/bangladesh.rst
applications/productivity/sign/brazil.rst applications/productivity/sign/validity/brazil.rst
#applications/productivity/sign/canada.rst applications/productivity/sign/validity/canada.rst
#applications/productivity/sign/chile.rst applications/productivity/sign/validity/chile.rst
applications/productivity/sign/china.rst applications/productivity/sign/validity/china.rst
applications/productivity/sign/colombia.rst applications/productivity/sign/validity/colombia.rst
applications/productivity/sign/dominican_republic.rst applications/productivity/sign/validity/dominican_republic.rst
applications/productivity/sign/ecuador.rst applications/productivity/sign/validity/ecuador.rst
applications/productivity/sign/egypt.rst applications/productivity/sign/validity/egypt.rst
applications/productivity/sign/ethiopia.rst applications/productivity/sign/validity/ethiopia.rst
applications/productivity/sign/germany.rst applications/productivity/sign/validity/germany.rst
applications/productivity/sign/guatemala.rst applications/productivity/sign/validity/guatemala.rst
applications/productivity/sign/hong_kong.rst applications/productivity/sign/validity/hong_kong.rst
applications/productivity/sign/india.rst applications/productivity/sign/validity/india.rst
applications/productivity/sign/indonesia.rst applications/productivity/sign/validity/indonesia.rst
applications/productivity/sign/iran.rst applications/productivity/sign/validity/iran.rst
applications/productivity/sign/iraq.rst applications/productivity/sign/validity/iraq.rst
applications/productivity/sign/israel.rst applications/productivity/sign/validity/israel.rst
applications/productivity/sign/japan.rst applications/productivity/sign/validity/japan.rst
applications/productivity/sign/kazakhstan.rst applications/productivity/sign/validity/kazakhstan.rst
applications/productivity/sign/kenya.rst applications/productivity/sign/validity/kenya.rst
applications/productivity/sign/kuwait.rst applications/productivity/sign/validity/kuwait.rst
applications/productivity/sign/malaysia.rst applications/productivity/sign/validity/malaysia.rst
applications/productivity/sign/mexico.rst applications/productivity/sign/validity/mexico.rst
applications/productivity/sign/morocco.rst applications/productivity/sign/validity/morocco.rst
applications/productivity/sign/new_zealand.rst applications/productivity/sign/validity/new_zealand.rst
applications/productivity/sign/nigeria.rst applications/productivity/sign/validity/nigeria.rst
applications/productivity/sign/norway.rst applications/productivity/sign/validity/norway.rst
applications/productivity/sign/oman.rst applications/productivity/sign/validity/oman.rst
applications/productivity/sign/pakistan.rst applications/productivity/sign/validity/pakistan.rst
applications/productivity/sign/peru.rst applications/productivity/sign/validity/peru.rst
applications/productivity/sign/philippines.rst applications/productivity/sign/validity/philippines.rst
applications/productivity/sign/qatar.rst applications/productivity/sign/validity/qatar.rst
applications/productivity/sign/russia.rst applications/productivity/sign/validity/russia.rst
applications/productivity/sign/saudi_arabia.rst applications/productivity/sign/validity/saudi_arabia.rst
applications/productivity/sign/singapore.rst applications/productivity/sign/validity/singapore.rst
applications/productivity/sign/south_africa.rst applications/productivity/sign/validity/south_africa.rst
applications/productivity/sign/south_korea.rst applications/productivity/sign/validity/south_korea.rst
applications/productivity/sign/switzerland.rst applications/productivity/sign/validity/switzerland.rst
applications/productivity/sign/thailand.rst applications/productivity/sign/validity/thailand.rst
applications/productivity/sign/turkey.rst applications/productivity/sign/validity/turkey.rst
applications/productivity/sign/ukraine.rst applications/productivity/sign/validity/ukraine.rst
applications/productivity/sign/united_arab_emirates.rst applications/productivity/sign/validity/united_arab_emirates.rst
applications/productivity/sign/united_kingdom.rst applications/productivity/sign/validity/united_kingdom.rst
applications/productivity/sign/uzbekistan.rst applications/productivity/sign/validity/uzbekistan.rst
applications/productivity/sign/vietnam.rst applications/productivity/sign/validity/vietnam.rst
# applications/websites
applications/websites/ecommerce/payments.rst applications/websites/ecommerce/checkout.rst