mirror of
https://github.com/odoo/documentation.git
synced 2025-12-12 07:29:27 +07:00
[IMP] sign: updates for 19.0
task-5106515
This commit is contained in:
mcsi-odoo
@@ -1,410 +1,45 @@
|
||||
: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/sign_received_documents
|
||||
sign/request_signatures
|
||||
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:
|
||||
|
||||
- :doc:`sign a document <sign/sign_received_documents>` in the Sign app, from the chatter of an Odoo
|
||||
record, or from the Documents app
|
||||
- send :doc:`a single document <sign/request_signatures>` 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
|
||||
- :ref:`prepare documents for signing <sign/prepare-document>` by one or multiple signers using
|
||||
drag-and-drop fields
|
||||
- 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
|
||||
- use :ref:`templates <sign/request-signatures/create-manage-templates>` for frequently used
|
||||
documents or document envelopes
|
||||
|
||||
.. 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
|
||||
|
||||
190
content/applications/productivity/sign/configuration.rst
Normal file
190
content/applications/productivity/sign/configuration.rst
Normal file
@@ -0,0 +1,190 @@
|
||||
=============
|
||||
Configuration
|
||||
=============
|
||||
|
||||
.. _sign/configuration/settings:
|
||||
|
||||
Settings
|
||||
========
|
||||
|
||||
Sign's general settings, available via :menuselection:`Sign --> Configuration --> Settings`, allow
|
||||
you to:
|
||||
|
||||
- add :ref:`Sign 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/create-manage-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 sent via email:
|
||||
|
||||
#. Go to :menuselection:`Sign --> Configuration --> Settings`.
|
||||
#. Enable :guilabel:`Default Terms & Conditions`. By default, the :guilabel:`Terms in Email`
|
||||
option is selected; this option places the terms and conditions at the bottom of the signature
|
||||
request email.
|
||||
#. Add your terms and conditions to the text box.
|
||||
|
||||
.. tip::
|
||||
Type `/` to open the :ref:`powerbox <essentials/html_editor/commands>`, then use commands to
|
||||
insert headings, bulleted lists, etc.
|
||||
|
||||
#. Click :guilabel:`Save`.
|
||||
|
||||
Alternatively, to display the terms and conditions on a web page, select :guilabel:`Terms as Web
|
||||
Page` option, then click :guilabel:`Save`. Click :guilabel:`Update Terms`, edit the
|
||||
content, and click :guilabel:`Save`. The link to that page is then added as a link in the signature
|
||||
request email.
|
||||
|
||||
.. tip::
|
||||
You can also add a `.pdf` version of your terms and conditions manually as an attachment to
|
||||
signature requests. Alternatively, for templates, documents can be attached by default in the
|
||||
:guilabel:`Communication` section of the template :guilabel:`Configuration` when :ref:`creating
|
||||
or editing the template <sign/request-signatures/create-manage-templates>`.
|
||||
|
||||
.. _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.
|
||||
|
||||
Fields are managed in :menuselection:`Sign --> Configuration --> Fields`.
|
||||
|
||||
.. _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 prepared for signature.
|
||||
- :guilabel:`Type`: Choose the relevant :ref:`field type <sign/fields/field-types>` from the
|
||||
dropdown; there are nine possible :ref:`field types <sign/fields/field-types>`.
|
||||
- :guilabel:`Placeholder`: Optionally, specify a placeholder text for the field. If this field is
|
||||
left blank, the :guilabel:`Field Name` is used as placeholder text.
|
||||
- :guilabel:`Tip`: Optionally, add a tip to guide the signer. A tip is displayed inside an arrow
|
||||
on the left-hand side of the signer's screen during the signing process to help them understand
|
||||
what the step entails (e.g., "Sign here").
|
||||
- :guilabel:`Field Size`: By default, the size of new fields is set to :guilabel:`Regular Text`.
|
||||
For fields that will contain particularly short or long values, it is possible to change this
|
||||
to :guilabel:`Short Text` or `Long Text`, respectively.
|
||||
|
||||
.. tip::
|
||||
When adding a field to a document or document envelope, change the size of the field
|
||||
manually by hovering over the bottom right of the field until the horizontal, vertical or
|
||||
diagonal double arrows appear, then drag the edge of the box until it reaches the desired
|
||||
size.
|
||||
|
||||
- :guilabel:`Linked to`: Linking the field to a model, and then defining a :guilabel:`Linked
|
||||
field`, allows the field to be :ref:`auto-completed during signing <sign/fields/auto-fill>`.
|
||||
|
||||
.. _sign/fields/field-types:
|
||||
|
||||
Field types
|
||||
-----------
|
||||
|
||||
- :guilabel:`Signature`: Signers enter their signature either by drawing it, generating an automatic
|
||||
signature based on their name, 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.
|
||||
|
||||
.. tip::
|
||||
If an :guilabel:`Initials` field is added to a multi-page document, a pop-up message asks if
|
||||
you want to add initials to all pages of the document, or if they should only be added once.
|
||||
|
||||
- :guilabel:`Text`: Signers can enter text on a single line.
|
||||
- :guilabel:`Multiline Text`: Signers can enter text on multiple lines.
|
||||
- :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 by clicking the
|
||||
radio button beside the desired option.
|
||||
- :guilabel:`Selection`: Signers can select a single option from a series of options by clicking the
|
||||
text of the desired option; the remaining options are crossed out.
|
||||
- :guilabel:`Strikethrough`: Signers can reject certain phrases by clicking the strikethrough field;
|
||||
this adds a visible line through the text. Phrases that have not been struck through are
|
||||
considered as accepted by the signer.
|
||||
|
||||
.. tip::
|
||||
To use this field type to allow signers to reject certain phrases, place a
|
||||
:guilabel:`Strikethrough` field on top of the relevant text. Ensure that the field is neither
|
||||
:guilabel:`Mandatory` nor :guilabel:`Read-only` to allow the signer to freely decide which
|
||||
phrases to reject.
|
||||
|
||||
- :guilabel:`Stamp`: Signers can add a company stamp to the document.
|
||||
|
||||
.. _sign/fields/auto-fill:
|
||||
|
||||
Auto-completed 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 during the signing
|
||||
process. This is done by linking a Sign field to a field from a specific model.
|
||||
|
||||
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* containing 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.
|
||||
|
||||
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 with the Sign app, allowing users to quickly
|
||||
search for and filter documents based on specific criteria.
|
||||
|
||||
Tags are managed in :menuselection:`Sign --> Configuration --> Tags`.
|
||||
|
||||
To create a new tag:
|
||||
|
||||
#. Go to :menuselection:`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.
|
||||
|
||||
To duplicate or delete a tag, select the tag, click the :icon:`fa-cog` :guilabel:`Actions` button,
|
||||
then click :icon:`fa-clone` :guilabel:`Duplicate` or :icon:`fa-trash` :guilabel:`Delete`.
|
||||
Binary file not shown.
|
After Width: | Height: | Size: 12 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 20 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 3.3 KiB |
612
content/applications/productivity/sign/request_signatures.rst
Normal file
612
content/applications/productivity/sign/request_signatures.rst
Normal file
@@ -0,0 +1,612 @@
|
||||
===================
|
||||
Request a signature
|
||||
===================
|
||||
|
||||
When you need to request a signature from one or more signers on a single document or :ref:`document
|
||||
envelope <sign/prepare-document/create-envelope>`, you can initiate a signature request:
|
||||
|
||||
- :ref:`from the Sign app <sign/request-signatures/sign-app>`
|
||||
- :ref:`from an Odoo record <sign/request-signatures/odoo-record>`
|
||||
|
||||
In both cases, you can upload one-off documents or :ref:`use templates
|
||||
<sign/request-signatures/template>` for documents or document envelopes that are used regularly.
|
||||
|
||||
Once a document or document envelope has been fully signed, the signed document and the
|
||||
:ref:`certificate of completion <sign/security/certificate-of-completion>` is sent to you, and to
|
||||
any contacts added in :guilabel:`CC` when you configured the signature request, via email.
|
||||
|
||||
All signature requests that have been sent and completed :ref:`are visible, and can be managed
|
||||
<sign/request-signatures/manage>`, in :menuselection:`Sign --> Documents --> All Documents`.
|
||||
|
||||
.. _sign/request-signatures/sign-app:
|
||||
|
||||
From the Sign app
|
||||
=================
|
||||
|
||||
.. _sign/request-signatures/one-off:
|
||||
|
||||
One-off documents
|
||||
-----------------
|
||||
|
||||
To request the signature of a one-off `.pdf` document or document envelope:
|
||||
|
||||
#. From :menuselection:`Documents --> My Documents` or :menuselection:`--> All Documents`, click
|
||||
:guilabel:`Upload PDF` then select and open the relevant `.pdf` document(s). Alternatively,
|
||||
:ref:`import a document <sign/request-signatures/import-documents>` from the Documents app.
|
||||
#. :ref:`Prepare the document(s) for signing <sign/prepare-document>` by adding the relevant
|
||||
fields and 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 are ready to sign the document directly, click :guilabel:`Sign Now`,
|
||||
complete and sign the document, then click :guilabel:`Validate & Send Completed Document`.
|
||||
- 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/template:
|
||||
|
||||
Using templates
|
||||
---------------
|
||||
|
||||
When using a :ref:`template of a document or document envelope
|
||||
<sign/request-signatures/create-manage-templates>`, it is possible to:
|
||||
|
||||
- send a signature request to one or more specific signers; or
|
||||
- for a document or document envelope with *only one signer*, copy a link that can be shared outside
|
||||
the Sign app. This option is useful when you need to have multiple individuals sign a 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, and each time a recipient of a link
|
||||
signs a document, a new document is created within Odoo Sign.
|
||||
|
||||
To request the signature of one or more specific signers on the same templated document:
|
||||
|
||||
#. Click :menuselection:`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>`.
|
||||
#. If you are:
|
||||
|
||||
- one of the signers and are ready to sign the document directly, click :guilabel:`Sign Now`,
|
||||
complete and sign the document, then click :guilabel:`Validate & Send Completed Document`.
|
||||
- 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:
|
||||
|
||||
#. Click :menuselection:`Templates` to see all existing templates.
|
||||
#. From the kanban or list view, click :guilabel:`Share`. 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 :menuselection:`Templates` kanban view.
|
||||
- To stop sharing a link, from the :menuselection:`Templates` kanban view, click the
|
||||
:icon:`fa-ellipsis-v` :guilabel:`(vertical ellipsis)` icon in the top-right corner of the card,
|
||||
then click :guilabel:`Stop sharing`.
|
||||
|
||||
.. _sign/request-signatures/import-documents:
|
||||
|
||||
Import a document from the Documents app
|
||||
----------------------------------------
|
||||
|
||||
To import a `.pdf` document into the Sign app from the Documents app:
|
||||
|
||||
#. From :menuselection:`Sign --> Documents --> My Documents` or :menuselection:`--> All Documents`,
|
||||
or :menuselection:`Sign --> Templates`, click the :icon:`fa-cog` :guilabel:`(Actions)` icon
|
||||
beside the name of the view, then :menuselection:`Import from Documents`.
|
||||
|
||||
.. image:: request_signatures/import-document.png
|
||||
:alt: Importing a document from the Documents app
|
||||
:scale: 80%
|
||||
|
||||
#. In the window that opens, select the document to import from the dropdown or click
|
||||
:guilabel:`Search more` to see a list of all `.pdf` documents in the Documents app.
|
||||
#. Click :guilabel:`Import and Sign`.
|
||||
|
||||
.. _sign/request-signatures/odoo-record:
|
||||
|
||||
From an Odoo record
|
||||
===================
|
||||
|
||||
To send a signature request from an Odoo record:
|
||||
|
||||
#. With the relevant record open, click the :icon:`fa-cog` :guilabel:`(Actions)` icon, then
|
||||
:icon:`fa-file-text` :guilabel:`Request Signature`.
|
||||
|
||||
.. image:: request_signatures/request-record.png
|
||||
:alt: Request a signature from an Odoo record
|
||||
:scale: 80%
|
||||
|
||||
#. In the :guilabel:`New Signature Request` window:
|
||||
|
||||
- to use a :ref:`template <sign/request-signatures/create-manage-templates>`, select the relevant
|
||||
:guilabel:`Template` from the dropdown; or
|
||||
- to upload a one-off document or documents, click :guilabel:`Upload PDF`, select the relevant
|
||||
`.pdf` document(s), then click :guilabel:`Open`.
|
||||
|
||||
.. image:: request_signatures/template-record.png
|
||||
:alt: Selecting a template to request a signature
|
||||
:scale: 80%
|
||||
|
||||
.. note::
|
||||
Templates linked to the current model can be selected, as well as templates that are not
|
||||
linked to any model; the latter are available in any model. A template can be linked
|
||||
to a model in the template's configuration settings when :ref:`creating or editing the
|
||||
template <sign/request-signatures/create-manage-templates>`.
|
||||
|
||||
#. If you are sending a one-off document or documents, :ref:`prepare the document(s) for signing
|
||||
<sign/prepare-document>`, then 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 are ready to sign the document directly, click :guilabel:`Sign Now`,
|
||||
complete and sign the document, then click :guilabel:`Validate & Send Completed Document`.
|
||||
- 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 document 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/create-manage-templates:
|
||||
|
||||
Create and manage templates
|
||||
===========================
|
||||
|
||||
When the same document or document envelope needs to be used regularly, using a template can save
|
||||
time and streamline the workflow.
|
||||
|
||||
.. _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). Alternatively,
|
||||
:ref:`import a document <sign/request-signatures/import-documents>` from the Documents app.
|
||||
|
||||
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 an existing template, go to :menuselection:`Sign --> Templates` and click on a
|
||||
template to open it. Alternatively, click the :icon:`fa-ellipsis-v` :guilabel:`(vertical ellipsis)`
|
||||
icon in the top-right corner, then :guilabel:`Edit`.
|
||||
|
||||
With the template open:
|
||||
|
||||
- :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`:
|
||||
|
||||
- :guilabel:`Model`: Select the model the template is linked to.
|
||||
|
||||
.. note::
|
||||
If no model is selected, the template can be used when :ref:`requesting a signature from a
|
||||
record <sign/request-signatures/odoo-record>` of *any* model. If a model is selected, the
|
||||
template can only be used in that model.
|
||||
|
||||
- :guilabel:`Redirect Link`: Add a url to which the user is redirected after signing the
|
||||
the document, e.g., to a thank you page, or to your company's homepage.
|
||||
- :guilabel:`Documents folder`: Define in which folder in the Documents app the documents
|
||||
using this template should be saved once fully signed.
|
||||
- :guilabel:`Documents tags`: Determine which Documents-app 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 modifed when configuring the 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 :menuselection:`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.
|
||||
|
||||
.. tip::
|
||||
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 in the template's
|
||||
:guilabel:`Configuration` settings.
|
||||
|
||||
Click the name of the template in the breadcrumbs at the top left to return to the previous
|
||||
screen.
|
||||
|
||||
.. _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 :menuselection:`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`.
|
||||
|
||||
To mark a template as a favorite for quicker access, 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 reveal the following options:
|
||||
|
||||
- :guilabel:`Edit` 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.
|
||||
|
||||
.. note::
|
||||
Once a signature request has been sent using a template, it is no longer possible to modify
|
||||
the template. The template can, however, be duplicated.
|
||||
|
||||
- :guilabel:`Duplicate` to make a copy of a template. The duplicated template can then be
|
||||
:ref:`edited <sign/templates/edit>` as needed.
|
||||
- :guilabel:`Archive` to archive a template that is not currently needed.
|
||||
|
||||
.. tip::
|
||||
Archived templates are removed from the main :menuselection:`Sign --> Templates` view but can
|
||||
be viewed using the :guilabel:`Archived` filter via the search bar.
|
||||
|
||||
- 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 or document envelope 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.
|
||||
|
||||
Once a field has been added, it is possible to:
|
||||
|
||||
- **Modify the attributes of the field**: Click on the field to open it, make the necessary changes,
|
||||
then click :guilabel:`Save`.
|
||||
|
||||
Depending on the field and :ref:`field type <sign/fields/field-types>`, attributes that can be
|
||||
modified include:
|
||||
|
||||
- the placeholder text, i.e., the temporary text the signer sees before starting to complete the
|
||||
field: enter the desired text in the :guilabel:`Placeholder` field.
|
||||
- whether or not a field is mandatory: uncheck :guilabel:`Mandatory field` to make a field
|
||||
optional;
|
||||
- whether or not a field that is :ref:`configured to be auto-completed
|
||||
<sign/fields/auto-fill>` is read-only: check :guilabel:`Read-only` to prevent the signer from
|
||||
editing the field;
|
||||
- the horizontal alignment of the text within the field: where this is available, select the
|
||||
desired alignment;
|
||||
- for a :guilabel:`Radio` button field, the number of options: hover over the :guilabel:`Options`
|
||||
value then use the :icon:`fa-caret-up` :guilabel:`(increase)` and :icon:`fa-caret-down`
|
||||
:guilabel:`(decrease)` icons to increase or decrease the number of :guilabel:`Options`. A
|
||||
minimum of two options is required;
|
||||
- for a selection field, the number and names of options: add each option on a new line in the
|
||||
text box, ensuring you have pressed `Enter` after each option. To delete options, remove the
|
||||
corresponding text from the text box.
|
||||
|
||||
.. note::
|
||||
Any changes made to the attributes of a field from within a document apply *to the current
|
||||
document only*. To make permanent changes to the field, :ref:`edit the field
|
||||
<sign/fields/create-edit-fields>`.
|
||||
|
||||
- **Change the size of a field**: Hover over the bottom right of the field until the horizontal,
|
||||
vertical or diagonal double arrows appear, then drag the edge of the box until it reaches the
|
||||
desired size.
|
||||
|
||||
- **Remove a field**: Click on the field to open it then click :icon:`fa-trash` :guilabel:`(remove)`
|
||||
to remove the field from the document.
|
||||
|
||||
- **Change the position of a 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.
|
||||
|
||||
- **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 field, 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:
|
||||
|
||||
Create a document envelope
|
||||
--------------------------
|
||||
|
||||
A document envelope allows you to upload multiple documents at once, or to add additional documents
|
||||
after the initial upload, and send them for signing in a single signature request. It is also
|
||||
possible to create a template of a document envelope.
|
||||
|
||||
To create a document envelope *during* the initial upload:
|
||||
|
||||
#. From :menuselection:`Sign --> Documents --> My Documents` or :menuselection:`Sign --> Templates`,
|
||||
click :guilabel:`Upload PDF`.
|
||||
#. Select the relevant `.pdf` documents and click :guilabel:`Open`.
|
||||
|
||||
To add one or more documents *after* the initial upload:
|
||||
|
||||
#. With the initial document or document envelope open, click :guilabel:`Add` in the
|
||||
:guilabel:`Documents` section.
|
||||
#. Select the relevant `.pdf` document(s) and 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`.
|
||||
|
||||
.. _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:
|
||||
|
||||
#. With the document or document envelope open, 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.
|
||||
|
||||
.. 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 :ref:`define the
|
||||
order <sign/configure-request/signing-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 preparing a one-off document or document envelope for signing and clicking :guilabel:`Send`,
|
||||
or selecting a template and clicking :guilabel:`Send`, the :guilabel:`New Signature Request` window
|
||||
appears.
|
||||
|
||||
.. image:: request_signatures/signature-request-send.png
|
||||
:alt: Configuring a signature request when sending a document for signing
|
||||
|
||||
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>` 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/create-manage-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 then 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:`Specify 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 singed the document.
|
||||
|
||||
.. _sign/configure-request/validity:
|
||||
|
||||
Validity dates and reminders
|
||||
----------------------------
|
||||
|
||||
For documents that need to be signed withing 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.
|
||||
|
||||
.. tip::
|
||||
When using a :ref:`template <sign/request-signatures/create-manage-templates>` for which a
|
||||
default validity period has been defined, the :guilabel:`Valid Until` date is updated
|
||||
automatically; this date can be changed when configuring the signature request 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 fully 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 :icon:`oi-view-list` :guilabel:`(List)` view and :icon:`oi-view-kanban`
|
||||
:guilabel:`(Kanban)` view offer different possiblities:
|
||||
|
||||
In the :icon:`oi-view-list` :guilabel:`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 model the template is linked to.
|
||||
|
||||
In the :icon:`oi-view-kanban` :guilabel:`(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 signers 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 :icon:`fa-times` with a
|
||||
cross :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
|
||||
|
||||
.. image:: request_signatures/signature-status.png
|
||||
:alt: Options available in the kanban view for sent signature requests
|
||||
:scale: 80%
|
||||
|
||||
.. _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
|
||||
:icon:`oi-view-kanban` :guilabel:`(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.
|
||||
Binary file not shown.
|
After Width: | Height: | Size: 11 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 3.6 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 7.3 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 20 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 17 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 9.3 KiB |
@@ -0,0 +1,261 @@
|
||||
===========================
|
||||
Security and authentication
|
||||
===========================
|
||||
|
||||
Various security features as 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 document 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 the signatures. Internal
|
||||
users can hide or show it by turning the :guilabel:`Frame` option on or off when signing the
|
||||
document.
|
||||
|
||||
.. image:: security_authentication/sign-hash.png
|
||||
:alt: Adding the visual security frame to a signature.
|
||||
:scale: 80%
|
||||
|
||||
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, 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 a record's chatter <sign_received_documents>`, or when a
|
||||
:ref:`signature request initiated from a record <sign/request-signatures/odoo-record>` is fully
|
||||
completed, 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: 70%
|
||||
|
||||
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 accessed at
|
||||
any time via the Sign app:
|
||||
|
||||
#. In :menuselection:`Sign --> All Documents`, enable the :icon:`oi-view-kanban`
|
||||
:guilabel:`(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` to download the certificate to your
|
||||
device.
|
||||
|
||||
.. _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.
|
||||
#. 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.
|
||||
Binary file not shown.
|
After Width: | Height: | Size: 64 KiB |
|
Before Width: | Height: | Size: 34 KiB After Width: | Height: | Size: 34 KiB |
|
Before Width: | Height: | Size: 4.5 KiB After Width: | Height: | Size: 4.5 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 24 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 28 KiB |
@@ -0,0 +1,81 @@
|
||||
===============
|
||||
Sign a document
|
||||
===============
|
||||
|
||||
When you are asked to sign a document, this typically involves adding your name, date, and signature
|
||||
to a 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 Documents app
|
||||
|
||||
.. note::
|
||||
To be able to sign documents via the Documents app, the :guilabel:`Sign` action :ref:`must be
|
||||
enabled <sign/sign-document/enable-sign-option>` for the folder or sub-folder in which the
|
||||
document is stored.
|
||||
|
||||
To sign a document in Odoo:
|
||||
|
||||
#. Open the document:
|
||||
|
||||
- From the Sign app: In :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.
|
||||
|
||||
#. :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.
|
||||
|
||||
#. Complete and sign the document, then click :guilabel:`Validate & Send Completed Document`.
|
||||
|
||||
The signed document and the certificate of completion is 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 fully signing a document, an internal user is shown a list of any other documents
|
||||
awaiting their signature. They can then :guilabel:`Sign` or :guilabel:`View` the documents, if
|
||||
desired.
|
||||
- If the document was signed from a record's chatter, the signed document and the related
|
||||
certificate of completion are added to the chatter.
|
||||
|
||||
.. image:: sign_received_document/chatter.png
|
||||
:alt: Signed document and certificate of completion added to Chatter
|
||||
|
||||
.. _sign/sign-document/enable-sign-option:
|
||||
|
||||
Enable the sign option in Documents
|
||||
===================================
|
||||
|
||||
Enabling the :guilabel:`Sign` option for a folder or sub-folder in the Documents app allows any
|
||||
document stored in that folder to be signed without having to leave the Documents app.
|
||||
|
||||
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`.
|
||||
|
||||
.. image:: sign_received_document/enable-sign-documents.png
|
||||
:alt: Signed document and certificate of completion added to Chatter
|
||||
:scale: 80%
|
||||
|
||||
.. seealso::
|
||||
:ref:`Folder-specific email aliases in the Documents app <documents/email-aliases>`
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 6.2 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 4.0 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 13 KiB |
132
content/applications/productivity/sign/validity.rst
Normal file
132
content/applications/productivity/sign/validity.rst
Normal 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)
|
||||
|
||||
.. note::
|
||||
: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>`
|
||||
@@ -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
|
||||
@@ -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
|
||||
@@ -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
|
||||
@@ -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
|
||||
@@ -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
|
||||
@@ -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
|
||||
@@ -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
|
||||
@@ -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
|
||||
@@ -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
|
||||
@@ -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
|
||||
@@ -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
|
||||
@@ -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
|
||||
@@ -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
|
||||
@@ -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
|
||||
@@ -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
|
||||
@@ -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
|
||||
@@ -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
|
||||
@@ -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
|
||||
@@ -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
|
||||
@@ -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
|
||||
@@ -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
|
||||
@@ -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
|
||||
@@ -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
|
||||
@@ -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
|
||||
@@ -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
|
||||
@@ -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
|
||||
@@ -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
|
||||
@@ -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
|
||||
@@ -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
|
||||
@@ -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
|
||||
@@ -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
|
||||
@@ -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
|
||||
@@ -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
|
||||
@@ -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
|
||||
@@ -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
|
||||
@@ -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
|
||||
@@ -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
|
||||
@@ -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
|
||||
@@ -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
|
||||
@@ -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
|
||||
@@ -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
|
||||
@@ -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
|
||||
@@ -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
|
||||
@@ -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
|
||||
@@ -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
|
||||
@@ -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
|
||||
@@ -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
|
||||
@@ -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
|
||||
@@ -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
|
||||
@@ -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
|
||||
@@ -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
|
||||
@@ -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
|
||||
|
||||
Reference in New Issue
Block a user