Device and workspace access

Sign-in authenticates you; workspace membership/policy and exact device authority permit work. Current human policy can give workspace-wide ordinary access while retaining older selected-device assignments for compatibility. Admin-only settings, team governance and unused-share extension remain distinct. Visibility never grants Rescue owner control or machine-principal human rights.

Access lifetime

Daemon makes outbound native relay connections, not an inbound LAN listener. One technician identity controls a device at a time; several channels may share that lease. Login and current workspace authority remain required; short internal grants renew only within the original approved task.

With Bridge 1.21.214, Daemon 0.24.0 and CLI 0.39.0, a new support request defaults to until End or device restart. Pending requests have no countdown. Approval survives lock, sleep and sign-out, but does not transfer to another task, actor or replacement request. End, cancellation, task-owner termination and revoked authority stop access. Reopen the original local controls when returning after sign-out; an interruption never authorizes replaying a command.

Existing timed approvals retain their actual limits. An explicit --minutes request keeps the bounded 1–60-minute behavior and its accepted-start limit. Unsupported components refuse the new lifetime instead of silently falling back. Local Allow/End and fresh OS-admin approval remain authoritative.

Commands, transfers and diagnostics have no implicit total-runtime or quiet-output deadline. Explicit cancellation remains available. Connection establishment and cleanup are bounded independently; a failed connection is not a completed operation. Events use UTC; interfaces may display those instants in the viewer's local time.

Work and history

A channel being open is not completed work. End/expiry/revocation stop authority; channel loss does not prove remote cleanup. Exact original IDs distinguish enrolled and temporary targets, including after promotion. Owner cleanup can report an ended Rescue period without restoring control. Work-history access is reauthorized and bounded; stale or missing evidence is not success.

Work sessions count device-accepted operations, not login, keepalives, stored reads or background health. The same target/workspace/date can be shared by technicians, conversations and runs; running silent work remains continuous. Billing does not authorize execution or blindly stop an already-running repair.

Lightweight device health

See Automations and health for cumulative Disabled/Light/Full scope, local veto and configured-versus-observed evidence. Reading a health page never collects or applies monitoring. See CLI and API for authorized agent contracts.

Enroll a device

Use the current exact shared page/package workflow, choose target-computer platform and access mode, and retain private output/code. Local target approval and current issuer/device capacity remain independent. Shared issuance/replacement is separately enabled; uncertain replay can return status without a secret URL. See Rescue.