Vianordis
--:--:-- UTCVianordis / SUPPORT
collaboration

Viaport

Beta

Viaport creates time-limited zero-knowledge file transfers. Files and metadata are encrypted in the sender's browser, and the decryption key stays in the URL fragment rather than being sent to the storage service.

Open Viaport
Beta operating manual

Viaport beta transfer manual

Create and receive zero-knowledge encrypted file transfers while protecting the complete link, password, and deletion settings.

Manual
Version 1.0
Product
Viaport live frontend 1.0.0 beta
Verified
July 15, 2026
Language
English · Source
Owner
Viaport product and support
Source
viaport · 65c49bf
Review cycle
45 days
Start here

Audience, scope, and prerequisites

Covers the live Viaport v1 browser workflow for one-file encrypted transfers, expiry, download limits, password protection, recipient-device mode, sender dashboard, and deletion. Viaport is not shared storage, a folder workspace, or a versioned collaboration service.

Who this is for

  • People sending an encrypted transfer
  • Transfer recipients
  • Viaport support and security staff

Before you sign in

  • A supported browser with WebCrypto
  • Approval to transfer the file to the intended recipient
  • An approved channel for the complete link and a separate channel for any password
  • A retained source copy because Viaport is not an archive
Access model

Roles and responsibilities

RoleAccessResponsibilities
SenderEncrypt and upload a file and manage owned transfers.
  • Set minimum expiry and downloads
  • Protect the complete generated link
RecipientDecrypt and download with the complete link or approved recipient-device flow.
  • Use the intended device
  • Protect downloaded copies
SupportDiagnose service metadata and transfer state without possessing the fragment key.
  • Never request a decryption fragment
  • Explain irrecoverable-key behavior
Workspace map

Navigation

Home

/

Review the transfer service and start upload or sign-in.

Upload

/upload

Encrypt one file in the browser and create a transfer.

My Files

/dashboard

Review and delete transfers owned by the signed-in sender.

Download

/d/{id}#{key}

Decrypt a transfer using the key in the URL fragment.

Chapter 01

Create a transfer

The browser generates the key and encrypts file content and metadata before upload; losing the fragment loses access.

Procedure 1.1

Configure and upload a transfer

Choose the minimum lifetime and download exposure needed for the purpose.

  1. 1
    Prepare one file

    Confirm recipient, classification, size, malware checks, and that a retained source copy exists.

  2. 2
    Open Upload

    Select the file and review its displayed identity.

  3. 3
    Set expiry

    Choose 1, 3, 7, 14, or 30 days according to the shortest approved transfer window.

  4. 4
    Set download controls

    Use delete-after-download or a maximum download count when compatible with the recipient workflow.

  5. 5
    Set password protection when required

    Use a unique transfer password and plan a separate delivery channel.

  6. 6
    Encrypt and upload once

    Keep the page open while key generation, encryption, and upload complete.

Expected result

One encrypted transfer is stored and the browser displays a complete share link and expiry.

Chapter 02

Receive and close a transfer

Download on the intended device, verify the file, and remove the transfer when the business purpose ends.

Procedure 2.1

Decrypt and download a transfer

Use the complete link and verify the result before relying on the file.

  1. 1
    Open the complete link

    Use the intended browser/device and preserve the # fragment.

  2. 2
    Enter the password if prompted

    Use the separately received password; do not send it back through the link channel.

  3. 3
    Review metadata

    Confirm sender context, filename, expiry, upload time, and download state.

  4. 4
    Download once

    Allow encrypted download, browser decryption, and local save to finish.

  5. 5
    Validate the file

    Check file identity, expected content, and integrity through the approved method.

  6. 6
    Move or delete locally

    Place it in approved storage or remove the temporary copy according to policy.

Expected result

The intended file is decrypted locally and handled under its original classification.

Procedure 2.2

Review or delete an owned transfer

Use the dashboard to inspect current limits and remove access early.

  1. 1
    Open My Files

    Sign in and locate the transfer by decrypted name and creation time.

  2. 2
    Review state

    Check expiry, download count, maximum downloads, and delete-after-download state.

  3. 3
    Confirm the business need

    Ask whether the recipient still requires access.

  4. 4
    Delete when complete or exposed

    Use Delete and verify the transfer disappears.

Expected result

The sender understands remaining exposure or removes the transfer before natural expiry.

Procedure 2.3

Handle a recipient-device transfer

Complete the device-bound flow on the intended linked device.

  1. 1
    Open the link on the intended device

    Recipient mode may legitimately have no URL fragment.

  2. 2
    Read the private-transfer notice

    Do not attempt standard fragment decryption when the page identifies a device transfer.

  3. 3
    Complete the approved device linking flow

    Use only the client and device specified by the organization.

  4. 4
    Escalate unsupported state

    Do not copy keys or attempt to bypass device binding.

Expected result

The transfer is opened only through the intended recipient-device mechanism or is safely escalated.

Operating rules

Security and data handling

  • Treat the complete fragment-bearing link as a decryption secret.
  • Send transfer passwords through a separate approved channel.
  • Use the shortest expiry and smallest download count that meet the purpose.
  • Retain the source elsewhere; Viaport is not archival storage.
  • Delete the transfer early if the recipient completes the task or exposure is suspected.
Current release

Known limitations

Read before relying on an unsupported workflow

These limits describe the source-pinned Viaport live frontend 1.0.0 beta scope and must be rechecked when the product changes.

  • Viaport supports discrete transfers, not folders, team permissions, collaborative editing, previews, or version history.
  • The service cannot recover a lost or stripped decryption fragment.
  • Delete-after-download can remove availability after the first completed download and may not suit multi-device workflows.
  • Browser memory, file size, connection, and local storage constrain large transfers.
  • The viaport-v2 frontend is preview-only; this manual follows live v1 behavior.
Problem solving

Troubleshooting

You cannot sign in to Viaport

Likely cause: The session expired, the identity is not assigned to the application, or the tenant claim is missing.

  1. Open the application from the approved portal and complete sign-in again.
  2. Confirm that the correct organizational identity and tenant are selected.
  3. If access is still denied, record the time and request an entitlement check from support.

A documented action or navigation item is not visible

Likely cause: The current role, release, tenant configuration, or feature flag does not expose that operation.

  1. Confirm the role and prerequisites listed for the procedure.
  2. Reload the page after signing in again; do not attempt to bypass the interface through direct URLs.
  3. Ask the product owner whether the feature is enabled for the tenant before reporting a defect.

A saved change or background operation is not visible

Likely cause: Validation failed, processing is still running, or the current view is stale or filtered.

  1. Review inline validation, status indicators, filters, and the selected tenant or workspace.
  2. Refresh once and search for the item by its stable name or identifier.
  3. Do not repeat irreversible or externally visible actions until the original operation status is known.

The page reports a missing key or decryption failure

Likely cause: The # fragment was stripped, copied incompletely, altered, or belongs to another transfer.

  1. Compare the link through the sender’s original success page or secure record.
  2. Ensure the fragment after # is present and no characters were changed.
  3. If lost, create a new transfer; support cannot reconstruct the key.

The transfer is expired, deleted, or over its download limit

Likely cause: The configured lifecycle condition has been reached or the sender removed it.

  1. Do not attempt to bypass the state.
  2. Ask the sender to verify dashboard status.
  3. Create a new bounded transfer from the retained source when still authorized.
Escalation

Contact support

Contact support when

  • A repeatable Viaport error blocks an approved workflow
  • Expected data, permissions, or tenant boundaries appear incorrect
  • A security, privacy, compliance, or data-loss concern is suspected
  • A complete link or password may be exposed
  • A transfer downloaded or deleted unexpectedly
  • Recipient-device mode cannot be completed safely

Include

  • The page, action, and expected result
  • The exact error text and time of occurrence, including time zone
  • Your tenant, role, browser, and a sanitized record or item identifier
  • Whether the problem can be reproduced and which troubleshooting steps were tried

Never include

  • Passwords, access tokens, API keys, recovery codes, or session cookies
  • Unredacted personal, health, financial, or other regulated data
  • Private encryption keys or complete confidential documents unless an approved channel is provided
  • The complete URL fragment or transfer password
Contact support