Endpoint lost or offline
Use scoped snapshot browse and single-file download from a clean browser. The stored-data path does not contact the original endpoint.
Arivaran Twin
Browse a completed recovery point and download one file when your signed-in dashboard role and organization scope permit it. Assigned-owner-only recovery and in-place restore are not available yet.
This page does not promise owner-only self-service, an in-place restore job, migration to another endpoint, or a bootable Twin. Those paths remain unavailable or planned until their authorization, execution, audit, and failure behavior are accepted.
Verified path
The original endpoint can be offline because browsing and file reassembly use the stored catalog and content blocks. Access still depends on a valid identity, role, tenant, and organization scope.
Three supported beats end at a single-file browser download. No in-place restore is depicted.
Step 1: Store a recovery point
An enrolled endpoint must complete a snapshot with a persisted file catalog.
Step 2: Browse the snapshot
A signed-in role with file browse permission can open the stored catalog inside its tenant and organization scope.
Step 3: Download one file
A role with file download permission can reassemble one stored file in the browser.
Outcome matrix
Availability belongs to each outcome, not to Twin as one broad promise. Every available row carries its access and data conditions.
| Outcome | Status | Condition |
|---|---|---|
| See only assigned endpoints | Unavailable | Unavailable for owner self-service. Owner-only enforcement is not accepted across endpoint, snapshot, browse, and download requests. |
| Browse stored files | Available | Available after a completed snapshot with a persisted catalog, for roles with file browse permission inside their tenant and organization scope. |
| Download one file | Available | Available for roles with file download permission when the snapshot and stored content blocks are accessible. Folder and whole-snapshot export are not included. |
| Restore to the original endpoint | Unavailable | Unavailable on this public journey. The dashboard currently obtains a restore plan but does not provide accepted dispatch and completion evidence. |
| Original endpoint lost or offline | Available | Stored browse and single-file download remain available under the same access conditions. This does not make in-place restore possible. |
| Identity compromised | Unavailable | Unavailable as a bypass. Recover or revoke the identity through the configured identity provider or an authorized administrator first. |
| Restore to another endpoint | Unavailable | Unavailable. A different target is not dispatched by the current dashboard restore request. |
| Boot a full Twin | Planned | Planned. No bootable endpoint replica is marketed as generally available. |
| Owner policy and audit proof | Unavailable | Unavailable as an accepted owner journey. Durable allow and deny records, outcome linkage, and failure-path evidence are still required. |
Recovery boundaries
Twin can recover stored data only after identity and authorization succeed. Device loss does not weaken those gates.
Use scoped snapshot browse and single-file download from a clean browser. The stored-data path does not contact the original endpoint.
Twin does not bypass sign-in, revocation, or administrator controls. Recover the identity before requesting data.
In-place execution, restore to another endpoint, owner-only acceptance, and full boot remain outside the available claim.