|
| 1 | +============= |
| 2 | +Configuration |
| 3 | +============= |
| 4 | + |
| 5 | +.. _sign/configuration/settings: |
| 6 | + |
| 7 | +Settings |
| 8 | +-------- |
| 9 | + |
| 10 | +Sign's general settings, available via :menuselection:`Sign --> Configuration --> Settings`, offer |
| 11 | +possibilties for: |
| 12 | + |
| 13 | +- adding :ref:`default terms and conditions <sign/configuration/settings-t-and-c>` to the signature |
| 14 | + request email |
| 15 | +- managing template access by restricting access to specific user groups only; once enabled, access |
| 16 | + is managed when :ref:`creating or editing a template |
| 17 | + <sign/request-signatures/create-manage-templates>` |
| 18 | +- enabling additional authentication via: |
| 19 | + |
| 20 | + - :ref:`Aadhaar eSign <sign/security/authentication-aadhaar>` (available in India), including |
| 21 | + managing the service, and buying credits |
| 22 | + - :ref:`itsme® <sign/security/authentication-itsme>` (available in Belgium and the Netherlands), |
| 23 | + including managing the service, and buying credits |
| 24 | + |
| 25 | +- managing authentication via SMS and :ref:`buying credits <in_app_purchase/credits>` |
| 26 | + |
| 27 | +.. _sign/configuration/settings-t-and-c: |
| 28 | + |
| 29 | +Default terms and conditions |
| 30 | +~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 31 | + |
| 32 | +Terms and conditions allow a business to standardize the legal relationship with its clients, define |
| 33 | +obligations and expectations, manage risk, and protect its interests by setting clear rules for |
| 34 | +aspects such as liability and dispute resolution. |
| 35 | + |
| 36 | +To add default terms and conditions to signature requests send via email: |
| 37 | + |
| 38 | +#. Go to :menuselection:`Sign --> Configuration --> Settings`. |
| 39 | +#. Enable :guilabel:`Default Terms & Conditions`. By default, the :guilabel:`Terms in Email` |
| 40 | + option is selected; this option places the terms and conditions at the bottom of the signature |
| 41 | + request email. |
| 42 | +#. Add your terms and conditions to the text box. |
| 43 | + |
| 44 | + .. tip:: |
| 45 | + Type `/` to open the :ref:`powerbox <essentials/html_editor/commands>`, then use commands to |
| 46 | + insert headings, bulleted lists, etc. |
| 47 | + |
| 48 | +#. Click :guilabel:`Save`. |
| 49 | + |
| 50 | +Alternatively, to display the terms and conditions on a web page, select :guilabel:`Terms as Web |
| 51 | +Page` option, then click :guilabel:`Save`. Click :guilabel:`Update Terms`, edit the |
| 52 | +content, and click :guilabel:`Save`. The link to that page is then added as a link in the signature |
| 53 | +request email. |
| 54 | + |
| 55 | +.. tip:: |
| 56 | + You can also add a `.pdf` version of your terms and conditions manually as an attachment to |
| 57 | + signature requests. Alternatively, for templates, documents can be attached by default in the |
| 58 | + :guilabel:`Communication` section of the template :guilabel:`Configuration` when :ref:`creating |
| 59 | + or editing the template <sign/request-signatures/create-manage-templates>`. |
| 60 | + |
| 61 | +.. _sign/configuration/fields: |
| 62 | + |
| 63 | +Fields |
| 64 | +------ |
| 65 | + |
| 66 | +Fields are :ref:`added to documents <sign/prepare-document/add-fields>` to indicate what information |
| 67 | +must be completed by the signers. Various fields are available by default. These fields can be |
| 68 | +:ref:`edited and additional fields can be created <sign/fields/create-edit-fields>` if needed. |
| 69 | + |
| 70 | +Fields are managed in :menuselection:`Sign --> Configuration --> Fields`. |
| 71 | + |
| 72 | +.. _sign/fields/create-edit-fields: |
| 73 | + |
| 74 | +Create and edit fields |
| 75 | +~~~~~~~~~~~~~~~~~~~~~~ |
| 76 | + |
| 77 | +To create or edit a field: |
| 78 | + |
| 79 | +#. Go to :menuselection:`Sign --> Configuration --> Fields`. |
| 80 | +#. Click :guilabel:`New` to create a new field or click on a field to open and edit it. |
| 81 | +#. Complete or edit the following fields: |
| 82 | + |
| 83 | + - :guilabel:`Field Name`: Enter or edit the field name. This is visible in the list of fields in |
| 84 | + the left panel when a document is being prepared for signature. |
| 85 | + - :guilabel:`Type`: Choose the relevant :ref:`field type <sign/fields/field-types>` from the |
| 86 | + dropdown. |
| 87 | + - :guilabel:`Placeholder`: This allows you to specify a placeholder text for the field. If this |
| 88 | + field is left blank, the :guilabel:`Field Name` is used as placeholder text. |
| 89 | + - :guilabel:`Tip`: A tip is displayed inside an arrow on the left-hand side of the signer's |
| 90 | + screen during the signing process to help them understand what the step entails (e.g., "Sign |
| 91 | + here"). |
| 92 | + - :guilabel:`Field Size`: By default, the size of new fields is set to :guilabel:`Regular Text`. |
| 93 | + For fields that will contain particularly short or long values, it is possible to change this |
| 94 | + to :guilabel:`Short Text` or `Long Text`, respectively. |
| 95 | + - :guilabel:`Linked to`: Linking the field to a model, and then defining a :guilabel:`Linked |
| 96 | + field`, allows the field to be :ref:`auto-completed during signing <sign/fields/auto-fill>`. |
| 97 | + |
| 98 | +There are nine possible :ref:`field types <sign/fields/field-types>`. |
| 99 | + |
| 100 | +.. _sign/fields/field-types: |
| 101 | + |
| 102 | +Field types |
| 103 | +~~~~~~~~~~~ |
| 104 | + |
| 105 | +- :guilabel:`Signature`: Signers enter their signature either by drawing it, generating an automatic |
| 106 | + signature based on their name, or uploading a local file (usually an image). Each subsequent |
| 107 | + :guilabel:`Signature` field in a document reuses the data entered in the first field. |
| 108 | +- :guilabel:`Initial`: Signers enter their initials, in a similar way to the :guilabel:`Signature` |
| 109 | + field. |
| 110 | + |
| 111 | + .. tip:: |
| 112 | + If an :guilabel:`Initials` field is added to a multi-page document, a pop-up message asks if |
| 113 | + you want to add initials to all pages of the document, or if they should only be added once. |
| 114 | + |
| 115 | +- :guilabel:`Text`: Signers can enter text on a single line. |
| 116 | +- :guilabel:`Multiline Text`: Signers can enter text on multiple lines. |
| 117 | +- :guilabel:`Checkbox`: Signers can tick a box (e.g., to confirm they accept the terms and |
| 118 | + conditions). |
| 119 | +- :guilabel:`Radio`: Signers can select a single option from a series of options by clicking the |
| 120 | + radio button beside the desired option. |
| 121 | +- :guilabel:`Selection`: Signers can select a single option from a series of options by clicking the |
| 122 | + text of the desired option; the remaining options are crossed out. |
| 123 | +- :guilabel:`Strikethrough`: Signers can reject certain phrases by clicking the strikethrough field; |
| 124 | + this adds a visible line through the text. Phrases that have not been struck through are |
| 125 | + considered as accepted by the signer. |
| 126 | + |
| 127 | + .. tip:: |
| 128 | + To use this field type to allow signers to reject certain phrases, place a |
| 129 | + :guilabel:`Strikethrough` field on top of the relevant text. Ensure that the field is neither |
| 130 | + :guilabel:`Mandatory` nor :guilabel:`Read-only` to allow the signer to freely decide which |
| 131 | + phrases to reject. |
| 132 | + |
| 133 | +- :guilabel:`Stamp`: Signers can add a company stamp to the document. |
| 134 | + |
| 135 | +.. _sign/fields/auto-fill: |
| 136 | + |
| 137 | +Auto-completed fields |
| 138 | +~~~~~~~~~~~~~~~~~~~~~ |
| 139 | + |
| 140 | +To reduce the need for manual input and ensure accurate and consistent information, it is possible |
| 141 | +have certain fields automatically completed with data from your database during the signing process. |
| 142 | +This is done by linking a Sign field to a specific field from a specific model. |
| 143 | + |
| 144 | +To enable auto-completion for a Sign field: |
| 145 | + |
| 146 | +#. Go to :menuselection:`Sign --> Configuration --> Fields`. |
| 147 | +#. Open the relevant field. |
| 148 | +#. From the dropdown beside :guilabel:`Linked to` select the model, e.g., *Contact* containing the |
| 149 | + field you want to link to. |
| 150 | +#. Click beside :guilabel:`Linked Field`, then use the field selector to select the relevant field. |
| 151 | + |
| 152 | +When a document containing this field is being signed, the field is auto-completed. By default, |
| 153 | +field can still be edited after auto-completion. However, this can be prevented by editing the |
| 154 | +field *after it has been added to the document* and setting it to :guilabel:`Read only`. |
| 155 | + |
| 156 | +.. example:: |
| 157 | + In the example, the :icon:`fa-envelope` :guilabel:`Email` field in the Sign app is linked to the |
| 158 | + :guilabel:`Email` field in the *Contact* model. When the contact signs the document, their email |
| 159 | + address, as it appears in their record in the Odoo database, is automatically added to the |
| 160 | + document. |
| 161 | + |
| 162 | + .. image:: configuration/auto-complete.png |
| 163 | + :alt: Configuring a field to be auto-completed |
| 164 | + |
| 165 | +.. _sign/configuration/tags: |
| 166 | + |
| 167 | +Tags |
| 168 | +---- |
| 169 | + |
| 170 | +Tags can be used to categorize and organize documents with the Sign app, allowing users to quickly |
| 171 | +search for and filter documents based on specific criteria. |
| 172 | + |
| 173 | +Tags are managed in :menuselection:`Sign --> Configuration --> Tags`. |
| 174 | + |
| 175 | +To create a new tag: |
| 176 | + |
| 177 | +#. Go to :menuselection:`Configuration --> Tags`. |
| 178 | +#. Click :guilabel:`New`. |
| 179 | +#. On the new line that is added at the bottom of the list of tags, type the :guilabel:`Tag Name` |
| 180 | + and select a :guilabel:`Color Index` for your tag. |
| 181 | + |
| 182 | +To duplicate or delete a tag, select the tag, click the :icon:`fa-cog` :guilabel:`Actions` button, |
| 183 | +then click :icon:`fa-clone` :guilabel:`Duplicate` or :icon:`fa-trash` :guilabel:`Delete`. |
0 commit comments