Eligible Workspace organizations can share supported Drive content with visitors who do not have Google Accounts. The visitor verifies control of their email address with a PIN. This is different from public link access and from an organization’s separately hosted Guest account.
Confirm that visitor sharing is allowed
The file owner’s organization must enable visitor sharing and allow the recipient’s domain or address. Use the authorized work or school account and confirm that the content type supports the intended workflow.
In Share, enter the recipient’s address, select Viewer, Commenter, or Editor as appropriate, and send the invitation. Do not ask the recipient to use the owner’s credentials. An external email address can also already be associated with a Google Account, so establish which identity method applies.
Use the invitation and verification flow
The visitor opens the original invitation, requests or receives the verification email, and enters the PIN on the verification page. Google documents a seven-day verified collaboration period. Continuing later can require verification again through the original invitation link.
Visitors cannot own Drive content or become root-level shared-drive members. Supported shared-drive folders allow some creation and upload workflows, whereas visitor uploads into My Drive are not supported.
Keep permission and identity separate
A successful PIN proves the verification step for that visitor session; it does not grant unlimited access to the organization’s Drive. The selected role and file sharing still apply. When the collaboration ends, remove the visitor’s permission through the authorized sharing controls. If the invitation does not work, have the owner inspect policy, file type, and recipient address rather than enabling an unrestricted public link.
References
Reviewed against the linked official product guidance on November 3, 2026. Features, limits, screen labels, and access can vary by account, platform, region, and organization policy.