---
title: Using VOTPort
label: Using VOTPort
description: The everyday workflows for your facility’s VOTPort deployment.
layout: docs
order: 105
---

Begin with [your first transfer](/docs/using/getting-started/) if you are new to the deployment. The two link types have different purposes: a request accepts files; a delivery provides them.

## Receive files

[Create a request](/docs/using/receiving/), share its link, and find the completed files at your configured destination.

## Deliver files

[Prepare a delivery](/docs/using/delivering/) from your outbound library. Set the conditions of the handoff and share the recipient's link.

## Verify a receipt

[Check the file against its signed receipt](/docs/using/verification/) and understand what its recorded assurance means.

## Desktop and automation

Use the [desktop clients](/docs/using/desktop/) for local sends and downloads, or the [command-line client](/docs/using/command-line/) for scripted transfers and watched folders.

## Repeat work and recovery

Use [automation](/docs/using/automation/) for watched exports, scoped API access, and MCP agents that create, inspect, recover, and revoke deliveries. If a handoff stalls, [troubleshooting](/docs/using/troubleshooting/) explains preparation, native connectivity, download allowances, and verification failures.

## Govern a package from preparation to acceptance

Use [delivery workflows](/docs/using/workflows/) for persistent jobs, required checks, approval, scheduled starts, and acceptance deadlines. Track signed verification and explicit recipient acceptance against the exact files.

## Route incoming work

[Reception projects and trade routes](/docs/using/reception/) apply checks and approval to completed uploads, distribute copies to multiple destinations, and retain signed custody across VOTPort deployments.

## Get help with your deployment

Your administrator supplies your VOTPort address and account access. [Contact us](/contact/) to discuss facility deployment or a workflow that needs a different setup.