DesktopWhat you need to know
For a straightforward remote session you need two things: a Windows computer running DesktopBee as the host, and another computer or browser as the viewer. Someone at the host must be available to provide a current access code and approve the request. Here is the process without complicated network configuration.
Step 1 — Prepare the Windows computer
Install DesktopBee from its verified release page when available and launch it on the Windows 10 or 11 host. Confirm the app is connected to DesktopBee Cloud. If the release page says the installer is pending, the public Setup EXE has not yet been published.
Step 2 — Ask for the ID and code
The host should find the permanent nine-digit computer ID and a temporary access code inside DesktopBee. Share these over a channel you trust and only with the intended viewer. Do not include them in screenshots posted publicly.
Step 3 — Open the viewer
On another Windows PC, open DesktopBee; alternatively, open the web viewer in a compatible modern browser. Enter the computer ID and current code, then request access. Do not retry repeatedly if the host declines.
Step 4 — Approve permission at the host
The Windows host decides whether to reject, allow View Only, or allow Full Control. Start with View Only whenever practical. The host can change the permission or disconnect during the session.
Step 5 — End and check
When the task is finished, terminate the session and confirm the remote control has stopped. Never leave credentials visible or assume a trusted device can connect silently. In this preview, each new session still requires host consent.
Frequently asked questions
Is port forwarding necessary?
No inbound Windows router port is generally needed for DesktopBee Cloud relay connections.
Do I need admin rights?
Your Windows environment may need installation permission for the desktop application; using a browser as the viewer typically does not.
Can I leave a PC unattended?
No. Host presence and approval are required today.