Are you planning to create a sensitive Google Form? Don’t want to share it with anyone on the web? Well, you don’t have to worry. Here is a simple guide to password protect the Google form.
By default all Google forms are publicly view able. So, if you would like to Password protect your Google form, follow the step by step procedure given here.
How To Password Protect The Google Form?
To password protect your Google form, what we are going to do is just split the actual form into two pages with the first page being served as the log in page. Therefore if someone wishes to view the actual form, they will have to enter the password in the first page.
Still confused? Well, follow these simple steps:
Step 1: First open up your web browser, log in to your Google Accounts and open Google Forms.
Step 2: Now create your Google form. Once done, split the actual form into two pages by clicking on the “Add Section” button as shown below.
Step 3: For reference, I have renamed this form title as “Password Protected Form”.
Step 4: Next, add a question by clicking on the “Add Question” button. Enter “Password” as the question title and choose “Short answer” from the drop down list next to the question title field.
Step 5: Now enable the required field. Once done, click on “Data Validation” option as shown below.
Step 6: In the first drop down list, select “Regular Expression”. In the next one, select “Matches” and then enter the your Password in the third field. For this tutorial purpose, I am using the password “crackaloud”. Once done, specify the error text as per your wish.
That’s it. Now whenever someone tries to access this Google form, it will prompt them to enter the password as shown below in the picture below. Once they enter the correct password, Google will let them Google form.
Note: This is not a bullet proof method to protect your Google form. Anyone with a fair amount of HTML knowledge can find out the password by looking at the source code.
If you encounter any issues while following this tutorial, do let me know via comments.