{"id":376,"date":"2020-02-18T20:23:10","date_gmt":"2020-02-18T20:23:10","guid":{"rendered":"https:\/\/swiftcloud.ai\/support\/?p=376"},"modified":"2020-08-04T17:46:16","modified_gmt":"2020-08-04T17:46:16","slug":"wordpress-electronic-signature","status":"publish","type":"post","link":"https:\/\/swiftcloud.ai\/supportwebadmin\/wordpress-electronic-signature","title":{"rendered":"WordPress Electronic Signature"},"content":{"rendered":"
NOTE: Any e-Sign that happens on a server in which you control the HTML can be dismissed<\/strong><\/span>, because you have the potential for CSS or Javascript obfuscation of signer intent, and\/or change to signer intent. For that reason, the actual signature must happen on our server, in an environment with a “legally disinterested” 3rd party, and the final signed doc held by a legally disinterested third party (so you could not change the contents after it was signed).<\/p><\/blockquote>\n
NOTE: The actual e-Sign happens on our server (with your logo, colors), then we usually send then back to your server.<\/strong> If you’re using WordPress (common), you’ll link the site to our servers (with your logo, colors, etc) to get the signature (reason: We must be able to legally guarantee the contents – no CSS\/JS hiding stuff, etc), then return them back to your server.<\/p>\n
Our docs system works similar to WordPress in that it uses shortcodes – so you’ll be right at home.<\/p>\n
Quick “WordPress Electronic Signature” Setup (WordPress-Style [shortcodes])<\/h2>\n
Note: We previously had a plugin, but due to the above legal concerns, had to change to our current system. WordPress users will feel right at home.<\/p>\n
\n
- Copy your doc you want signed<\/li>\n
- Create a new doc in SwiftCloud<\/li>\n
- Paste your doc<\/li>\n
- Replace the ____ with shortcodes<\/li>\n<\/ol>\n
That’s it. Well, mostly… here’s a video tour<\/p>\n