FAQs

Simple Signature running in Professional Edition can mostly do everything in our app except for the Signature Requests. That is because the Professional Edition of Salesforce does not include the Salesforce Sites feature, which is what Simple Signature uses to host the signature form for non-Salesforce users. It talks about it a bit in the documentation. Also, the integration with Google Docs is not 100% proven in a Professional Edition environment, we don't currently have any Professional clients using this feature. Up until now, we've always used Visualforce for our professional clients, which has it's own limitations since you cannot use code in Professional, so the PDFs need to be somewhat simple.

Not all users need licenses; only users who need to see the signatures or request them from your clients, as well as users who will administer the app. Basically, if a user is in a role that will never need to interact with signatures, you wouldn't have to provide them a license.

Click on Gear Button -> Setup -> User -> Permission Sets. You will see 3 Options:

Simple Signature (Admin) for admins needing to administer the app, Simple Signature (User) - for all other users, and Simple Signature (Guest User) for use in Salesforce Site guest users only. To assign a permission set, select one of these three permission sets, then click on Manage Assignments. --> Click on Add Assignment. --> Add the user you want to give access to the Simple Signature app. Save the Setting.

Yes, permission set groups do NOT work with managed permission sets. You can vote on an idea for Salesforce to fix this here:

https://ideas.salesforce.com/s/idea/a0B8W00000GdlCJUAZ/enable-managed-package-permission-sets-in-permission-set-groups

There are a few reasons this could happen. The first one to check is whether the email address is correct. If it is not, there should be a bounced warning on the Lead or Contact connected to the Signature. A second thing to check is if the user who created the signature request is assigned one of the permission sets that come with the app usually. It should be the "Simple Signature (User)" one. The next thing to check is if the document is being created. Wait a few minutes, and check on the Files related list for the Signature. If it does not have a document that is attached to this list, then likely the email was not sent out because the document failed to generate. There are many reasons this could happen, so you would need to open a case in order for us to investigate at this point.

According to the Electronic Signatures in Global and National Commerce Act, electronically signed documents are just as legally binding as paper documents. You can look at the law below and see in section 101(a) that it states this pretty clearly.

https://www.gpo.gov/fdsys/pkg/PLAW-106publ229/html/PLAW-106publ229.htm

That means that the wording you apply and the ability to track the process is really the most important part, to make sure that any signature will be legally binding. We would recommend that you test it out, but in our opinion (we are not lawyers), you will be able to enforce a legally binding process with Simple Signature.

We usually don't turn on the license management feature for installs. The reason for this is that we do not strictly monitor licensed usage except around renewal time, so if your team grows by a few members, or more users desire to start using it, we just 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 management of these licenses is a waste of time for our clients as well, so 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 potentially upgrading to our paid product and are testing it out in the free version, then we can offer limited support to ensure you are able to test successfully.

The first reason this might be is if the user is not assigned one of our permission sets. The "Admin" permission set should be assigned for anyone administering the app, and the "User" permission set for everyone else.

Our app uses document space in several ways:

1) It saves a preview PDF that is sent to the customer as an email attachment and displayed on the signature page. Simple Signature admins can configure a Maintenance job that deletes these PDFs after the signature request has been signed. They could potentially also delete the signature request itself, along with the PDF, if it doesn't get signed after X number of days.

2) It saves a PNG image of the signature. We have an option where this image is automatically deleted after the final PDF is generated, and the image is also saved into a rich-text Signature field.

3) It optionally saves the final PDF as an attachment in multiple places. This last one does not need to be done, as instead you could have each confirmation email at the end of the signature process be CC'd to an email account that would store the emails containing the final attachment. In that way, the final document would be in your email, and not in Salesforce.

Our app uses standard Salesforce email, and we have no control over what bounces. What we have seen in the past is that if a particular contact has a bad email address and it bounces, then Salesforce somehow marks it as a bounced contact, and even if you fix the email address, it still bounces. The only solution we have found is to delete the record and start over on a new contact or lead record.

We use only named licenses. We do allow you to change the user assigned to the license as an admin, but they are not concurrent licenses.