A client needs to send several documents. You want something easier to manage than another chain of attachments, but sharing your main client folder feels risky. Should you create an upload link, invite the client into SharePoint, or use a separate portal?
Microsoft 365 offers two different approaches: upload-only file requests and sharing with specified recipients. They solve different problems. File requests prevent uploaders from browsing the destination folder, while sharing with specific people restricts access to invited recipients. Neither choice replaces a review of the information involved and the permissions you grant. (support.microsoft.com)
The practical goal is simple: give each client an appropriate way to submit documents, keep unrelated information out of reach, and establish who checks and closes each request.
Start with the documents, not the sharing button
Before changing settings, write a short intake specification. Use one real business process, such as collecting bookkeeping records or receiving project materials, rather than trying to redesign every document exchange at once.
Answer these questions:
- What documents do we actually need?
- Do they contain financial, personal, contractual, or otherwise restricted information?
- Must we verify the submitter, or is an upload from anyone holding the link acceptable?
- Should the client only submit documents, or also review and update them?
- Which employees should handle the submission?
- Who will close access, and when?
Treat those answers as acceptance criteria. For example, “clients must not see one another’s submissions” is a requirement you can test. “Make it secure” is not specific enough to guide a configuration decision.
For sensitive records, make verified access your starting preference. If an existing approved client portal already meets your requirements, avoid creating a second intake route merely because Microsoft 365 is available.
Understand the two Microsoft 365 approaches
Upload-only file requests
With Request files in OneDrive for work or school or SharePoint, anyone holding the request link can upload without needing OneDrive. Through that link, they cannot view, edit, delete, or download the folder’s contents or see other uploaders. However, an unsigned-in person’s entered name is not validated. An upload label therefore is not proof of identity. (support.microsoft.com)
Consider this option for a narrowly scoped collection of ordinary project materials when you have explicitly accepted those identity limitations. Do not assume that an upload-only interface makes it suitable for every confidential document.
There is also an administrative trade-off: Microsoft’s file-request feature requires Anyone links to be enabled, alongside other prerequisites. Disabling Anyone links disables file requests. If the button is missing, ask your administrator to review the requirements rather than relaxing sharing settings just to reveal it. (learn.microsoft.com)
Sharing with specified clients
For recipient-restricted access, use Specific people in the sharing settings. Depending on the account and configuration, an external recipient may sign in or verify access through a one-time code. A recipient does not necessarily need to purchase Microsoft 365 or create a Microsoft account. (support.microsoft.com)
The important limitation is that an editable shared folder is not an upload-only inbox. Edit permission can allow changes, copying, moving, renaming, sharing, and deletion of accessible contents. Keep internal working documents and other clients’ records outside that folder. (support.microsoft.com)
If you require both verified identity and strictly upload-only behavior, treat that combination as a separate design requirement. Ask your administrator to evaluate a suitable portal or configuration rather than assuming ordinary folder editing meets it.
Build a small pilot before inviting real clients
1. Assign ownership and a narrow scope
Choose one employee to manage intake and a backup person to cover absences. Write down where submissions belong, who reviews them, and how receipt is acknowledged.
For a repeatable team process, consider an administrator-approved SharePoint location. Create a separate intake folder for each client or engagement. Use neutral project identifiers where practical; avoid putting sensitive personal details in folder names.
Do not populate the pilot with real records. Create clearly labeled dummy documents instead.
2. Review existing access
Select the proposed folder and inspect Manage access. Microsoft’s access panel shows people, groups, and links; an individual’s access summary can also include groups with access to the containing site. Review more than the invitation you are about to create. (support.microsoft.com)
Ask the site owner to explain any broad group or unfamiliar link. Your recommended approval rule should be: no real client documents until the owner can explain every access route relevant to the folder.
A separate folder name is an organizational convention, not evidence that permissions are correct.
3. Configure the chosen route
For an approved file-request workflow, select the destination folder, choose Request files, describe the requested materials, and send the generated request link. When intake ends, deleting that request link stops further uploads through it. (support.microsoft.com)
For recipient-restricted sharing, select the client’s dedicated folder, open Share and its link settings, and choose the specific-recipient option. Identify the intended recipient and review the permission level before sending. Do not share the parent folder containing multiple clients. Microsoft’s current interface may label the recipient choice People you choose. (support.microsoft.com)
If the required option is unavailable, stop and ask the administrator. Organization-level sharing controls set the boundary, and individual sites can be more restrictive. A missing option is not a reason to substitute a public link. (learn.microsoft.com)
4. Give clients understandable instructions
Prepare a short message that states:
- Which documents to submit and which not to submit.
- Whether sign-in or verification should be expected.
- How to confirm the request through an established contact method.
- When your team will acknowledge receipt.
- What to do if access fails.
Avoid asking clients to work around an error by sending sensitive records through an unapproved alternative. Log the problem and resolve the intended route instead.
Run this do-it-yourself acceptance checklist
Use an authorized external test account and dummy files. Test from outside your normal employee session so you are not accidentally evaluating the experience with staff permissions.
- Correct destination: Submit a dummy file and confirm that it reaches the intended folder.
- Client separation: Check whether the test user can reach another client’s folder or internal working documents.
- Identity expectations: Record whether the experience requires sign-in, a verification code, or only a typed name.
- Forwarding behavior: Try the invitation using a second, uninvited test identity. Compare the result with the access model you selected.
- Permission scope: Attempt to view, rename, replace, and delete dummy files. Record what is possible rather than assuming upload access is limited.
- Usability: Repeat the intended submission from a phone browser.
- Closure: Remove the test access or request link and confirm that the old route no longer works.
- Staff coverage: Have the backup employee locate the submission and explain the next step.
These tests are designed to check the distinctions Microsoft documents between file requests, recipient-specific sharing, editing permissions, and access management. If a result differs from your intake specification, resolve it before using real information. (support.microsoft.com)
Keep a brief test record with the date, folder owner, selected approach, observed permissions, and unresolved issues.
A Raleigh/Triangle consideration: financial and tax records
For bookkeeping and tax practices serving Raleigh, Durham, Cary, and Chapel Hill, this is more than a convenience decision. North Carolina’s Department of Revenue warns that criminals impersonate tax authorities and other organizations to obtain sensitive financial information, and it directs tax professionals to federal security guidance. (ncdor.gov)
The IRS’s October 20, 2026 guidance also warns about malicious new-client and document-request messages. It recommends multifactor authentication, updated security software, vigilance for suspicious requests, and reviewing the firm’s written information security plan. (irs.gov)
For a Triangle practice handling these records, make the intake procedure part of that broader security review. Do not treat a working upload link as proof that the entire process meets professional, contractual, or regulatory requirements.
Know when professional help is sensible
An owner or operations leader can define requirements, prepare instructions, and run the dummy-file tests. Bring in an administrator when permissions are unclear, sharing controls need changes, or the workflow spans several teams.
Seek a broader review when you need verified upload-only intake, detailed access evidence, or handling rules for sensitive records. EverpineLab’s modern workplace and cybersecurity services are relevant to that configuration and process review—not necessarily to replacing tools that already work.
Before expanding the pilot, require three outcomes: clients can complete the intended task, the observed permissions match your written requirements, and staff can reliably review submissions and close access. Start with one process, correct the failures, and only then make it the standard.
Sources and further reading
- Microsoft Support: Create a file request
- Microsoft Learn: Enable file requests in SharePoint or OneDrive
- Microsoft Support: External or guest sharing in OneDrive, SharePoint, and Lists
- Microsoft Support: Share SharePoint files or folders
- Microsoft Support: See who a file is shared with in OneDrive or SharePoint
- Microsoft Learn: Manage sharing settings for SharePoint and OneDrive in Microsoft 365
- North Carolina Department of Revenue: Financial Safety During Holiday Season
- Internal Revenue Service: Security reminders and tools for tax pros
Ready to improve the next bottleneck?
We will help you identify the most practical next step for your business—without turning it into a giant technology project.