EXTERNAL PARTNER FILE TRANSFER
Open only the file transfers
an external partner needs.
Exchanging files with a partner does not mean granting access to your whole internal system.
Offer each partner only the file transfer jobs it is allowed in INNORIX Portal. The partner runs the prepared job itself, and your company manages the transfer targets, the conditions for running and the results.
PARTNER-SPECIFIC ACCESS
A partner sees
only its own transfer jobs.
Several partners may work with the same company without any of them needing access to the same systems and files.
Separate the transfer jobs each partner is allowed, so every user sees and runs only the work that is theirs.
- Partner A
- Partner B
- Partner C
Example jobs3
- Project material distributionCompany system → partner devices
- Delivery dataPartner → company system
- Test result collectionExternal test devices → central system
The point is that partner A never sees partner B's transfer jobs.
CONTROLLED SYSTEM ACCESS
Protect the internal system;
connect only the paths you need.
Allowing an external partner to transfer files does not mean exposing every folder and every device on your internal servers.
Configure the permitted devices, paths and transfer direction in Studio, and give the partner Portal only the options that job needs.
The partner transfers files inside a defined scope, and your company manages how far it reaches into the internal system.
- Partner AAccess active
- Partner BAccess active
- Partner CAccess active
Once the permitted devices and paths are set in Studio, the destinations the Portal offers are limited to that scope.
Project Alpha — Authorized accessAccess active
- Delivery dataPartner → company system
- Project material distributionCompany system → partner devices
There is no unrestricted browsing of the internal system and no arbitrary path to type.
PARTNER WORKFLOWS
Give each partner
the transfer job its work needs.
The file transfers a partner needs change with its role and its project.
A manufacturing partner delivers production data, a development partner's test results are collected, and a project partner receives the material it needs.
Rather than developing a separate transfer program for every job, connect the transfers prepared in Studio to the Portal.
- Delivery dataPartner → company system
- Test result collectionExternal test devices → central system
- Project material distributionCompany system → partner devices
Choosing a type of job changes the transfer direction, the connected devices, the file selection area and the run conditions together.
APPROVAL & TIME WINDOWS
Run it only with approval,
and only inside the permitted hours.
An external partner's file transfer may need stricter run conditions than internal work does.
Require the approval of the responsible person before a transfer, or allow it only at a designated time, and keep both the partner's convenience and your own operational control.
- Partner requestPartner transfer request — Pending approval
- Internal approvalApproval: Waiting / Execution: Not started
- Ready to runThe approver's decision appears in the partner Portal.
- Transfer startsProject Alpha Data Delivery — Partner A → Project Storage
SHARED TRANSFER VISIBILITY
No more asking, every time,
how far along it is.
Once a partner has started a file transfer, it can see the run state and the result in its own Portal.
The company's operator sees the same transfer job in Studio, which cuts the repeated emails and phone calls asking whether it has finished.
Delivery dataReady to run
- Delivery dataPartner → company systemReady to run
When the partner starts the transfer in its Portal, the same run appears in Studio Runs.
PARTNER ACCESS LIFECYCLE
When the work is over,
tidy up the access too.
When a project ends or a partner changes, the transfer access it held has to be reviewed as well.
Manage each partner's transfer jobs and access scope, and run it so that access nobody needs any more is disabled or withdrawn.
Example jobsNo longer runnable
- Delivery dataPartner → company system
- Project material distributionCompany system → partner devices
- Access activePartner A — Active — Transfer access: Enabled
- Project endsThe transfer access it held is reviewed with it.
- Access disabledAccess nobody needs any more is disabled or withdrawn.
- No longer runnableThe job can no longer be run from the partner Portal.
How far each partner's access can be managed follows the permission specification of the product itself.
GET STARTED
Build a file transfer environment for your partners.
Configure the transfer jobs and the access scope you want to give an external partner in Studio and connect them to the Portal. The partner runs what it is allowed, and you can check the result.
TECHNICAL FAQ
Frequently asked questions
Can an external partner use INNORIX Portal too?
Yes. An external user who has been granted permission can be set up to run pre-configured device-to-device file transfer jobs in the Portal and to check the results.
Can each partner be given different transfer jobs?
Composing a permitted Portal and transfer jobs per partner gives each one a different scope to run.
Does the whole internal server have to be exposed to an external partner?
No. It can be set up so that only the permitted devices, paths and transfer jobs are reachable.
Can a partner upload or download files from its own PC?
The standard Portal is a feature for running transfers between connected devices. Upload and download between a partner's own PC and a website has to be built with INNORIX EX or as a separate customisation.
Does INNORIX Agent have to be installed on the partner's server as well?
For direct device-to-device transfer, the partner's system has to be registered with INNORIX over a supported connection method. An Agent is the standard approach for an ordinary server, while object storage and the like may be connected another way.
Can an approval step be applied to a partner's file transfer?
Supported approval policies can separate a transfer request from its execution. The approval steps and who handles them have to be confirmed against the product specification.
Can the hours of a partner's file transfer be limited?
Supported time windows and execution policies can be used to have transfers run at particular hours.
Can the company and the partner see the same transfer progress?
The partner sees its own execution state in the Portal, and the company's operator sees the result of that transfer in Studio Runs.
Can a partner's access be blocked once the work is over?
An operating procedure has to be in place to disable or withdraw the accounts and Portal access involved. The management features available have to be confirmed against the product's permission specification.
How is this different from a service that gives a partner a download link?
INNORIX Portal runs and monitors transfer jobs between devices connected in advance. Letting a general user download a file over a web link is the territory of INNORIX EX.
Every one of these capabilities,on a single platform.
The capability on this page is one of the many file transfer features INNORIX Platform provides. From file transfer to automation and unified operations, try every feature free.
Start FreeLooking at file transfers with your external partners?
We review the transfer jobs each partner needs, how far they reach into your internal systems, and the approval and time-window conditions, with you.
- Review of the transfer jobs and Portal for each partner
- Design of the internal access scope and permitted paths
- Guidance on applying approvals and permitted hours