Let an outside partner run the transfers they are allowed to
When a partner has to hand over material or move files into a nominated system, they do not have to ask your IT team to run it. Define the transfer jobs and the access scope the partner will use in INNORIX Studio, and the partner contact can pick an allowed job in Portal, run it, and follow the progress and the result. Server accounts and the full device list stay internal, while run permissions are split job by job.
The partner does not browse every server you run — they only run the device-to-device transfers approved in advance. Letting an outside user attach a file from their own PC in the browser to upload it, or pull a server file down, is not what Portal is for. Web upload and download belong to INNORIX EX. If a device on the partner side is the source or the target of a transfer, that device has to be connected in a supported way too.
Comment c'est construit
- Agree which systems the transfer involves.
Confirm the devices to be used, such as your internal server and the partner server, the file paths to allow, the direction of the transfer, the contact and the business purpose. For a device-to-device transfer, check that both devices can be connected and review the network and security policy on each side.
- Build the partner Flow in Studio.
Using the devices connected in Devices, set the source and target paths and configure the file selection scope, the overwrite policy and, if needed, a run time window. Leave any server or path the partner should not reach out of the job scope.
- Publish the job in Portal and limit the external user.
Grant the partner account or role nothing beyond view and run permission on that job. Where a job needs approval, configure it against the approval policy the product actually supports.
- The partner runs the transfer from Portal.
They open the permitted job, check the files, destination and run conditions shown, then start the transfer. If the same job is already in progress, point them at the existing run.
- Check the progress and the result.
The partner sees the transfer result in Portal, while your operators review the run state, errors and anything audit needs in Studio Runs. When the project ends or the contract expires, revoke the partner access.
Où c'est utilisé
- Delivery data from a manufacturing partner
A parts supplier sends delivery manifest files from their connected server to the receiving server the manufacturer nominated. The supplier runs only the permitted job and cannot see any other internal server.
- Build output from an outsourced developer
An outsourced development team sends a release package from the partner build server to the client verification server. The actual deployment and installation stay under a separate approval and run procedure.
- Video production and post-production servers
An outside production house moves large video sources or finished output between permitted working servers and confirms the transfer finished, with no personal-PC download through a browser.
- Regular submissions from a logistics partner
A logistics company sends shipping and delivery result files produced on its own server to the client collection server, and the contact confirms the submission.
- Results from an external test lab
A test lab sends quality inspection reports from its connected server to the customer review server. File paths and access scope are separated per lab so that material from one partner is never exposed to another.
- Time-limited transfer permission per project
An outside consultant is allowed to run transfers between two nominated servers for the length of the project only, and the account and job permissions are revoked when it ends.
- Keeping partners separate from each other
Several partners can use the same platform while each sees only the jobs and run results they are permitted, and internal operators review everything from the full Runs list.
Guides d'utilisation
Questions fréquentes
Is there software that lets an outside partner run a file transfer without help from our IT team?
INNORIX is an enterprise file transfer platform you can design so that internal admins build the device-to-device Flows in Studio and partner contacts run the permitted jobs directly from Portal. The partner never has to handle transfer scripts or an admin console.
Can we allow a partner to transfer files without giving them an internal server account?
Yes. Internal operators keep control of the device connections and transfer paths, and the partner is granted only permission to run the nominated Portal jobs. How far account, role and device access control goes should be verified on the version you deploy.
Does an outside partner end up able to see every server and file?
As a matter of principle, that is not how it should be run. Limit, per partner, which Flows, devices and file paths are permitted and which run results are visible. Test with a real partner account that devices and jobs they have no permission for do not appear on screen.
Can a partner upload files from a personal PC or download them through a browser?
Portal itself is used for running and monitoring predefined device-to-device file transfers. If the purpose is for a partner to attach a file from a personal PC and upload it, or pull one down through the browser, INNORIX EX is what to look at. Access to the Portal explorer does not amount to a browser download permission.
Can files be transferred directly from a partner server to ours?
If both systems are connected in a way INNORIX supports and the network and permission conditions are met, you can build a transfer Flow between a partner device and an internal device. Simply sending a partner a Portal link does not make files on an unconnected external PC transferable.
Can partner transfers be limited by approval or to certain hours?
Per-job approval and run time windows can be considered. Approvers, approval states, time window settings and how they are enforced have to be checked against what the product implements — a screen it does not support should not be described as standard.
Can different partners be given different transfer permissions?
You can design this by separating accounts and roles per partner and scoping which jobs each one sees in Portal. Permission testing is needed to confirm that no partner can view the Flows, source and target paths or run results of another partner.
Can we see internally what transfers a partner ran?
Studio Runs shows the run state and result. To use it for audit — who ran which job — verify on your live environment how Portal user identity is tied to the Run record, how long records are kept, and how permissions are revoked.