SharePoint File Request: Setup, Folder Permissions & Document Ingestion

Collecting documents from external vendors, contractors, and clients routinely introduces administrative friction. Granting full guest access creates unmanaged identities within Microsoft Entra ID, while circulating open edit links risks accidental deletion or unauthorized browsing of sensitive files. SharePoint File Request resolves this operational dilemma by establishing a one-way upload portal tied to a specific folder within a document library.

SharePoint File Request allows administrators and library owners to generate an upload link for external contributors to deposit files into a SharePoint document library without granting site access. External contributors access a clean web interface where they drag and drop files and input their names. When users upload files through this link, they cannot view, edit, delete, or download existing folder files, nor can they identify other contributors who have submitted assets.

Security Boundaries and Inbound File Attribution

The security architecture of SharePoint File Request relies on anonymous upload tokens that restrict the recipient to write-only operations. Unlike standard SharePoint sharing links that expose library navigation, a file request URL isolates the user inside an upload form.

When a file lands in the document library, SharePoint prepends the contributor's provided first and last name to the file name, producing an identifier such as John_Doe_Contract.pdf. This naming convention prevents incoming submissions from overwriting existing files with identical names and provides immediate attribution for internal reviewers.

Why File Request Fails to Appear by Default

Many administrators expect the Request files button to appear on any SharePoint folder as soon as external sharing is active. However, SharePoint Online separates consumer OneDrive sharing behavior from enterprise SharePoint document libraries. Even when an organization permits external sharing in Microsoft 365, SharePoint document libraries keep the file request capability dormant until an administrator activates it explicitly through the SharePoint Online Management Shell.

• OneDrive File Request: Setup, Folder Permissions & Workspace IngestionOneDrive File Request allows users and administrators to create a secure upload-only link for external contributors to...
• SharePoint Folder Permissions: Managing Unique Permissions and Access ControlManaging SharePoint folder permissions allows administrators to break permission inheritance and assign unique access...
• ChatGPT SharePoint Connector Limits: 100 MiB File Cap, Throttling, and ArchitectureAs of October 2026, the native ChatGPT SharePoint connector enforces a 100 MiB file ceiling and triggers Microsoft...
• Rclone SharePoint: Setup, Mount & Fast Cloud SyncRclone SharePoint configuration allows command-line synchronization and mounting of Microsoft 365 SharePoint document...
• How to Create Folders with SharePoint API: REST, Graph, and Agent WorkspacesCreating folders across SharePoint environments requires choosing between legacy REST endpoints and modern Microsoft...
• Google Drive to SharePoint Migration: Step-by-Step Technical GuideA Google Drive to SharePoint migration requires mapping user identities, converting proprietary Google MIME types into...

More on this subject: Agent File and Document Workflows (397 guides)

Activating file requests across SharePoint Online requires a coordinated sequence of tenant-level security adjustments and PowerShell commands. If an administrator configures folder permissions without adjusting global tenant parameters, the option remains invisible in the user interface.

Step 1: Enable Anyone Links in the SharePoint Admin Center

SharePoint File Request functions on top of anonymous link infrastructure. If your organization disables anonymous links, Microsoft 365 blocks file request creation across all sites.

1. Sign in to the SharePoint Admin Center as a Global Administrator or SharePoint Administrator.
2. In the left navigation pane, expand Policies and select Sharing.
3. Under External sharing, adjust the SharePoint slider to Anyone. If the slider is set to New and existing guests or Only people in your organization, file requests cannot function.
4. Under More external sharing settings, review your link expiration defaults. While optional, establishing a default expiration window (such as 30 or 60 days) prevents orphaned upload links from remaining active indefinitely.
5. Save your policy adjustments.

Step 2: Enable Core Request Files via SharePoint Online Management Shell

Enabling Anyone links in the admin console activates file requests for OneDrive for Business, but it leaves SharePoint document libraries disabled. To enable the button in SharePoint libraries, you must use PowerShell to toggle the CoreRequestFilesLinkEnabled property.

Launch PowerShell as an administrator and connect to your SharePoint Online tenant:

Connect-SPOService -Url https://yourtenant-admin.sharepoint.com

Inspect the current tenant configuration:

Get-SPOTenant | Select-Object CoreRequestFilesLinkEnabled, OneDriveRequestFilesLinkEnabled

If CoreRequestFilesLinkEnabled returns False, execute the following cmdlet to enable the feature globally across all SharePoint document libraries:

Set-SPOTenant -CoreRequestFilesLinkEnabled $True

You can also establish an optional tenant-wide link expiration period specifically for file request links using days:

Set-SPOTenant -CoreRequestFilesLinkExpirationInDays 30

Step 3: Enable File Requests on Specific Site Collections

Tenant-level activation makes the feature available to sites, but individual site collections can maintain independent sharing boundaries. To verify and enable file requests on a specific site collection:

Get-SPOSite -Identity https://yourtenant.sharepoint.com/sites/Finance -Detailed | Select-Object RequestFilesLinkEnabled, SharingCapability

If the site collection has RequestFilesLinkEnabled set to False, activate it directly:

Set-SPOSite -Identity https://yourtenant.sharepoint.com/sites/Finance -RequestFilesLinkEnabled $True

Ensure that the site collection's SharingCapability is set to ExternalUserAndGuestSharing (Anyone). A site restricted to ExistingExternalUserSharingOnly or Disabled cannot host anonymous file request links.

Step 4: Deactivate Lockdown Mode on the Site Collection

A frequent stumbling block on legacy or migrated SharePoint sites is Limited-access user permission lockdown mode. When this feature is active, anonymous tokens cannot access list items or trigger upload endpoints.

To inspect and deactivate lockdown mode:

1. Open the target SharePoint site and navigate to Site settings.
2. Under Site Collection Administration, select Site collection features.
3. Locate Limited-access user permission lockdown mode.
4. If active, click Deactivate to allow anonymous file ingestion links to process uploads properly.

Once tenant and site policies are active, site members with edit rights can generate file request links for any folder inside a document library.

Step-by-Step Procedure to Generate a File Request Link

1. Open the SharePoint document library and locate the destination folder. File requests cannot be attached to individual files or the root library canvas; they require a dedicated target folder.
2. Select the circular checkbox next to the folder name.
3. In the top command ribbon, click Request files. Alternatively, click the vertical three dots next to the folder and select Request files from the context menu.
4. Enter a descriptive title in the dialog box, such as "Q4 Tax Schedules and Audit Documentation". This title appears prominently on the external upload web page.
5. Click Next. SharePoint generates a unique URL containing the anonymous upload token.
6. Click Copy link to distribute the URL through corporate email, ticketing systems, or client messages, or enter recipient email addresses directly to send an automated notification.

The External Contributor Experience

When an external partner opens the file request URL, they are directed to a lightweight web page branded with your organization's name:

• The page displays the custom request title created during setup.
• A Select files button allows contributors to choose documents from their local workstation or drag files into the browser window.
• Before submitting, the uploader enters their First name and Last name.
• Upon clicking Upload, a progress bar monitors the data transfer. Once complete, the contributor receives a confirmation message and the option to submit additional documents.

The uploader never sees existing folder contents, cannot view submissions from other contractors, and has no ability to edit or retrieve documents once uploaded.

Managing Ingested Documents and Revoking Links

Incoming files appear immediately in the SharePoint folder. The document library displays standard metadata including the modified date and the contributor's prepended name.

If a vendor uploads a file named Statement.xlsx and your folder already contains a file with that name, SharePoint does not overwrite the original record. Instead, it appends a numerical sequence to the file name, saving the new upload as John_Doe_Statement (1).xlsx.

To terminate file collection when an intake window closes:

1. Select the destination folder in your document library.
2. Open the Details pane by clicking the information icon in the top right corner.
3. Under Has Access, click Manage access.
4. In the Links tab, locate the file request link.
5. Click the trash can icon or the Delete link option to deactivate the URL immediately. Any subsequent access attempts return an HTTP 404 resource not found error.

When team members report that the Request files button is absent or unclickable, the problem can be traced to specific permission overrides, library rules, or tenant policies.

1. "Request files" Button Is Missing Entirely

If the button does not show up in the command bar or context menu, verify these baseline conditions:

• Root folder selection: You cannot create a file request on the document library root view. You must select an actual folder within the library.
• PowerShell feature status: Verify that CoreRequestFilesLinkEnabled is $True in tenant settings and RequestFilesLinkEnabled is $True on the site collection.
• Anyone links disabled: Disabling Anyone links across a Microsoft 365 organization automatically disables the Request files feature in SharePoint Online and OneDrive for Business. Check if an administrator recently reduced tenant sharing to New and existing guests.

2. "Request files" Is Greyed Out

If the option appears in the menu but cannot be clicked:

• Folder permission levels: The user attempting to generate the link must hold Edit or Contribute permissions on the target folder. Read-only visitors cannot create file request links.
• Broken permission inheritance: If the target folder uses unique permissions that strip Edit rights from site members, restore inheritance or grant explicit Edit permissions to the user.

3. Upload Failures Caused by Document Library Settings

Certain advanced SharePoint document library configurations interfere with anonymous document ingestion:

• Require Check Out: If the document library has Require documents to be checked out before they can be edited set to Yes in Versioning Settings, anonymous uploaders cannot complete file submission. The upload fails because an anonymous token cannot execute a check-in action.
• Mandatory metadata columns: If your document library contains required columns that lack default values, anonymous uploads fail validation. Because the file request interface only collects the uploader's name and file bytes, SharePoint rejects submissions that do not satisfy required metadata fields.
• Draft item security: Libraries configured to only permit authors and approvers to view draft items can prevent anonymous tokens from verifying upload completion.

Troubleshooting Diagnostic Matrix

Automate SharePoint Document Ingestion with Fast.io Workspaces

Sync your SharePoint document libraries through Cloud Sync, index uploaded files for search and AI reasoning, and let agents query ingested documents through the remote MCP server. Monthly plans start with a 14-day free trial (credit card required).

Start 14-Day Trial

Collecting inbound files in SharePoint solves the initial intake step, but downstream document processing frequently exposes operational bottlenecks. Whether processing incoming vendor invoices, compliance filings, or technical specifications, organizations increasingly rely on automated AI assistants to audit, summarize, and extract data from ingested files.

Challenges with Native SharePoint AI Connectors

Connecting AI agents (such as models running in Claude, ChatGPT, Gemini, or local coding environments) directly to SharePoint document libraries presents substantial operational hurdles:

• API Throttling and Rate Limits: The Microsoft Graph API enforces strict concurrency limits across tenants. When an automated agent attempts to scan hundreds of newly deposited documents, Microsoft Graph responds with HTTP status code 429 Too Many Requests, stalling pipeline execution.
• Excessive Context Consumption: Native cloud drive connectors often attempt to traverse entire directory trees or pull entire document libraries into the model context. Ingesting full PDF files into an agent prompt consumes tokens rapidly and slows down reasoning cycles.
• Broad Delegated Permissions: Connecting an external agent directly to SharePoint typically requires broad Entra ID application permissions (such as Files.Read.All), granting the model visibility across unrelated organizational assets rather than scoping it to a single intake folder.

In connector benchmarks across cloud storage providers in Claude Cowork (published at https://fast.io/benchmarks/), Fastio was measured the fastest and the lowest cost of the providers tested.

Decoupling Ingestion with Scheduled Cloud Sync and Remote MCP

Rather than forcing AI agents to pull directly from SharePoint over rate-limited APIs, organizations can decouple storage from retrieval. Teams keep SharePoint as their primary document repository while establishing an automated bridge into an intelligent workspace:

1. Ingest into SharePoint: External clients continue using the SharePoint file request link to submit deliverables.
2. Synchronize to a Fast.io Workspace: Using Cloud Sync for OneDrive (which accesses SharePoint document libraries), the intake folder synchronizes into a Fast.io workspace. Cloud Sync operates one-way or two-way, on a schedule or on demand (never continuous, live, or real-time).
3. Index for Fast Agent Retrieval: Once files arrive in the Fast.io workspace, Intelligence Mode auto-indexes content for hybrid search (combining full-text keyword matching and semantic search).
4. Connect via Remote MCP: Autonomous agents connect to the workspace through the remote Fast.io MCP server (https://mcp.fast.io/mcp/tools for Claude and general MCP clients, https://mcp.fast.io/mcp/code for coding agents) using consolidated MCP tools. Instead of reading whole folder trees, the agent executes targeted semantic queries against indexed files and extracts relevant passages.

While SharePoint File Request serves organizations deeply committed to the Microsoft 365 ecosystem, it imposes a significant compromise: IT administrators must enable tenant-wide Anyone links, which relaxes security boundaries across the entire organization.

For teams that require inbound file collection without altering global enterprise security policies, Fast.io provides purpose-built Receive Shares within shared workspaces.

Branded Receive Shares vs. SharePoint File Request

Fast.io Receive Shares allow organizations to establish dedicated upload portals on any workspace folder:

• No Tenant-Wide Anonymous Toggles: You can generate a public upload link for external contributors without enabling anonymous sharing across your entire company directory.
• Custom Branding and Client Experience: Portals display custom branding, custom upload instructions, and clean web upload targets suitable for high-touch client engagements through branded file sharing.
• Access Controls and Expiry: Assign explicit link expiration dates, access passwords, or per-recipient permissions directly from the share settings.
• Structured Document Extraction: Using Metadata Views, incoming documents (such as invoices, W-9s, or real estate contracts) are automatically processed by AI into typed schema fields (Text, Integer, Date & Time, Decimal, Boolean, URL, JSON) without writing OCR templates.

Integrated Audit Logs and Versioning

Every file uploaded to a Fast.io workspace is governed by per-file version history and a detailed activity log. If a vendor submits a revised statement, the previous draft is preserved, allowing team members to inspect historical versions and track change timelines. The activity log records upload timestamps, uploader identifiers, and later changes to each file.

Teams can also use Collaborative Notes to keep summaries, intake checklists, and review documentation alongside uploaded assets with version-checked saves, allowing humans and AI agents to work within the same workspace context.

Subscription Plans and Commercial Structure

Fast.io operates on a transparent subscription model. Monthly plans start with a 14-day free trial (credit card required); annual billing is paid upfront with no trial. Plans scale to accommodate team storage and AI processing requirements:

Credits meter AI processing tasks, including semantic search indexing, conversational chat, and Metadata Views extraction. Storage and team seats come included with each plan. Extra storage beyond plan limits is billed at 1.5 cents per GB per month, and additional bandwidth is billed at 4 cents per GB.