Attended and Unattended Support Context in Splashtop
An educational look at attended support with a 9-digit session code and unattended access to managed devices, focusing on what should be clear before, during, and after access.
Splashtop as a Session Boundary Example
Compare attended support with a user-provided 9-digit code and prior authorization for unattended managed devices. The focus is permission, actions, confirmation, and closure.
Attended Support with a 9-Digit Session Code
Splashtop describes on-demand attended support using a 9-digit session code. The user is present at the device. The code helps establish the connection; technician identity, permission, the approved device, and the task still need to be agreed separately.
- Request: Identify the expected technician, target device, and support purpose through a trusted channel.
- Permission: Explain screen visibility and remote input, and obtain approval before the session.
- Session and Action: Keep the user informed and reconfirm permission when scope or participants change.
- Confirmation and Closure: Ask the user to verify the outcome, then confirm that active access has ended.
> Client Application Launched: SessionToken [9-Digit] Generated
> Technician Requests Binding via Relay Gateways
> Host Prompt: "Allow remote control session?" -> ACCEPTED
> State: ACTIVE_ATTENDED [Audio, Display, Pointer Attached]
Use the product’s documented disconnect controls and verify the active connection’s end. Do not rely on an assumed code lifetime as a substitute for closure confirmation.
Unattended Access to Managed Devices
Splashtop distinguishes unattended access to managed devices from on-demand attended support. The device owner or authorized organization should approve the specific device, technicians, purpose, and access window before work begins.
- Authorization: Confirm the owner or delegated approver and the approved managed device.
- Scope: Specify permitted actions, technicians, and access windows; device availability alone is not permission.
- Communication: Agree on notifications, interruptions, and how ongoing authorization can be withdrawn.
- Closure: End the active connection, report the result, and separately record any continuing managed access.
| Security Layer | Attended | Unattended |
|---|---|---|
| User Presence | Present for the attended task | May be absent under prior approval |
| Permission | Task and device agreed with user | Owner-approved managed-device scope |
| Actions | Visible work and scope confirmations | Approved window, actions, and records |
| Closure | User outcome and disconnection confirmed | Owner notified; ongoing access stated |
Organizations must enforce principle-of-least-privilege by separating ad-hoc helpdesk technicians from unattended server pools.
Determine Your Required Splashtop Session Boundary
Choose the user-presence and ownership context to explore which permission questions should be answered. This educational example does not connect to a device.
Attended On-Demand (9-Digit Code)
The user is present. Confirm the technician, one approved device, the purpose, and the pause or disconnect procedure before considering attended access.
Mandatory Boundary Safeguards:
- Obtain verbal/ticket confirmation before requesting the 9-digit key.
- Verify technician identification on user prompt before elevation.
- Confirm explicit session termination upon completion.
Request → Permission
PERMISSION TO CONFIRMAgree on the technician, approved device, purpose, and attended or unattended permission.
Session → Action
SCOPE TO MAINTAINKeep actions visible or documented as agreed; recheck permission when scope or participants change.
Confirmation → Closure
CLOSURE TO VERIFYConfirm the outcome, end the active connection, and state any continuing managed access.
SessionBoundary Playbook is an independent educational publication about remote-support workflow boundaries. It does not initiate Splashtop sessions, issue access codes, request user credentials, manage devices, or provide official Splashtop technical support.
Official product context: Splashtop Inc. — Attended Access and Remote Support. Category: IT workflow education · Remote-support sessions · Format: Boundary Scenarios · Brand role: Support-session example.
Ask About a Session Boundary
Send a question or comment about the educational playbook.