WP E-Signature (and add-ons) have been created in such a way that they CAN be translated into ANY native language. In order to translate the plugins, you would need to be familiar with the translation process. There is a (free) tool that helps with translation, which you can find @ https://make.wordpress.org/polyglots/handbook/tools/poedit/
File size upload limitations are usually related to a server configuration issue.
If you do not have access to the proper server files we have good news:
There is a third-party plugin called “Upload Larger Plugins”
I swear there’s a plugin for everything 🙂
install this plugin and upload the “E-Signature” plugin using this plugin.
UTC or GTM is “World Time.” We decided for consistency between documents and accuracy it would be best to implement UTC time instead of the local time zone.
Example: If a user is in California and another signer is in Japan the “local” sign time would differ for both he signer and the admin user. By using UTC time it is extremely clear (in court) as to what time and date the document was signed.
You can vote on and request new features and extensions in our WP E-Signature board.
What happens to a signed document?
Once the e-signature document has been digitally signed the document contents are encrypted and stored in your database (read about the document security here). The document can be downloaded a few different ways:
1. Document Sender E-Signature Dashboard lets you download archived documents as PDF’s
2. All parties involved receive an email with a link to the document (where they can download as PDF or print the document)
3. Attach PDF to email add-on (business license) automatically attaches a PDF of the document to the confirmation email
4. Dropbox Sync Add-on (business license) automatically syncs signed PDF’s to a dropbox account
This Occurs for Two Reasons:
1. Many third party themes and plugins have intrusive code that often conflict, manipulate, or simply break WP E-Signature. We have created a document signing template that is standard across the board and is customizable with premium add-ons.
2. Similar to HelloSign and Docusign (the larger monthly fee based document signing companies) we wanted to create a standardized template that is the same across the board so that as WP E-Signature’s popularity grows people will see and trust the document signing process more knowing the credibility of the platform they are signing on.
Note: In the coming months we will be introducing multiple ways in which you can customize the signing page, add a logo, email templates, etc. using add-ons. So keep an eye out!
WP E-Signature has two types of Documents:
a) A Basic Document is a document you create on the fly to send to user(s) for immediate signature request. You can also save this as a draft. Each signer will receive a signer invite email with their own unique signer URL (think of it like a password). Signing details and events are stored and tracked for each signer. You can install automation add-ons like “Signing Reminders” to remind a signer to sign your document (if they have not signed it within your pre-defined timeline).
b) A Stand Alone Documents is a document that is attached to a WordPress page. The signers fill in the agreement (and if Custom Input Fields is installed… they could add additional data via a text field, radio button, checkbox, etc.). Because it lives on the front-end of your website it is usually an agreement that is between the user and a way to “automate” collecting signatures on a generic document like Terms of Service, NDA, etc.
Once a Stand Alone Document is signed WP E-Signature would create a unique document for that signer using a combination of the Stand Alone Document’s name and the signers name.
Example: If you had a Stand Alone Document named “ABC Company Terms” and the signer that signed the Stand Alone Document added the name “Steve Jobs” the new signed document would be called “ABC Company Terms – Steve Jobs.”
c) A Template Document is more or less a document that mirrors itself. When you (or your sales rep) goes to create a new document they simply select “Create from Template.” Creating a document from a pre-defined template will save the sender time and they would fill in/edit the document fields they need to before sending it to the signer.
Identifying WP E-signature links:
Here is a quick primer on how to identify what your signers should see as compared to what you (the admin/document sender) would see.
For a Basic documents:
Signer should see – The url should contain “…e-signature-document/?invite=123456” and the signer would see this after clicking the button inside of the email they receive from you. Each signer receives their own unique URL (think of it like a password that is only emailed to one person). When the document activity notifications add-on is installed you can track whether or not your signers have viewed your document, when they’ve viewed your document and from what ip address the document was viewed.
Note: This link is inside of the email that the signer would receive so If you want to see the link yourself for testing purposes you can create a basic document and send it to yourself by supplying your email as a signer.
Admins should see – When the admin sees “/?esigpreview=” inside of the url, this was generated by clicking on the document title or the word “view” inside of the WordPress admin –> WP E=Signature –> My Documents –> Awaiting Signatures. Its purpose is for you to preview. See attachment “Basic Document”
For a Stand Alone document:
Signer should see – The url looks like a standard WordPress url and can be obtained from WordPress admin –> WP E=Signature –> My Documents –> Stand Alone. By clicking “Share/Invite” link beneath the document. See attachment “Stand Alone Document”
You can password protect your Stand Alone Document by using the native WordPress password protect feature.
Note: If you click the “View” button on this page, you will get a url that contains “/?esigpreview=”.
Got questions about security and protection? Check out this article
Learn more about the legality of the WordPress document signing process: UETA & ESIGN Act
We understand the desire to have a “completely” white labeled “no-branding” document signing application. However, it’s a delicate juggle because our goal is to build a UETA/ESIGN compliant platform that is recognized and trusted in the courtroom (much like docusign, hellosign, etc) so there needs to be a minimal amount of indication to a signer (and a judge) that a document was signed on our compliant platform… yet there needs to be enough customization that your brand/company is more front and center than the platform branding itself. To read how you can customize the plugin with your branding please visit this how to guide.