Share a SharePoint file with specific people, even if the link gets forwarded

Select the circle beside one file, choose Share, and set the invitation to Specific people or People you choose. Enter each recipient’s exact email address, choose the permission they need, and check the details before sending. A link set this way is intended for the named people. Forwarding alone grants no new access to an unnamed person. Existing file access still applies. Microsoft’s file sharing guide explains the sharing controls.

Plan the invitation

Write down the exact filename and source folder first. For example, Jo wants Alex and Mina at a partner organization to read Quote-review.docx in the Harbor Project folder. Jo should confirm that this is the file both people need, then enter alex@partner.example and mina@partner.example as the two recipients. The .example addresses here are fictional; replace them with real addresses in an actual invitation.

Read the full address in each recipient chip before accepting an autocomplete suggestion. An old work alias, a personal address, or a generic team mailbox may be different from the identity the person will use to open the file. Tell recipients which address was invited.

Decide what they need to do with the file. Can view fits a read only quote review. If the file is a Word document and Can review is available, that option fits a request for comments. Choose Can edit when recipients actually need to change the file. Inspect the permission shown in the Share dialog before sending, since its starting selection can vary. If Alex already has editing permission, a Can review invitation leaves that earlier permission in place. Jo must ask the owner to resolve the earlier grant before expecting comments-only access. Microsoft’s file sharing guide describes these permission choices.

Jo can use the named invitation worksheet to record the two addresses, selected audience and permission, plus existing site or group access. It includes a ready-to-edit invitation and fields for the recipient’s actual opening result. The audience example CSV contains the four modeled people below; it is a planning example, not an account export.

Send it to the named people

For Copy link, open the link settings gear and choose People you choose. Apply the intended recipients and permission before copying. Jo sends the configured link to Alex and Mina after inspecting the selected audience.

An Anyone link admits its holders. People in your organization excludes these external guests. Specific people applies to the named audience. People with existing access supplies a URL to existing readers without granting permission. Microsoft’s explanation of sharing permissions distinguishes these link types.

Jo could send this message with the invitation:

Alex and Mina, please read Quote-review.docx in the Harbor Project folder and send me your feedback by [date]. I invited alex@partner.example and mina@partner.example with Can view access. Open it using the address invited, or follow the identity verification prompt you receive. If you use more than one account, check which one is signed in. Please do not forward a verification code. If the file does not open, tell me which address and account you used.

A review deadline in the message does not enforce link expiration. If access should end on a date, the owner must arrange the available permission control separately; do not present the requested deadline as a configured expiry.

What a forwarded link changes

Consider four people around Jo’s file. These are modeled cases, not results from a SharePoint tenant test.

Person	Route to the file	Expected eligibility
Alex	Named on the invitation and opens with the invited identity	Eligible through the invitation if sharing policy permits
Mina	Named on the invitation and opens with the invited identity	Eligible through the invitation if sharing policy permits
Lee	Receives Alex’s forwarded link but has no other grant	The forward alone does not add Lee
Sam	Was not invited but already has internal access	Keeps that existing access

Sam can open the file through an earlier site grant even though Jo entered only Alex and Mina. If the request is “only these two reviewers may see this quote,” Jo needs an owner’s review of the existing audience before sending the invitation. Permissions inherited from a library or site can also affect an item; limited access may let someone reach an item without granting full site browsing. Microsoft’s permissions guidance explains that distinction.

When the invited person cannot open it

Start with the identity, especially when one recipient can open the file and another cannot. Alex may have both a partner work account and a personal account. Ask Alex to confirm the exact address Jo invited and which identity is signed in or being verified. An address that looks familiar is not necessarily the invited identity. Correcting that mismatch is more useful than creating an Anyone link.

Microsoft’s guest sharing guidance includes Microsoft Entra B2B and identity verification for non-Microsoft addresses. Do not send Alex instructions to buy a Microsoft subscription merely because the invitation asks them to verify an identity. The sign in or verification steps the recipient sees depend on the organization’s actual settings, so follow the prompt presented for this invitation rather than promising a particular screen or one time code. Microsoft’s collaboration options describe the policy choices.

Also confirm that the person is opening the link Jo just configured for this file. An older copied link may have a different audience or permission. If both Alex and Mina fail, check the file and URL as well as the organization and site sharing policies. A site cannot allow external sharing more broadly than its organization permits. Settings may allow new and existing guests, only existing guests, or only internal sharing. Files in shared channels have additional restrictions; an external specific people link for a shared channel is limited to channel members. Microsoft’s sharing permissions guide and collaboration options cover those limits.

If the route still fails, give the file owner or support contact a compact description: the file URL and item, the owner’s requested access scope, the exact guest address invited, whether Specific people was available, and what the recipient observed when opening the current link. Ask for an approved way to give that person access. For example: “Alex was invited at alex@partner.example, opened the current Quote-review.docx link with the personal account shown in the browser, and saw [exact message]. Mina opened it with mina@partner.example. Please check the invited identity and permitted guest route.” Keep passwords and verification codes out of that report.

Confirm the invitation with the recipient

Jo opening the file in the owner account proves little about Alex’s route. Ask Alex to open the current invitation in their own session and confirm the filename and permission they see. Record their invited address and result in the worksheet. A signed-out browser may prompt for sign-in or verification; that prompt alone does not tell Jo whether the named recipient will be admitted after completing it.

For the Word example, Jo should ask Alex to describe the controls available after the file opens. If the task is to leave comments, confirm that the actual access permits the intended review. If Alex reports full editing controls despite a review invitation, inspect any earlier Edit grant. Sam’s site access and Alex’s named invitation are separate rows in the plan, so a successful test for Sam cannot substitute for Alex’s result.

If another colleague needs the quote, add that person through the approved invitation route. Forwarding Alex’s verification code or switching the file to Anyone would change the audience Jo set out to create.

The Microsoft instructions were checked October 7, 2026. The Harbor Project example uses fictional identities and modeled outcomes; no live tenant invitation was tested.