Focused experience
Let an external user upload to or download from the intended package without exposing the internal administration interface.
Public links
Give an external user one focused upload or download path.
A public link should be simple for the participant and narrow for the operator. RIPTON CLOUD separates public browser access from named-user administration and issues supported transfer setup only after the relevant package or invitation policy is satisfied.
RIPTON CLOUD / Public links
01
entry
Public URL
02
control
Passcode or invite
03
transfer
Scoped operation
04
evidence
External activity
Why it matters
A product capability tied to an operational outcome.
Short-lived scope
Keep supported external credentials time-bounded and tied to one resource and operation.
Current-state checks
Re-evaluate package, delivery, invitation, and access state when the external operation is used.
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.
- STEP 01
Create the entry point
Choose a supported package upload, package download, or Shared Inbox upload experience.
- STEP 02
Apply access policy
Configure the relevant passcode, invitation, expiry, package state, and supported download controls.
- STEP 03
Authenticate externally
The participant opens the focused page and satisfies the required package or invitation check.
- STEP 04
Issue narrow transfer setup
RIPTON provides only the upload, view, download, Desktop, or eligible Web Edge setup allowed for that resource.
Capability detail
What your team can inspect and use.
Distinct external scopes
Upload, view, download, and Shared Inbox upload remain separate operations rather than one broad external permission.
Time-bounded credentials
Supported signed external credentials expire and are rejected when incomplete, altered, or used for another resource.
Revocable access
Cancellation, blocking, expiry, removal, or invitation changes can deny later operations when state is checked.
Separate transfer credentials
Node-facing Desktop or Web Edge setup is issued only after the external access policy is applied.
Operational evidence
Reachable by URL does not mean unrestricted.
The public route can be opened without an internal session, but the supported operation remains tied to the intended credential, resource state, scope, and transfer policy.
- Package or inbox identity
- External credential and expiry
- Allowed operation and selected path
- Recipient or external activity context
Continue exploring
Related platform and solution pages.
Shared Inboxes
Use a reusable destination for repeat external intake.
Explore →Web Edge
See how eligible browser transfer setup is issued.
Explore →Secure partner exchange
Design a governed external handoff around the link.
Explore →Share a package with a public link
Set a passcode, copy the link, share the two separately.
Explore →Compared with WeTransfer
Where a consumer sharing link stops and a scoped package link starts.
Explore →Send large files
Recipients who need no account and no paid seat.
Explore →Frequently asked questions
Technical questions, answered plainly.
Are RIPTON public links completely anonymous?
No. Public routes are reachable without an internal login, but supported transfer actions require the intended package passcode or approved Shared Inbox invitation and remain scoped to one resource and operation.
Can access be stopped before a token expires?
Current package, delivery, and invitation state is checked when supported access is used, so cancellation, blocking, expiry, or removal can deny later operations.
Does the public user see internal administration?
No. The external experience is focused on the approved package or Shared Inbox operation rather than the internal administration workspace.
Evaluate the workflow
Test the public experience from both sides.
We will review what the external participant sees and what the operator can configure, observe, revoke, and support.