# SharePoint File Request: Setup, Folder Permissions & Document Ingestion

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. Activating the feature requires configuring tenant-level Anyone links, running specific PowerShell cmdlets, and adjusting folder permissions. Downstream teams can then sync collected files into intelligent workspaces for automated indexing and AI agent analysis.

Source: https://fast.io/resources/sharepoint-file-request/
Author: [Derek Labian](https://fast.io/authors/derek-labian/)
Last reviewed: 2026-10-02

## How SharePoint File Request Works and Folder Security Boundaries

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.

| Capability | File Request Link | Standard "Anyone" Edit Link | Authenticated Guest Access |
| :--- | :--- | :--- | :--- |
| Inbound File Upload | Yes | Yes | Yes |
| View Existing Files | No | Yes | Yes |
| Modify or Delete Files | No | Yes | Based on role |
| Microsoft Account Required | No | No | Yes |
| Directory Guest Created | No | No | Yes |

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.

## Steps to Enable SharePoint File Request in Admin Center and PowerShell

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:

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

Inspect the current tenant configuration:

```powershell
Get-SPOTenant | Select-Object CoreRequestFilesLinkEnabled, OneDriveRequestFilesLinkEnabled
```

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

```powershell
Set-SPOTenant -CoreRequestFilesLinkEnabled $True
```

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

```powershell
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:

```powershell
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:

```powershell
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.

## How to Create File Request Links and Manage Submissions

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.

## Why Request Files Appears Greyed Out and Troubleshooting Checklist

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

| Symptom | Primary Root Cause | Remediation Step |
| :--- | :--- | :--- |
| Button missing on all folders | `CoreRequestFilesLinkEnabled` is `$False` | Run `Set-SPOTenant -CoreRequestFilesLinkEnabled $True` |
| Button missing on single site | Site sharing set below Anyone | Update site `SharingCapability` in Admin Center or PowerShell |
| Button greyed out for user | User lacks folder Edit permission | Grant Contribute or Edit permissions on target folder |
| Upload fails during transfer | Require Check Out enabled | Disable mandatory check out in Library Versioning Settings |
| Files blocked on upload | Required custom columns without defaults | Assign default values or set columns to optional |

## Downstream Ingestion Bottlenecks and AI Agent Connectors

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.

## Modern Workspace Ingestion with Fast.io Receive Shares

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](/product/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](/product/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](/product/document-data-extraction/), 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:

| Plan | Monthly Billing | Annual Billing | Storage & Workspaces | Monthly Credits |
| :--- | :--- | :--- | :--- | :--- |
| Starter | $9.99/mo | $99/yr | 250 GB storage, 5 workspaces, 3 seats | 100,000 |
| Business | $49.99/mo | $499/yr | 5 TB storage, 50 workspaces, 10 seats | 600,000 |
| Enterprise | $199.99/mo | $1,999/yr | 25 TB storage, 200 workspaces, 30 seats | 3,000,000 |

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.

## Frequently asked questions

### How do I enable Request files in a SharePoint document library?

To enable Request files in a SharePoint document library, an administrator must first verify that Anyone links are enabled under Policies > Sharing in the SharePoint Admin Center. Next, connect to the SharePoint Online Management Shell and run Set-SPOTenant -CoreRequestFilesLinkEnabled $True. Finally, ensure the specific site collection has RequestFilesLinkEnabled set to True using Set-SPOSite, and verify that the target folder allows Edit permissions.

### Why is Request files greyed out in SharePoint?

Request files is greyed out when folder permissions or site sharing policies conflict with the feature requirements. Common causes include holding read-only permissions on the target folder, having site-level sharing configured more restrictively than Anyone, or having Limited-access user permission lockdown mode activated in Site Collection Features. Additionally, if the document library requires document checkout, anonymous uploads are disabled.

### Can external users upload to SharePoint without logging in?

Yes. When an administrator enables Anyone links and configures a file request on a folder, external users can upload files directly through a web browser without logging into a Microsoft account, creating an Entra ID profile, or entering a verification passcode. They can only deposit files and cannot view existing folder contents.

### How does SharePoint handle duplicate file names during a file request?

When an external user uploads a file with a name that already exists in the destination folder, SharePoint does not overwrite the existing document. Instead, it preserves the original file and appends an incremental number to the new upload, saving it as ContributorName_Filename (1).ext.

### Can you set an expiration date on a SharePoint file request link?

Yes. Administrators can set a global expiration window using the Set-SPOTenant -CoreRequestFilesLinkExpirationInDays cmdlet in PowerShell. Site owners can also define link expiration dates when creating anonymous sharing links or manually delete the file request link under Manage Access when intake is complete.

### Does SharePoint notify the folder owner when someone uploads a file via file request?

Yes. SharePoint automatically sends an email notification to the user who created the file request link whenever an external contributor completes an upload. The notification includes the uploader's stated name and a direct link to the newly deposited document.

## Sources

- [Microsoft Learn: Enable File Requests in SharePoint or OneDrive](https://learn.microsoft.com/en-us/sharepoint/enable-file-requests): When users upload files through a SharePoint file request link, they cannot view, edit, delete, or download existing folder files, nor can they identify other contributors who have submitted assets.
- [Microsoft Learn: Enable File Requests in SharePoint or OneDrive](https://learn.microsoft.com/en-us/sharepoint/enable-file-requests): Disabling Anyone links across a Microsoft 365 organization automatically disables the Request files feature in SharePoint Online and OneDrive for Business.

## About Fast.io

Fast.io provides shared workspaces where people and AI agents work on the same files, with built-in semantic search and citation-backed chat over what they hold. Agents reach it through a remote MCP server, a REST API at https://api.fast.io/current/, and a command line client published on npm as @vividengine/fastio-cli. MCP setup is at https://mcp.fast.io/docs: Claude and most MCP clients connect to https://mcp.fast.io/mcp/tools, ChatGPT to https://mcp.fast.io/mcp/operations, and coding agents to https://mcp.fast.io/mcp/code.