Start using your deployment
Find your workspace, understand the two kinds of link, and complete your first handoff.
On this page
Get your address and access
Your administrator provides an HTTPS address such as https://transfer.example. This is your port. It is separate from the marketing and documentation site at votport.com.
Open the address to sign in with the method your administrator configured. If SSO is available, use your organization’s sign-in. Access to the administrative workspace depends on your role and tenant membership.
If you only need to send or download files, use the request or delivery link you were given. You normally do not need a port account.
Understand the two kinds of link
| Link | What the person opening it does | Who prepares it |
|---|---|---|
Request, with /r/ in the path |
Sends files into the request’s destination | The team receiving the files |
Delivery, with /s/ in the path |
Downloads a prepared selection of files | The team delivering the files |
The browser workspace calls these areas Receive and Deliver from the operator’s point of view. The desktop app’s Send and Receive describe what happens on your computer: Send uploads to a request; Receive downloads a delivery.
Make a first request
- Sign in and select the correct tenant if your account has more than one.
- Open Receive and create a clearly labeled request.
- Set the destination subfolder, expiry, password, and size limit your workflow needs.
- Copy the link and send a small test file through it.
- Confirm the completed file appears in the receive destination and locate its receipt.
The receiving guide explains the sender’s view and what happens after an interruption.
Make a first delivery
- Open Deliver and choose a file from the outbound library, or upload a test file.
- Issue a delivery link with suitable expiry and download limits.
- Open the link as a recipient and download the file.
- Check the saved bytes with the receipt when verification is part of your handoff.
- Revoke the test link when you are finished.
A download start in the history is not proof that a browser saved the full file. Use the verification guide when you need evidence about the received bytes.
Set the expectations for real work
Agree where files should land, who monitors completion, how long they remain available, and who can revoke or delete them. A link expiry controls access through that link; it is not a file-retention policy.
Use a native client when you need direct folder receives, recoverable jobs, or native QUIC. For a one-off collaborator, a browser may be all that is needed.