No, Google Forms has no built-in password setting. You can restrict the form to people who sign in with an approved Google account, or ask for a shared code in a required first question before people can continue. Google’s responder settings (opens in a new tab), sign-in help (opens in a new tab), and response validation rules (opens in a new tab)
Say you’re sending a class quiz to students who already have school accounts. You want the school account to decide who gets in. For a club dinner, you might only want to keep casual visitors out of an RSVP form. A code included in the invitation may be enough for that job.
Restrict a Google Form to specific accounts
Google Forms is the better fit when everyone already has a Google account in the same organisation and you want to decide who can open the form by account. You can grant responder access to individuals or Google Groups. If your Google Workspace setup offers a suitable target audience, you can choose it under General access. Responders need to sign in to the Google account you’ve granted access to. Google’s sharing guide (opens in a new tab), Workspace access options (opens in a new tab), and responder sign-in help (opens in a new tab)
- For a new form, choose Publish, then Manage. For a form you’ve already published, open Share to review responder access. Google’s publishing steps (opens in a new tab)
- Add the people or group and give them the Responder role, or choose your intended audience under General access if it’s available. Make sure general access doesn’t allow everyone with the link. Publish the form if needed and choose Copy responder link. Google’s sharing steps (opens in a new tab)
- Ask one invited person to open the responder link with the account they’ll actually use. For a class quiz, check with a student’s school account before sending it to the class. If they see You need access, check which account they’re signed in to and whether you’ve included it. Google’s permission troubleshooting (opens in a new tab)
Ask for a password before the form opens
If you’re sending that club dinner RSVP to guests who use different email providers, whatayarn can ask for a password before showing the questions. Setting a form password requires Creator, whatayarn’s paid plan. Guests can enter the password without signing in. Form access guide and how people answer
Use one shared password to keep casual visitors out. Anyone you give it to can pass it on, so it doesn’t tell you who is opening the form. For the dinner example, the event RSVP form template gives you a starting point for attendance and guest numbers. Add the password in your form settings.
In whatayarn, open your form’s Settings and find Access. Turn on Password, enter the password and choose Save password. Open the live link in a signed-out window and try the wrong password and then the right one. Share the link and the password with your guests once you’ve checked the prompt. Set a form password
Adding a password requires the paid Creator plan.
Add a shared code to the first section in Google Forms
If you want to keep your Google Form and a simple speed bump is enough, put a required code question on the first page and the rest of your questions on later pages. Google Forms uses response validation to check that answer before the respondent can go to the next section. Google’s section setup (opens in a new tab) and how validation affects the Next button (opens in a new tab)
- Add the code question. At the top of the form, add a Short answer question called Enter your invitation code. Turn on Required. Google’s question setup (opens in a new tab)
- Set the match rule. On the question, open More and choose Response validation. Select Regular expression, then Matches. For the example code
RIVER27, enter^RIVER27$as the pattern. The^and$mark the start and end, so the whole answer must be the code. Use letters and numbers for your own code to keep the pattern simple. Google’s response validation rules (opens in a new tab) - Write the error message. In Custom error text, enter something like “That code didn’t match. Check your invitation and try again.” Keep the code in the invitation. Google’s custom error instructions (opens in a new tab)
- Move the other questions to the next section. Choose Add section after the code question. Leave the code as the only question in the first section, move the rest of your questions into the later section or sections, and check that the first section leads to the second. Google’s guide to creating sections (opens in a new tab) and choosing which section comes next (opens in a new tab)
- Test the responder link. Publish the form if needed and open the responder link as a guest would. Try Next with the field blank, then with
RIVER270, then withRIVER27. Only the exact code should let you reach the next section. Google’s publishing guide (opens in a new tab) and validation troubleshooting (opens in a new tab)
The rule applies to everyone, so you can’t change the code for just one guest. To replace it, edit the rule and give the new code to everyone who still needs it. The first question checks what someone types. For access control by person, use Google’s responder permissions. Google’s question rules (opens in a new tab) and responder permissions (opens in a new tab)
If sign-in is the sticking point for another form, see how Google Forms file uploads handle sign-in. For the dinner example, browse RSVP questions for a party.










