How to create a new EviSign

Copy

• Copy for LLM

  Copy page as Markdown for LLMs
• View as Markdown

  Open this page as Markdown
• Open in ChatGPT

  Get insights from ChatGPT
• Open in Claude

  Get insights from Claude
• Connect to Cursor

  Install MCP server on Cursor
• Connect to VS Code

  Install MCP server on VS Code

This guide explains how issuers create and send an EviSign from Namirial Notify. EviSign sends documents for remote signature, tracks signer actions, and records the evidence generated throughout the configured signature workflow.

Prerequisites

• You are signed in as an issuer.
• You have the main document you want to send for signature.
• You have any annexes or additional files you want to attach.
• You know the signer email addresses, mobile numbers, or both.
• If your workflow uses notification recipients, reminders, or callback URLs, you have that data ready.

Open a new EviSign

1. Sign in to Namirial Notify.
2. In NEW SUBMISSION, select the EviSign option.
3. Open New EviSign.

Complete the main submission form

1. Select the sender in From email address.
2. Decide whether to enable Do not send the Sender header in notification emails.
3. Add one or more signers in Signers > Destination.
4. Add notification recipients in Notify > Destination if your process requires them.
5. Enter the Subject.
6. Upload the main PDF in Document.
7. Add any extra files in Attachments if needed.
8. Enter Internal reference in Additional data if your process uses it.

Key fields in this section:

• From email address selects the sender used in the workflow.
• Signers defines who must sign the document.
• Notify lets you add recipients who should receive notifications without acting as signers.
• Document is the main PDF to be signed. The form shown in the UI accepts one file and shows an 8 MB limit.
• Attachments adds annexes or supporting files.
• Internal reference stores an internal identifier for later tracking.

Configure processing and recipient options

1. Set Tracking until.
2. Select the Certification and security level.
3. Select the Affidavit Language.
4. Review the selected Affidavits.
5. Select the Agreement possibilities.
6. Enable Comments are allowed if recipients should be able to add comments.
7. Enable Reason for rejection required if rejection must include a reason.
8. Enter or review Reasons for rejection when that field is used.
9. Decide whether to enable Generate PDF document with the signatures of the certification and of each signatory.
10. Select the Notification language.

Key fields in this section:

• Tracking until defines how long the signature process remains active.
• Certification and security level affects how the evidence is certified.
• Affidavits are selected through the cards shown in the UI, and the default set can vary according to the selected certification level.
• Agreement possibilities controls whether recipients can accept, reject, or do both.
• Reasons for rejection supports the rejection flow when that option is enabled.
• Generate PDF document with the signatures of the certification and of each signatory enables the Generated Signed Document (GSD) feature. See below.
• Notification language controls the language used in recipient-facing messages.

For more detail on generated evidence and affidavit kinds, see Evidence and affidavits.

Generated Signed Document (GSD)

When enabled, Namirial Notify generates an additional PDF after the signing process completes. This PDF contains the original document content with the electronic signature of each signatory graphically embedded at the configured position. This document is independent of the affidavits generated during the process.

If personalized certificates are configured for your site or user, a dropdown appears allowing you to select which certificate to use to certify the content of the generated document. This option is not shown when no certificates are configured.

Signature position

When GSD is enabled, each signer entry shows a Specify the signature position in the document toggle. Enabling it reveals four coordinate fields that define where the signature box is placed in the generated PDF.

The PDF coordinate system uses points as the unit, with origin (0, 0) at the bottom-left corner of the page. X coordinates increase to the right; Y coordinates increase upward.

You define the signature box by specifying two corners of a rectangle:

If no position is specified for a signer, the signature is embedded without a graphical representation at a specific location.

Review customization options

1. Use Reload default texts if you want to restore the default wording.
2. Review or edit the informative text for the signature request email.
3. Review or edit the informative text for the reminder email.
4. Review or edit the informative texts shown in the final, rejected, or expired notifications, depending on the fields available in your environment.
5. Review or edit the informative text shown on the web page where the document is opened or read.
6. Enter the Ending url if recipients should be redirected after the process.
7. Select what to Attach to the final notification.
8. Select what to Attach to the signature request.
9. Enter Additional commitments if your process requires them.
10. Decide whether to enable Require differentiated acceptance of annexes.

Key fields in this section:

• Reload default texts restores the default wording for the informative texts shown in this section.
• The informative-text fields control the messages shown in emails, web pages, and end-of-process notifications.
• Ending url redirects users at the end of the workflow when your process requires it.
• The attachment selectors define what recipients receive with the signature request and the final notification.
• Require differentiated acceptance of annexes can make annex acceptance explicit when that option is enabled.

Review advanced options

1. Enter the Url for event notification if your process uses callbacks.
2. Decide whether to enable Show filters for event notification.
3. Decide whether to enable Show notification options for interested parties notifications.
4. Select the interested-party notification filters you want, such as Sent, Signed, Rejected, Expired, Failed, or Cancelled.
5. Configure the Signature Reminder Options.
6. Set the waiting time and repeat interval.
7. Select the reminder days and time ranges if your process uses them.
8. Select the Time zone.
9. Set Ends on and Maximum number of repetitions.
10. Select the Cost Centre.
11. Set the Retention period.
12. Select the Custody access control method.
13. Decide whether to enable Notarial deposit.
14. Enter a Safety tag if your organization uses one.

Key fields in this section:

• Url for event notification sends callback events to your endpoint.
• Interested-parties notifications can be enabled and filtered by the specific events you want to share.
• The reminder settings control when reminders are sent, how often they repeat, and in which time windows they are allowed.
• Cost Centre supports internal allocation when your organization uses it.
• Retention period, Custody access control, and Notarial deposit affect evidence custody and access.
• Safety tag can be used when your organization applies tag-based restrictions.

Lite Flow

Lite Flow is a simplified signing interface for recipients. It reduces the number of steps in the signing process for a faster experience.

When to use it: Lite Flow suits signers who are familiar with the process and need a quick, streamlined experience. It is not recommended for signers who may need more guidance through each step.

Enable Lite Flow via the UI

In the signer configuration, enable the Lite Flow toggle for each signer who should use the simplified interface. The setting is per-signer — you can mix standard and Lite Flow signers in the same EviSign.

Compatible features

Not all EviSign features are available when Lite Flow is active for a signer. The table below shows what is and is not supported.

Send the EviSign

1. Review the configured sender, signers, notifications, document, attachments, and options.
2. Confirm that the workflow matches what you want to send.
3. Click Send.

Expected result

Namirial Notify creates the EviSign and starts the configured signature workflow. The transaction then appears in the issuer area, where you can monitor its status and retrieve the available evidence and affidavits.

Troubleshooting

The signer configuration cannot be completed

Problem: The signer section remains incomplete or the form does not accept the entered signer data.

Cause: A signer destination may be missing, invalid, or incomplete.

Solution:

1. Confirm that at least one signer was added in Signers > Destination.
2. Review the signer data shown in the list.
3. Correct any validation message shown in the content area.

The document cannot be uploaded

Problem: The main document cannot be uploaded or accepted in the form.

Cause: The selected file may not meet the format or size restrictions shown in the form.

Solution:

1. Confirm that the main file is a PDF.
2. Check the size limits shown in the Document area.
3. Replace the file and try again if the current document does not meet the allowed limits.

An expected signing option is not available

Problem: A field or option described in this guide does not appear in your EviSign form.

Cause: The option may depend on tenant configuration, enabled services, territory, or user role.

Solution:

1. Confirm whether the feature is enabled for your tenant or role.
2. Check whether your environment exposes that option in the relevant tab.
3. Contact your administrator or sales contact if you need the option enabled.

The EviSign cannot be submitted

Problem: The form does not let you complete the submission.

Cause: One or more required fields may be missing, invalid, or blocked by a validation error.

Solution:

1. Confirm that the signer data is complete.
2. Confirm that the main document is attached.
3. Review the subject and the required tab settings.
4. Check the form for validation messages and correct the reported issue.

Related

• Issuer User Manual
• EviSign
• Evidence and affidavits
• States and outcomes
• Search and filters