Understand who can connect and what Deskbat records
Learn how Deskbat connections are approved, how unattended access works, what connection diagnostics contain, and how to report misuse.
Remote support gives another person access to a computer. Use Deskbat with people you know and whose help you requested. This page explains the access choices visible in the product.
Two ways to authorize access
For attended support, the host can allow view-only access, allow control or decline. For unattended access, the owner configures a separate computer password. A signed-in person outside the workspace can connect by ID with local approval or that password. Knowing the ID alone is not enough.
Account password and computer password
Your account password signs you in to Deskbat. The unattended-access password authorizes access to a particular computer. Windows sign-in is separate again: connecting to a locked PC does not remove its normal sign-in requirement. Never send these passwords to support.
Ending and pausing access
End the current session when assistance is complete. On the host, Pause sharing prevents incoming access. The Windows tray includes Stop & pause sharing. Locking the screen is not the same as revoking unattended access.
Connection records and recordings
Connection history and technical diagnostics help support identify when and why a connection failed. Screen contents and mouse or keyboard input are not stored as server diagnostics. If a session is recorded using Deskbat, the recording stays on the recording computer. Review the privacy policy for account and connection data details.
Report a concern
- For a connection problem: [email protected]. Include the time, time zone and diagnostic reference.
- For scams or misuse: [email protected]. Do not approve an unexpected request.
- For privacy questions: [email protected].
- Security researchers: see security.txt.