Let Customers Upload Large Files Through a Browser

Getting Started#

Basic Concept#

The user receiving files creates an upload link and shares it with external customers.

When you need to receive large files from external users, you must first prepare a transfer method and storage location.

For example, when receiving source video, design files, project materials, or large datasets, you might provide an email address, separate transfer software, or a shared-storage account.

This can require creating a separate account for each external user, asking them to install transfer software, and explaining the storage location and access method individually.

When receiving files from multiple external users at the same time, you may also need to track who uploaded which files, where those files were stored, and whether each upload completed successfully.

With INNORIX Flow, you can configure where files will be received and the upload conditions, then generate a dedicated upload link that external users can access.

External users open the shared link in a browser, select the files to upload, and start the transfer. Without creating a separate account or installing transfer software, they can send files through a simple flow of open link → select files → upload → save to the designated storage location.

File Owner
    │
    │ Create Upload Link
    ▼
┌──────────────────┐
│   Upload Link    │
└────────┬─────────┘
         │
         │ Share Link
         ▼
   External User
         │
         │ Open in Browser
         ▼
     Select Files
         │
         ▼
       Upload
         │
         ▼
   Target Storage
         │
         ▼
   Upload Result

[Product UI: The file recipient configures the upload link and storage location, and an external user uploads files through a browser]

Instead of creating a transfer account for each external user or asking them to install separate software, you can provide a single upload link and let the required user send files directly through a browser.

By separating storage locations and file-transfer conditions for each upload link, you can also manage which files were uploaded through which link and where they were stored for each transfer flow, even when multiple projects or file requests are active at the same time.

Upload Process#

Proceed from opening the link through completion of the large-file upload

When a customer opens the upload link, they can select files in the browser and start the transfer.

You can also allow multiple files to be selected or support large files required for the workflow.

┌────────────┐
│ Upload Link│
└─────┬──────┘
      ▼
┌────────────┐
│ Open in Browser │
└─────┬──────┘
      ▼
┌────────────┐
│ Select Files    │
└─────┬──────┘
      ▼
┌────────────┐
│ Uploading       │
└─────┬──────┘
      ▼
┌────────────┐
│ Upload Complete │
└────────────┘

[Product UI: Select files in the browser and review upload progress for large files]

Customers can review the current progress while files are uploading.

After upload completes, the files are applied to the designated storage location and the receiving team can review the processing result.

Workflow Changes#

Reduce the setup required for accounts and transfer software when receiving files

Traditionally, receiving files from external customers may require creating user accounts or explaining a separate file-transfer method.

With an upload link, the receiving team prepares the upload environment in advance and only needs to provide the customer with the link.

For example, when customers need to send large source files, you can use the following structure.

Customer A ──┐
Customer B ──┼──► Upload Link ───► Customer Files
Customer C ──┘                         │
                                   ▼
                              Review · Process

This lets you collect files from multiple customers in a defined location and connect them to downstream work.

Business Teams#

Request Files#

Provide an upload link to customers who need to send files

Business teams can give customers an upload link and instruct them to submit the required files through that link.

For example, when requesting design drafts, you can send an upload link instead of asking the customer to attach files to email.

Request Files
   │
   ▼
Share Upload Link
   │
   ▼
Customer Uploads Files
   │
   ▼
Confirm File Receipt

Customers only need the upload link. They do not need instructions for the entire file-transfer environment.

Uploaded files can be reviewed in the designated work location and used in the next task.

Review Files#

Review files uploaded by customers and their upload results

After a customer uploads files, the receiving team can review the uploaded files and processing status.

After confirming that the files were stored successfully, the team can continue with review, processing, or handoff to another owner.

Customer Upload
       │
       ▼
┌───────────────┐
│ Received Files│
├───────────────┤
│ video_01.zip  │ ✓
│ images.zip    │ ✓
│ data.csv      │ ✓
└───────┬───────┘
        ▼
    Continue to Next Task

Business teams can review the following information.

• Uploaded file names

• File count and total size

• Upload status

• Upload completion time

• Storage location

• Files requiring additional review

This lets the team review the current upload result before asking the customer to resend anything.

Follow-Up Work#

Connect uploaded customer files directly to review and processing tasks

File upload does not have to end with receiving the file. It can continue directly into downstream work.

For example, after a customer uploads a source file, the assigned team member can review it or the file can be transferred automatically to a designated processing system.

Customer
   │
   ▼
File Upload
   │
    ├──────────────► Notify Assignee
   │
   ▼
File Storage
   │
   ▼
Review · Convert · Process
   │
   ▼
Use Result

This connects customer file receipt directly to the point where internal work begins.

IT Engineers#

Receive Environment#

Configure the storage location and upload path for external files

IT engineers first configure the Target environment where customer-uploaded files will be stored.

Files received through an upload link can be connected to a specific server folder, cloud storage location, or workflow-specific workspace.

External Customer
        │
        │ Browser Upload
        ▼
   Upload Endpoint
        │
        ▼
 ┌─────────────────┐
 │   Target Flow   │
 └────────┬────────┘
          │
    ┌─────┼─────────┐
    ▼     ▼         ▼
 Server  Storage  Workspace


Storage locations can be separated by customer or business purpose.

This lets you manage uploaded files according to the workflow they belong to.

Link Setup#

Configure customer-specific upload scope and file-processing rules

When creating an upload link, you can define what files a customer may upload and where they should be stored.

For example, you can accept only files for a specific project or separate upload jobs by allowed file type and storage location.

Upload Link
     │
     ├── Upload Target
     │      └── /customer/project-a/
     │
     ├── File Rules
     │      ├── *.zip
     │      ├── *.csv
     │      └── *.mp4
     │
     └── Access Rules
            └── Link-based Upload

Configure the following settings according to the work environment.

This lets you separate upload scope by customer or project instead of giving every customer the same shared upload environment.

Large-File Handling#

Process multiple files and large datasets in a single upload job

External customers may need to upload files that are difficult to handle through standard email attachments, including images, video, design materials, or data files.

The upload environment can process multiple files in one job and show overall progress.

Selected Files

├── source-video.mp4    24 GB
├── project-assets.zip   8 GB
├── images.zip           3 GB
└── metadata.csv         2 MB
          │
          ▼
     Upload Run
          │
          ▼
     Target Storage

Reviewing per-file results makes it possible to identify not only the overall upload state, but also files that require additional review.

Completion Connection#

Automatically connect customer uploads to the next task

After file upload completes, you can configure the next processing task to start automatically.

For example, when a customer uploads a video, you can start a conversion job or notify the assigned team member that the file was received.

                 File Upload
                      │
                 Completed
                      │
        ┌─────────────┼─────────────┐
        ▼             ▼             ▼
   Processing     Notification   Next Transfer
        │             │             │
        ▼             ▼             ▼
      Conversion     Assignee Review     Other System

Follow-up tasks can be configured according to how the file will be used.

This creates an automated flow from customer upload through internal processing and result verification.

Receive Management#

Operate based on upload requests and per-file processing results

When an external upload runs, review the overall upload status and per-file results in Runs.

Selecting a specific job shows which upload link the files came through, where they were stored on the Target, and the overall file-processing result.

If additional review is required, check the per-file processing results and Target storage state in the Run details.

After taking the required action, you can ask the customer to upload again or rerun downstream processing tasks.

With this structure, external customers can upload files through a browser without creating an account or installing separate transfer software, while internal teams can manage file receipt → storage in the designated location → downstream workflow connection → result verification in one flow.