Simple Signature for Salesforce

Yes. The Sign button works the same way in the Salesforce mobile app as on a computer. The signer signs on the screen with a finger. This works in the free version.

With the paid version, you can also send a signature request by email. The signer opens it on any phone and needs no Salesforce login. See Add the Sign button in the implementation guide.

The signature form needs an internet connection. Wi-Fi and cellular data both work.

With the paid version, a user with no connection can still make a signature request from a record in the Salesforce mobile app. The app keeps the request. When the phone connects again, Salesforce saves the request, and Simple Signature emails it to the signer. The signer then signs online.

Yes, in the paid version. A signature request sent by email can use more than one document template. Put the template IDs in the request, with commas between them. Use version 5.8.12 or later. See Make a PDF template in Google Docs.

In person, one form shows one document. For a second document, the user opens a second form from a second button.

Yes, in the paid version. The form can show up to 5 signature boxes, each with its own name. You choose which boxes are required. See the parameter multisignature in Build a signature experience.

For signers in different places, one request can go to several people, one after the other or at the same time. Each signer gets an email. See More than one signer.

The free version shows one signature box.

Yes, also in the free version. The form shows the fields of the SignatureFields field set on the ß Signature object. Add any field to that field set, checkbox fields included. See Choose the fields on the form.

The paid version lets you use more than one field set, for more than one form.

Yes, in the paid version, from version 5.8. Add the parameter initials to a signature experience. The form then shows a second, smaller box for the initials. See Build a signature experience.

Did your org make its own Initials field before version 5.8? Then read Signatures stop working after an update before you update.

The free version takes up to 100 signatures a year. The prices of the paid version are on the Simple Signature listing on the AppExchange, under Pricing. The listing also shows the discounts for nonprofits.

For a quote, email sales@toafinish.com or book a demo.

Not all users need licenses. Only users who need to see signatures or request them from your clients, and users who will administer the app, need one. If a user is in a role that will never need to interact with signatures, you don't have to give them a license.

Yes. The app comes with four permission sets:

• Simple Signature (Admin), for anyone who administers the app.
• Simple Signature (User), for all other users who take signatures.
• Simple Signature (Guest), for the guest user of a Salesforce Site only. Signature requests use it.
• Simple Signature (Community), for users of an Experience Cloud site only.

To assign one:

1. Click the gear icon, then Setup.
2. In the Quick Find box, type Permission Sets. Click Permission Sets.
3. Click the permission set.
4. Click Manage Assignments, then Add Assignment.
5. Tick the user who needs the app. Click Next.
6. Leave the assignment with no expiration date. Click Assign.

Permission set groups do not work with managed permission sets. You can vote for Salesforce to fix this on the Salesforce IdeaExchange.

There are a few reasons this can happen. Check them in this order:

1. Is the email address correct? If not, the Lead or Contact on the Signature shows a bounced warning.
2. Does the user who created the request have one of the app's permission sets? It is usually Simple Signature (User).
3. Was the document created? Wait a few minutes, then look at the Files related list on the Signature. If no document is there, the document failed to generate, so the email was not sent.

A document can fail to generate for many reasons. If it failed, open a case so we can look into it.

Under the Electronic Signatures in Global and National Commerce Act, electronically signed documents are just as legally binding as paper documents. Section 101(a) of the law says this plainly.

That means the wording you use, and your ability to track the process, matter most in making a signature legally binding. We recommend that you test it. In our opinion (we are not lawyers), you can run a legally binding process with Simple Signature.

We usually don't turn on the license management feature for installs. We do not strictly monitor licensed usage except around renewal time. If your team grows by a few members, or more users want to start using the app, we let you start using it, and we adjust the licenses next year at renewal time.

We don't have a person dedicated to license management, and managing these licenses is a waste of time for our clients as well. All you have to do is assign each user the appropriate permission set.

The short answer is that we do not offer support. However, if you are interested in upgrading to our paid product and are testing it in the free version, we can offer limited support to make sure your test succeeds.

The first reason to check is whether the user is assigned one of our permission sets. Assign the "Admin" permission set to anyone who administers the app, and the "User" permission set to everyone else.

The app uses file storage in three ways:

1. It saves a preview PDF. The customer gets it as an email attachment, and the signature page shows it. An admin can set up a Maintenance job that deletes these PDFs after the request is signed. The job can also delete an unsigned request and its PDF after a set number of days.
2. It saves a PNG image of the signature. An option deletes this image once the final PDF is made. The image is also saved in a rich text Signature field.
3. It can save the final PDF as an attachment in several places. You can skip this. Copy each final confirmation email to a mailbox that keeps it. The final document then lives in email, not in Salesforce.

The app uses standard Salesforce email, and we have no control over what bounces. We have seen this before: when a contact's email bounces, Salesforce marks the contact as bounced. Even after you fix the address, it can keep bouncing. The only fix we have found is to delete the record and start over on a new Contact or Lead.

We use only named licenses. As an admin, you can change the user assigned to a license.