Google account access and prerequisites
Use the right account and permissions for source forms, document setup and Google output connections.
Reviewed 2026-10-30 · Formesign guides
Use an account with permission to work on the Google source and the intended output destination. Formesign sign-in, the Drive picker, the source document and a signer's invitation can involve different permissions. Check which account is active at each step.
Prepare the source
For a Google Form, verify that you can open the intended source and that the chosen creation path permits the operation. The copy and edit-existing routes have different consequences; choose deliberately before continuing.
For a Google Doc, open the document and use the current Docs add-on workflow. For a spreadsheet, select the correct file and tab in Sheet signature. A file appearing in the picker does not by itself establish that you can edit or share it as required.
Select the account deliberately
- Sign in to Formesign with the account that should manage the form.
- When using Browse, confirm the Google account shown by the picker.
- Select the source and check its title before proceeding.
- Review the Google authorization request for the operation you are performing.
- If your organization blocks the connection, ask its Workspace administrator about that specific request and service account rather than changing unrelated sharing settings.
Connect output separately
Creating a form does not prove that its response Sheet or Drive output is configured. A Google Forms-linked Sheet and a report's Link to Sheets connection are separate routes. Choose the destination your team intends to use and check a demonstration response.
Drive synchronization uses the configured account and folder permissions. Current Formesign Drive setup supports My Drive, with additional sharing requirements; Shared Drives are not supported by that setup. Follow Save signed records to Drive for the exact destination workflow.
Check signer access
The signer should open the shared form or assigned request link, not your editor URL. Verified signature mode can require Google sign-in; a different access configuration may be appropriate for your audience. Test the intended experience before distributing the link.
For healthcare collection, use the HIPAA setup guide to understand the relevant Workspace and Formesign BAA branches and PHI controls. Ordinary Google sign-in alone does not complete that setup. For an access error, see Google source troubleshooting.