Secure or verified email submission when using Request Forms

Stephen McTigue

Features that would be greatly beneficial include the following when using Request Forms:

1. The email field that is populated by the requester at the submit stage of the form should be limited to a specific domain (ie. a company's email domain). Currently any email address entered in this field will be accepted. Someone not authorized could get the confirmation email that includes all the entered data. The current method creates a security and privacy risk.
2. There should be an option in the form design to mask or simply not send the submitted data with the confirmation email. The requester should be fine with simply getting an email that states their request was received.
3. Additionally, once the submit button is clicked, there's no way to confirm that the email address entered is correct. There should be a confirmation or additional screen where the requester must confirm their name and email address is correctly entered.

Permanently deleted user

Hi Stephen, this is an interesting suggestion and I can see why having a two-step confirmation process would be useful here for any human errors on the requester's side.

 

Thanks for posting so others can discuss and vote on this suggestion and it will be shared with our Product Team.

 

For now, if you're finding that you're seeing a lot of errors in these sections, perhaps add this question again in your form. It won't prompt the email to be sent but it will give the requester another opportunity to enter the correct information and it will give you a reference to ensure the emails provided match each other. I'm aware this is not exactly what you're looking for but might be a workaround for now.

 

Thanks for sharing and if there are any updates on this, I'll be sure to post back here.