Share links and control access
Understand passwords, public information, expiry, opening limits and recipient requirements.
UpdatedCheck what is public
Public notes, page titles and form instructions are there to help a visitor understand a link before unlocking it. Keep passwords, private URLs and sensitive personal details out of those fields. Use the protected content field for a secret memo.
Filenames and other operational metadata do not necessarily have the same protection as file contents. A field being unencrypted does not automatically mean that every visitor can see it, but it is a reason to avoid revealing names.
Share the correct password
For an ordinary protected URL, memo or media link, send the recipient the link's unlock password. Use a strong password that you do not reuse for your account. Send it separately from the link where practical.
Request links work differently. Keep the owner's unlock password private because it opens submitted content. If you enable a submit password, that is the password to give submitters. Signing in as the owner does not replace the unlock password.
Keep a secure record before sharing. Support cannot look up a forgotten content password for you. See password troubleshooting.
Set an availability window
When the creator offers scheduling for your plan and content type, a start time delays access and an expiry stops new access through the link. Check the date and time shown by the form before saving.
An expired link cannot recall a downloaded file, copied text, screenshot or destination URL. If the original website must stop accepting a recipient, update its own permissions too.
Understand opening limits
Use an access-count limit only where the selected creator supports it. A limit of one is a deliberate single-opening workflow, not the default for every link or memo. Testing a limited link can consume an opening.
An access event is not proof of a unique person reading or understanding the content. Do not apply a URL or memo opening limit to ordinary file links: the file form does not offer a one-download control.
Check recipient requirements
An ordinary password-and-open flow usually needs no recipient account. A destination such as Google Drive can still require its own account or permission. Additional recipient restrictions, where available and configured, can also require an eligible signed-in account.
If a recipient cannot enter, check the link, current availability and the restriction you actually configured. Do not remove a restriction merely to troubleshoot with the wrong account.
Test and hand off
- Test the workflow with separate, harmless sample content.
- Confirm the intended recipient and review the public text.
- Save the final link and password securely.
- Share them through the channels you agreed on.
- Ask the recipient to confirm an important handoff directly.
For a URL link, remember that the recipient can copy the destination after opening it. For any readable content, assume an authorized recipient can retain a copy. See security and privacy for the feature-specific protection models.