Getting Started
Basic Concept
Provide large-file download links to external customers
When you need to provide large files to external users, you might attach the files to email or messaging tools, or place them in shared storage and explain how to access them.
For example, when delivering project results, video files, installation packages, or large datasets, you may need to prepare the files and explain the download location and access method to each external user.
When files are large or different users require different files, however, you also need to consider which users can access which files, how long they can download them, and how access should be managed after the delivery period ends.
With INNORIX Flow, you can generate a dedicated download link for external users based on the files to provide and where they are stored.
External users open the shared link in a browser, review the available files, and start the download. Without installing separate file-transfer software or attaching the files to email, they can receive the files through a simple flow of open link → review files → download → save files.
File Storage
│
│ Select Files
▼
┌───────────────────┐
│ Download Link │
│ Access Settings │
└─────────┬─────────┘
│
│ Share Link
▼
External User
│
│ Open in Browser
▼
View Files
│
▼
Download
A download link can be connected to the files to provide or the location where they are stored, with additional conditions such as access permissions and usage period when needed.
For example, you can share a link that provides only the result files for a specific project or create a download path that remains available only for a defined period.
| Configuration Item | Settings |
|---|---|
| Provided Files | Files or folders available for download |
| File Location | System or storage where the files are stored |
| Access Scope | External users allowed to use the link |
| Usage Period | Period during which the link can be used |
| Access Conditions | Conditions required to download files |
| Download Result | Review file processing and download status |
This allows authorized users to download files directly in a browser through a link with defined file scope and access conditions, instead of sending files directly or attaching them one by one.
Creating separate download links by project, user, or file type also makes it possible to manage which files are provided through each link and the access conditions for that link according to the delivery workflow, even when multiple delivery requests are active.
Access Conditions
Manage download scope with file-specific permissions and usage periods
Download links can be configured with both the files to provide and the conditions under which they can be accessed.
For example, you can provide project results only to a specific customer or make the link unusable after a defined period.
Download Link
│
┌──────────────┼──────────────┐
▼ ▼ ▼
Target Files Access Permission Expiration
│ │ │
result.zip Download Allowed Expires in 7 Days
The download environment can define file availability using criteria like the following.
| Setting | Use |
|---|---|
| Provided Files | Specify files the customer can download |
| Download Scope | Define which files are visible through the link |
| Access Permission | Allow access based on authorized users or conditions |
| Expiration | Disable the link after the specified period |
| Storage Location | Connect the Source location where the files are stored |
| Download Result | Review file delivery and processing results |
This lets you apply separate download conditions by customer, project, or business purpose instead of exposing the same file to every external user.
Provisioning Flow
Connect file preparation through customer download and result verification
Providing files through a download link involves more than simply sharing the link.
You can connect the entire flow from preparing files and sharing the link to reviewing the actual download result.
┌─────────────┐
│ Prepare Files │
└──────┬──────┘
│
▼
┌─────────────┐
│ Set Link Conditions │
│ Permissions · Expiration │
└──────┬──────┘
│
▼
┌─────────────┐
│ Share with Customer │
└──────┬──────┘
│
▼
┌─────────────┐
│ Download Files │
└──────┬──────┘
│
▼
┌─────────────┐
│ Review Results │
└─────────────┘
By setting the required conditions before delivery, customers can download files within the allowed scope and the receiving team can review the results afterward.
Workflow Changes
Move from sending file attachments to providing a managed download environment
When delivering large files directly to customers, you may encounter file-size limits, storage constraints, and access-management requirements after delivery.
With a download link, you can keep the files in their existing environment and provide controlled access through a link instead of sending the files themselves.
| Category | Traditional File Delivery | Download Link |
|---|---|---|
| File Delivery | Use email or shared locations | Provide a download link |
| Customer Access | Use a separate path or account | Open the link in a browser |
| Access Management | Manage separately after delivery | Define the delivery scope through link conditions |
| Usage Period | Manage individually after file delivery | End access automatically based on expiration conditions |
| Result Review | Rely on customer confirmation | Review download-job results |
For example, when providing large videos, design assets, or project results to customers, you can use the following structure.
┌── Customer A ──► Download
│
Project Files ──► Download Link
│
└── Customer B ──► Download
Even when the same files must be provided to multiple customers, you can manage separate links and access conditions for each customer.
Business Teams
Provide Files
Select only the files the customer needs and share them through a download link
Business teams select the files to provide and generate a link that allows the customer to download them.
For example, after a project is completed, you can provide result materials, large source videos, or design files to the customer.
Business Files
│
├── proposal.pdf
├── result-video.mp4
└── project-files.zip
│
▼
Select Files to Provide
│
▼
Create Download Link
Before sharing files, review the following items.
| Item | Details |
|---|---|
| Recipient | Customer or contact receiving the files |
| Provided Files | Actual files available for download |
| File Version | Whether the files are the final versions to provide |
| Usage Period | How long the customer can download the files |
| Link Status | Whether the link is currently available |
After confirming the files and delivery conditions, share the link so the customer can download the specified files directly.
Verify Downloads
Review customer download results and delivery status
After sharing the link, you can review whether the customer downloaded the files successfully.
Once file delivery is complete, you can provide additional files or continue with the next task.
Download Link
│
▼
┌──────────────────┐
│ Customer Access │
└────────┬─────────┘
│
▼
┌──────────────────┐
│ File Downloaded │
└────────┬─────────┘
│
▼
Review Delivery Result
Business teams can review the following information.
Downloaded file names
File count and total size
Download progress
Download start and completion times
Link status by customer
Links that are expiring soon or already expired
If needed, you can later provide new files to the customer or review the current usage state of the existing link.
Link Management
Keep or replace links based on the business situation
Customers may need to review project files multiple times over a defined period, while files for completed work may no longer require access.
Managing the link's usage period and status lets you operate it according to the purpose of the file delivery.
Create Link
│
▼
Customer Downloads Files
│
├──────────────► Delivery Complete → Keep Link
│
▼
Work Complete
│
▼
Expire or Close
For example, links can be used differently depending on the workflow.
| Workflow Situation | Link Use |
|---|---|
| Project Result Delivery | Provide access during the customer review period |
| Large Source File Delivery | Share only the required files |
| Provide Revised Files | Create a link based on the updated files |
| Short-Term File Delivery | Expire automatically after the specified period |
| Repeated Downloads | Keep the link active during the work period |
This lets you provide a managed download environment when needed without repeatedly attaching files or explaining separate shared paths.
IT Engineers
Provisioning Environment
Connect the device containing the download files to an external access path
IT engineers connect the Source environment where customer files are stored to the external download path.
Files remain stored on a server, storage system, or workspace, while customers access only the permitted files through the download link.
┌────────────────┐
│ File Source │
│ Server/Storage │
└───────┬────────┘
│
▼
┌────────────────┐
│ Download Flow │
│ Access Rules │
└───────┬────────┘
│
▼
┌────────────────┐
│ Download Link │
└───────┬────────┘
│
▼
External Customer
Configure the Source and download path around the following items.
| Category | Configuration |
|---|---|
| Source | Device containing the files to provide to the customer |
| Source Path | File path used for downloading |
| Download Link | Download path accessed by the external customer |
| Access Policy | Criteria for permitting access to files |
| Expiration | Link usage period and end condition |
| Run | Actual download execution result |
This lets you provide only the required files to external customers while keeping the internal storage environment unchanged.
Permission Setup
Configure access scope and expiration conditions by customer and file
Rather than providing every file under the same conditions, an external download environment can separate access scope according to file characteristics and customer workflows.
For example, a customer for Project A can be limited to that project's files, with the link becoming unavailable after the specified period.
File Storage
│
┌───────────┼───────────┐
▼ ▼
Customer A Customer B
│ │
Project A Files Project B Files
│ │
7-Day Expiration 30-Day Expiration
Access policies can be separated according to the purpose of file delivery.
| Policy Basis | Example |
|---|---|
| By Customer | Provide a dedicated download link for each customer |
| By File | Allow only specified files or paths |
| By Project | Separate access scope by project |
| By Period | End access automatically after a defined period |
| By Workflow | Separate conditions for review, delivery, or sharing |
This lets you provide customers only the required files and manage the link scope according to the purpose of file delivery.
Large-File Transfer
Provide large files and multiple files in a single download job
When customers need large datasets such as video, design assets, backup files, or project results, multiple files can be provided through one link.
Customers review the available files in the browser and download the required files.
Available Files
├── final-video.mp4 18 GB
├── design-source.zip 9 GB
├── data-export.tar 6 GB
└── report.pdf 12 MB
│
▼
Download Run
│
▼
External Customer
During a download job, reviewing per-file results alongside the overall status makes it possible to identify files that need additional attention.
Automated Provisioning
Connect download-link generation and follow-up work after files are ready
The process of providing a download link after files are created or final results are ready can also be connected to an automated flow.
For example, after processing completes, you can prepare the result files, create a download environment using specified conditions, and notify the assigned team member.
File Processing Complete
│
▼
Prepare Result Files
│
▼
Apply Download Conditions
│
▼
Download Link
│
├──────────────► Notify Assignee
│
└──────────────► Connect Next Task
Connecting downstream work after file delivery extends the workflow beyond simple download into result-file preparation → customer delivery → download verification → follow-up work.
Provisioning History
Operate based on download jobs and per-file processing results
External customer downloads can be reviewed in Runs for overall execution status and processing results.
Selecting a specific job shows which Source files were provided for download, their per-file processing status, and the overall transfer result.
| Item | Details |
|---|---|
| Source | Device or storage containing the download files |
| Source Path | File path provided to the customer |
| Total Files | Number of files to process |
| Total Size | Total download size |
| Progress | Current download progress |
| Status | Download completion and progress state |
| Started | Download start time |
| Completed | Download completion time |
| Link Status | Link availability and expiration state |
If additional review is required, check per-file processing results and link status in the Run details.
If needed, adjust the file-delivery conditions or create a new download link and provide it to the customer again.
With this structure, external customers can download large files through a browser without creating an account or installing separate transfer software, while internal teams can manage file preparation → access-condition setup → download-link delivery → result verification → follow-up workflow connection in one flow.