Share a Teams file without exposing it to the wrong audience

A document posted in a Teams channel is stored with the team's SharePoint files; one sent in a chat is commonly stored in the sender's OneDrive for work or school and shared with chat participants. The message and the file permission are related but distinct. Copying a broad link into a private chat does not make it private, and deleting a chat message does not necessarily revoke a file link. A quick audience check before sending prevents embarrassing or costly exposure.

Before you start​

Identify whether the intended readers are the whole channel, a small chat or named external people. Use the work or school account that owns the file. Check whether the document contains personal data or a secret that should not be in Teams at all. If your organization has a sharing policy, follow it; some link types or external recipients may be disabled by an administrator.

Do it step by step​

1. Open the file in Teams OneDrive or the appropriate channel Shared tab. Confirm its location and owner. If it belongs to a channel, assume channel membership can matter to access, not just the people you mention in a post.
2. Select Share and inspect Sharing settings before copying a link. Prefer specific people for a small audience; choose Can view, Can review, Can edit or Can't download according to the real task and available organization controls.
3. Enter the exact recipient names or addresses when that is the intended scope. Check lookalike names and external domains. If you need to collaborate, grant edit only to those who must change the original.
4. Send the file through the intended chat or channel. Do not paste a previously created Anyone link without inspecting its scope; the older link's permissions may survive the new conversation.
5. Open Manage access and verify the people, groups and links shown. A test from the intended recipient's account can confirm that they can open the document, while a non-recipient test can reveal accidental broad access when feasible.
6. Set a review date for sensitive files. When the project ends, remove unneeded links or direct grants in OneDrive or SharePoint, and document the owner who can restore access if work continues.

Check the result​

The correct people can open the file with only the required permission, and Manage access shows no unintended broad link or external recipient. The file's storage location and owner are understood.

If something goes wrong​

If a recipient cannot open it, inspect the link type, their account and organizational sharing policy rather than generating an anonymous link immediately. If you cannot see Manage access, ask the owner or admin. If the file was copied to another location, audit that copy separately.

Know the limit​

Can't download can restrict a supported interface but cannot prevent screenshots or a recipient from retyping content. Revoking a link does not delete downloaded copies. File access can be inherited from a parent folder or SharePoint site, so remove or change the actual permission source rather than only one message. Teams file sharing Teams file storage Microsoft permission management