Use VOTPort on your desktop

Use the macOS or Windows build supplied for your deployment. Request the appropriate installer if you do not already have it. The commands and controls available depend on your client release and account permissions.

Send files

1. Open Send and paste the request link supplied by the recipient.
2. Read the link preview and enter its password if prompted.
3. Choose files or drag files and folders into the drop area.
4. Check your selection, then choose Send.

Files are sent from their existing locations. Keep them available and unchanged until the transfer completes; disconnecting a drive or replacing an in-progress export can prevent a send from finishing or resuming.

Understand preparation before sending

Before upload begins, the native client reads the source files to establish their cryptographic identities. For large files, reading overlaps with hashing across a bounded set of workers; it does not create another payload copy. The server uses the same preparation approach for library deliveries and missing proof catalogs.

Preparation still takes place before network transfer and depends on source storage and CPU capacity. A large selection can therefore spend time preparing before its upload speed appears. Keep source files unchanged, update the client as well as the server, and let preparation finish before diagnosing a transfer as stalled.

Receive a delivery

1. Open Receive and paste the delivery link.
2. Check the preview and enter a password if required.
3. Choose the destination folder.
4. Choose Receive and follow the job in Transfers.

The client checks arriving files against the delivery's announced roots. A completed download and a verification failure are different outcomes: inspect the transfer's status before handing the files to another process.

Understand the finishing stage

Files can become available as they are verified and published while other objects continue downloading. The transfer card shows the completed file count as well as the bytes moved. Wait for the whole job to finish before treating the entire delivery as complete.

After network transfer, Verifying and finishing covers the remaining integrity and publication work. Keep the app open and storage mounted. Completed cards include the file count, size, elapsed time, average transfer speed, and completion time. Total elapsed time includes finishing; the transfer-speed calculation excludes later verification and bytes reused from an earlier attempt.

Pause and resume

The Transfers view shows active and previous jobs. Expand a transfer to inspect its route, details, and file progress. Use Pause for a job you intend to continue and Resume when its source, destination, and connection are available again. A protected transfer may ask for its password again.

Use Cancel when you intend to stop the transfer. Removing an entry from the list is not a way to revoke a shared delivery link; revoke that link in your port's delivery controls.

After a successful receive, use Show in Finder or Show in Explorer to locate the files. If a job reports an error, record its transfer ID and error text before removing its history entry.

Work with your port

In Settings, enter your deployment address. Use Sign in with SSO when your deployment offers it, complete the sign-in in your browser, and return to the app. The browser handoff belongs to the sign-in attempt started by that app. Local password sign-in remains available where your administrator permits it.

Signed-in operators see Share and Manage links. Share opens the file and library picker; Manage links creates requests and lists requests and deliveries. Signing out removes those operator sections. A request or delivery link can still be used without administrator access.

Check the active tenant and your account permissions before issuing links. Finish a Share form before navigating away: its unsent selection is local to that view.

For repeated folder-based exports or scripted jobs, see the command-line guide.

Manage delivery workflows

Open Workflows to choose a project, enter required metadata, select enrolled recipients, and queue a delivery. Follow preparation and check errors, reception jobs, and per-destination status. Copy released links, retry failed jobs, or cancel them. A local-release project can expose its link while remote copies remain pending, so check destination status separately. Authorized human approvers can review and approve a manifest; the submitter cannot approve their own job.

Use Project rules, schedules, storage and events to open the browser’s Workflows page for project configuration and scheduling. Storage connections now have a separate Storage page; browser-issued agent tokens live in Automation. The desktop Workflows screen shows local recipient verification and acceptance, your device public key, and a control to retry pending reports. Acceptance is an explicit action after reviewing the verified files.

See delivery workflows and recipient evidence. Update the desktop app as well as the server to obtain these screens and the current bundled MCP adapter.

Connect an agent or automation tool

While signed in, open Settings > Agent access. Issue a token with a label, project folder, expiry, and the actions your integration needs. Copy the token immediately; it is only displayed once.

The macOS and Windows apps bundle the client CLI. Copy MCP configuration uses its installed path so an MCP host can start it directly. Keep the configuration in the host’s private settings because it contains the token. Agent credentials are independent of your desktop sign-in: signing out does not revoke them.

You can revoke tokens in Settings. Delivery links already issued by a token keep their own expiry and access controls; manage those separately in Manage links. The automation guide covers permissions, all 15 MCP tools, and recovery after an interrupted request.

Background progress and notifications

The macOS menu bar and Windows tray provide access to active transfers without keeping the main window in front. Transfer notifications can report completion or failure; app settings control whether those notifications and their completion sound are enabled.

Keep the application running for active work. A notification is a useful prompt to check the finished transfer and destination, especially before deleting the source copy.

Troubleshoot a transfer

What you see	What to check
A link cannot be used	Confirm its type, password, expiry, and whether its owner closed or revoked it.
A transfer stops partway through	Keep the original files in place, check connectivity and free disk space, then inspect the resume control.
A destination cannot be written	Confirm that the chosen folder exists, is writable, and remains mounted.
Native transfer is unavailable	The deployment may not expose its native endpoint, or the network may block UDP. Ask your administrator about the supported HTTP path.
Verification fails	Keep the error details and contact the delivery owner. Do not treat the affected file as verified.

When requesting support, include the client version, operating system, approximate time, transfer ID, and error text. Do not include passwords or private transfer links in a public issue.