Internal Deep Research · Slack + Outlook + Official Vendor Docs

External Party File-Sharing: What We Keep Re-Inventing

ForgeFX has tried FTP, Dropbox, Google Drive, SharePoint/OneDrive, direct web download links, video-platform links, and one-off specialist transfer services. The pattern is not “which app is best.” The pattern is missing ownership, missing default lanes, and a workflow that keeps pushing sales/client-facing staff into admin/setup details.

Recurring approaches found

Specific case studies below

10GB

Example prospect upload size discussed

870GB

Archive candidates flagged for Dropbox in storage audit

Bottom line: FTP is the most durable for very large transfers but the worst client experience. Dropbox works when Adam or the right owner approves requests, but that puts Adam in the critical path. Google Drive can work after “Anyone with link + editor” is set correctly, but the setup created confusion and access-request churn. SharePoint/OneDrive is strong for internal documents and known external collaborators, but it is not a simple anonymous external upload lane. MASV is the best fit I found for recurring large CAD/video uploads from external parties.

Comparison Table

Approach	Best use	What we tried internally	What failed	What worked / final state	Recommendation
Email attachments	Small PDFs, signed docs, quick client paperwork.	Commonly used around proposals, NDAs, compliance docs.	Not viable for CAD, video, builds, source assets, or large ZIPs; versions scatter across inboxes.	Works only when files are small and final.	Keep for small final docs only.
SharePoint / OneDrive links	Internal project/proposal docs; controlled client download; M365 co-authoring.	Proposal PDFs, compliance tables, RFP support docs, John Deere asset bundles, NBCRV build handoff source link.	External upload is not frictionless; “Anyone” links may be disabled or unsafe; Microsoft says link recipients may not upload new items through a copy-link flow.	Great as authoritative internal storage and client download once permissions are understood.	Default for internal canonical files and controlled delivery, not generic outside upload.
Google Drive folder	Fast ad hoc external collaboration when “anyone with link” + editor permission is acceptable.	SSAB/Dallas Brown fallback after FTP and Dropbox struggled.	Initial link required access; Sara got pulled into Google account / Workspace setup questions; needed owner to switch link mode.	Worked after Greg created a ForgeFX Drive folder, switched to anyone-with-link sharing, and Sara verified upload.	Good emergency fallback; script the link creation and permission check.
Dropbox shared folder / file request	Client uploads where Dropbox account ownership is clear; archived source assets outside SharePoint.	SSAB folder, Outokumpu file request/shared folder, SharePoint cleanup proposal to archive old source videos/CAD to Dropbox.	Access approvals landed on Adam; clients requested access; Dropbox/FTP both “oftentimes don’t work for prospects.”	Outokumpu eventually uploaded video after access was approved. Dropbox remains useful for archives.	Use with a team-owned account/workspace owner, not Adam’s personal approval path.
FTP / SFTP on storage.forgefx.com	Very large uploads/downloads; technical users; when reliability beats elegance.	SSAB and Outokumpu prospect folders; sales recipe for constructing FTP download links.	Browsers increasingly reject FTP; prospects cannot navigate it; credentials in links create security and polish problems; sales must ask Miguel/tech support.	Miguel verified FTP upload/delete works and said it is still reliable for large files, but too complex for prospects.	Stop using as default external-facing workflow. Keep as technical fallback only.
Direct website / HTTP download link	Build releases and final ZIP downloads to customers.	MRI NBCRV TeleOp ZIP was in SharePoint; Isaac asked Miguel to upload it to the website to get a direct download link.	Requires technical operator; not a client upload path.	Likely best when ForgeFX is distributing a finished simulator build.	Use for customer downloads of release builds; automate packaging/publish path.
Specialist large-transfer service (MASV / WeTransfer)	Large CAD/video/source uploads from clients with low friction.	MASV appears in John Deere email history as the channel for updated geometry; WeTransfer appears in searches but no strong ForgeFX case found.	No evidence of a standardized ForgeFX MASV/WeTransfer lane. WeTransfer free cap is too small for big CAD/video unless paid plan is used.	John Deere email: “updated geometry … through a MASV link,” then ForgeFX reviewed and requested more CAD context.	Pilot MASV Portals for external upload; keep WeTransfer for small/medium one-offs.

Case Studies

SSABFTP → Dropbox → Google Drive

1. SSAB: Three tools, four-plus emails, one working Drive folder

What happened: Sara reported that SSAB/Dallas Brown had already struggled with FTP and Dropbox. Greg suggested Google Drive; Sara got stuck on account setup questions. Greg then created a ForgeFX Google Drive folder, tested “anyone with link,” and Sara successfully uploaded a file.

Failure mode: The external-transfer burden moved from client to sales/admin staff. The first Drive link still requested access; only a corrected sharing link worked.

Final worked: Google Drive folder with link-based access and upload verified by Sara.

Source: #tech_support thread, 2026-07-09; #ssab_iowa_inc_proposals, 2026-06-29 to 2026-07-06.

OutokumpuFTP → Dropbox

2. Outokumpu: FTP failed in browser, Dropbox approval hit Adam

What happened: Greg asked Miguel for an FTP folder. The client reported the folder was unreachable in a browser. Miguel said browsers “just don’t want to deal with FTP anymore,” while also saying FTP remains reliable for large files. The team also used Dropbox; Denina requested access and Adam was asked to approve.

Failure mode: FTP’s UX is broken for nontechnical users; Dropbox access approval put Adam in the path.

Final worked: Outlook shows “Video is uploaded” from Denina on 2026-06-30 after the Dropbox access/request sequence.

Source: #outokumpu_proposals, 2026-06-25/26; Outlook thread “Outokumpu<>ForgeFX Capabilities,” 2026-06-30.

Sales workflowFTP guidance

3. Tech Support: The documented default was FTP, but everyone knows it is ugly

What happened: Adam asked for the go-to external file-transfer method. Kris answered “FTP” and posted steps for Windows Explorer/FileZilla/Cyberduck and manually constructing a download URL. Greg immediately replied that FTP and Dropbox often do not work for prospects. Miguel later said FTP works but is “a little too complex” for prospects and that 10GB HTTP uploads can timeout.

Failure mode: The default process requires client comfort with FTP, secret-bearing URLs, zipping folders, and support escalation.

Final worked: Internal tech support can make it work; it is not sales-friendly.

Source: #tech_support thread, 2026-07-06/07.

SharePoint storageDropbox archive

4. SharePoint storage pressure: Dropbox as archive, not transfer UX

What happened: Dave raised SharePoint storage pressure and suggested old source videos/images/CAD files could move to Dropbox. Miguel capped SharePoint versioning and recycle bins. AdamoBot scanned tenant storage and identified 117 folders over 5GB, 30 archive candidates, and roughly 870GB that could move to Dropbox.

Failure mode: SharePoint becomes expensive/noisy when it holds old media/source/CAD archives and long version histories.

Final worked: Read-only inventory + archive candidate list; Dropbox viewed as cold storage for old source assets.

Source: #production thread, 2026-06-15/16.

HalliburtonSharePoint CAD upload

5. Halliburton: Big CAD payloads landed in SharePoint, then conversion became the pain

What happened: Devin announced “TONS of CAD files” uploading into the Halliburton Cementing SharePoint folder, including SLDASM and SLDPRT files. The transfer itself worked enough to start downstream Jira/art work; the next bottleneck became CAD-to-Unity conversion.

Failure mode: SharePoint handled delivery, but not normalization, conversion, or pipeline readiness.

Final worked: SharePoint as authenticated project drop zone; ForgeBot produced a Pixyz/Unity Asset Transformer conversion plan afterward.

Source: #halliburton_cementing_services_production, 2026-07-08.

John DeereMASV

6. John Deere geometry: MASV showed up as the cleanest large-file transfer pattern

What happened: In the Excavator Model Review email thread, John Deere sent updated geometry “through a MASV link.” ForgeFX accepted/reviewed it and later asked for a fuller CAD model for context.

Failure mode: No standardized ForgeFX-owned MASV portal/process is visible, so it appears client-driven rather than our default lane.

Final worked: MASV link delivered large geometry from a customer without FTP instructions or personal Dropbox approvals.

Source: Outlook thread “Excavator Model Review Meeting Follow Up,” 2025-08-21 through 2025-09-02.

What External Vendor Docs Say

Vendor/source	Relevant fact	Why it matters for ForgeFX
Dropbox File Requests	Uploaders do not need a Dropbox account. Basic/Plus/Family file requests cap uploads at 2GB; Professional/Business-class requests can accept up to 250GB.	Dropbox can be a good receiving lane only if ForgeFX uses the right business plan/account owner and avoids Adam approval bottlenecks.
Google Drive folder sharing	Folders can be restricted or available to anyone with the link; folder permissions propagate to contents.	Drive worked for SSAB only after link mode was corrected. Permission setup must be templated and verified before sending to clients.
Microsoft SharePoint external sharing	External sharing depends on organization + site settings; the most restrictive setting wins. OneDrive can be more restrictive than SharePoint.	SharePoint is powerful but not “just send the link” reliable unless site policy and link type are known.
Microsoft SharePoint file/folder sharing	“Copy link” can share with outsiders depending on admin settings, but users with the link cannot upload new items.	SharePoint download links are not the same as external upload portals.
WeTransfer	Free transfers up to 3GB; recipients do not need an account; paid Ultimate removes per-transfer size cap.	Good for quick small/medium one-offs, but free tier is too small for 10GB+ CAD/video cases.
MASV large file transfer / MASV FTP alternative	No file package size limits; browser-based drag/drop; upload portals; no recipient/uploader account required for portals; security controls and cloud integrations.	Best match for the repeated “external party uploads huge CAD/video/source files” problem.

Recommended Default Lanes

Create one ForgeFX external-upload lane, not one-off folders

Use a dedicated ForgeFX-owned upload portal for prospects/customers. My vote: pilot MASV Portals first. It fits the actual pain: big CAD/video/source payloads, no FTP instructions, no Adam approval, and browser-based upload.

Keep SharePoint as source-of-truth, not the universal intake UX

SharePoint/OneDrive should remain canonical internal storage and controlled customer delivery. For outside uploads, route uploads into MASV/Dropbox/Drive first, then have ForgeBot or a responsible human move verified files into the right SharePoint project folder.

Retire FTP as the sales default

FTP can remain a technical fallback for huge transfers or legacy flows. It should not be what sales sends to a prospect. If used, a technical owner should generate a clean HTTP download link or supervised upload path, with no credentials exposed in the client-facing instructions.

Make ForgeBot own the checklist

The real workflow Adam wants is: “Share this file so the client can get it” or “Create an upload link for this client.” That should trigger: choose lane by file size/direction/sensitivity, create folder/portal, verify external access with a test upload/download, return the link plus one-line instructions.

Decision Matrix

Scenario	Default	Fallback	Avoid
ForgeFX sends small final document to prospect/customer	Email attachment or SharePoint view link	Google Drive link	FTP
ForgeFX sends simulator build / ZIP download	Direct website/HTTP download link backed by internal SharePoint source	SharePoint link if customer can access	Email, FTP URL with credentials
External party uploads 0–3GB quick files	WeTransfer or Google Drive verified upload folder	Dropbox file request	Personal/free ad hoc accounts
External party uploads 3–250GB CAD/video/source files	MASV Portal pilot	Dropbox Business file request; technical FTP fallback	Browser FTP, unmanaged HTTP uploads
Known customer already in M365 workflow	SharePoint/OneDrive guest sharing with verified permissions	Google Drive link	Anonymous link to sensitive source assets
Cold archive / old source assets leaving SharePoint	Dropbox archive with manifest + SharePoint link-back	Azure/AWS archive if governance needed	Leaving giant historical video/CAD in active SharePoint libraries

Evidence Table

Internal source	Date	Claim / evidence	Confidence
#tech_support SSAB escalation	2026-07-09	Sara reported FTP + Dropbox problems and Google Drive setup confusion; Drive worked only after link settings were corrected and upload was verified.	Internal-high
#tech_support go-to method thread	2026-07-06/07	Kris documented FTP as the go-to; Greg said FTP and Dropbox often fail for prospects; Miguel said FTP works but is too complex and 10GB HTTP uploads can timeout.	Internal-high
#outokumpu_proposals FTP broken thread	2026-06-26	Client could not reach FTP in browser; Miguel said browsers increasingly reject FTP and suggested easier/bulletproof solution needed.	Internal-high
Outlook: “Outokumpu<>ForgeFX Capabilities”	2026-06-30	Dropbox access request and security/login activity preceded client note: “Video is uploaded.”	Internal-medium
#production SharePoint storage thread	2026-06-15/16	SharePoint storage pressure led to Dropbox-as-archive discussion; scan flagged 117 folders over 5GB and 30 archive candidates totaling ~870GB.	Internal-high
#halliburton_cementing_services_production	2026-07-08	Large CAD files landed in SharePoint; downstream issue became CAD conversion/optimization.	Internal-high
Outlook: “Excavator Model Review Meeting Follow Up”	2025-08-21	John Deere sent updated geometry through a MASV link; ForgeFX accepted/reviewed and later requested fuller CAD context.	Internal-medium

Open Gaps

I searched Adam’s Outlook mailbox, not every ForgeFX mailbox. The useful email evidence is real but incomplete for team-wide history.
Slack search was broad and user-token based, but still limited to visible channels and Slack search relevance/rate behavior.
I did not mutate any external systems, create portals, or test live vendor uploads in this pass.
Some searches were noisy because terms like “Box” and “Vimeo” appear in unrelated newsletters; I excluded those from the findings unless connected to a ForgeFX case.