Browser workspace

Prepare, govern, and follow every package from one workspace.

The browser workspace is RIPTON CLOUD's control plane. It gives senders and operators a clear place to assemble a package, choose recipients, apply supported lifecycle controls, and understand what happened without moving local file paths through the page.

RIPTON CLOUD / Browser workspace
01

entry

Files + recipients

02

control

Package policy

03

transfer

Desktop or Web Edge

04

evidence

Status + activity

Why it matters

A product capability tied to an operational outcome.

01

One package workflow

Prepare recipients, files, metadata, notes, and supported delivery controls without stitching together separate upload and tracking screens.

02

Control before movement

Authorization and package policy remain in the browser control plane while Desktop, Web Edge, nodes, and relays handle package bytes.

03

Visible delivery state

Follow package, recipient, transfer, and completion state from the same workspace used to begin the handoff.

How it works

From entry point to evidence.

The workflow stays understandable at every stage, with the control plane coordinating policy and the data plane moving supported workloads.

  1. STEP 01

    Choose files

    Select files through RIPTON Desktop or an eligible Web Edge path while keeping local paths out of the browser page.

  2. STEP 02

    Prepare the package

    Add recipients, a title, metadata, notes, and supported release, expiration, passcode, and download controls.

  3. STEP 03

    Authorize the path

    RIPTON applies package and recipient policy before issuing the transfer setup for an eligible endpoint.

  4. STEP 04

    Follow delivery

    Review progress, recipient access, completion, forwarding where allowed, and package activity.

Capability detail

What your team can inspect and use.

Packages and recipients

Organize file movement around a named package and the people or destinations that should receive it.

Lifecycle controls

Apply supported metadata, release timing, expiration, passcodes, download limits, archiving, and retention settings.

Role-aware views

Keep user, operator, and administrator responsibilities separated through the product's current role model.

Recipient continuation

Carry the workflow through notification, secure access, download, forwarding where permitted, and completed delivery state.

Operational evidence

The workspace controls the transfer; it does not carry the bytes.

Separating control from data movement keeps package policy, authorization, and status understandable while the eligible transfer path handles the workload.

  • Package and delivery status
  • Recipient and activity context
  • Selected transfer path
  • Completion and transfer history

Frequently asked questions

Technical questions, answered plainly.

Does the browser upload local file paths?

For the Desktop path, local selection and movement are handled by RIPTON Desktop; the browser coordinates the package and receives status without needing the local paths.

Can a recipient forward a package?

The receiver experience can include forwarding when the package and delivery policy allow it.

Can administrators see transfer state?

Yes. Current product surfaces expose package status, selected path, transfer state, activity history, and operational diagnostics according to role.

Evaluate the workflow

Walk through the package lifecycle with your own workflow.

Bring one sender, recipient pattern, package policy, and transfer route. We will show how the browser workspace coordinates the handoff from preparation through completion.