-
Notifications
You must be signed in to change notification settings - Fork 560
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request] Remote Identity Verification of signers #410
Comments
@Tom-H-L we have Identify verification and AeS with Veriff available for Pro customers on docuseal.eu |
@omohokcoj Nice, I was not aware of that existing feature. So do I understand this correctly and I have to create a separate new account on docuseal.eu if my current account is at docuseal.co/com? If yes, can I transfer my account with all the documents from co/com to eu? P.S.: It says: "Access to QeS and AeS is available only to users with an account on document.eu." Is that the correct domain? |
@Tom-H-L yes, it requires to create docuseal.eu account, unfortunately that's not possible to transfer the data form .com to .eu. Thanks for spotting the typo! It has been fixed. I must admit that I purely explained the reason why the previous 2 issues were closed. Our goal is to keep open-source self-hosted docker app free from third party services or vendor locks, that's why some of the feature request that involve third party services were closed since it doesn't align with our vision for the self-hosted docker app. We are always happy to collaborate on other feature requests for the open-source app that do not involve third party services. |
It would be great to have the option that signers have to pass a remote identity verification process to guarantee their identity prior signing a document.
Various services exist and are used e.g. for opening bank accounts. Here is an AI compiled list:
This feature could be implemented in Docuseal as a Pro feature, or maybe splitting up to include AI based solutions in the free version and human based solutions in the Pro version.
The text was updated successfully, but these errors were encountered: