TheLanc3/rustdesk
1
0
Fork 0
mirror of https://github.com/rustdesk/rustdesk.git synced 2026-04-19 13:41:29 +03:00
Code Issues Packages Projects Releases Wiki Activity

Updated FAQ (markdown)

RustDesk
2025-11-11 18:14:07 +08:00
parent 3de7d7579b
commit b18bd0fba5
1 changed files with 12 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
FAQ.md

@@ -916,6 +916,11 @@ All devices connected to the server are counted, we can not know the device will
![image](https://github.com/user-attachments/assets/0289d1a6-a66a-420e-908f-195fb2a98f53)
> Controlling vs. Controlled Devices: If a machine is connected to our self-hosted server via the custom client, but its sole purpose is to act as a Controlling Device (the initiator, used by a reseller/technician) to access other endpoints, is that controlling machine counted as a "Managed Device" simply because it is connected to the server? Or does "Managed Device" only count the endpoints that are the targets of a remote session (i.e., the client machines being managed)?
You can create outgoing only custom client, it will not be counted.
## Login users
Login users, the number of accounts from your team can log into the web console and the RustDesk client. The team administrator can assign different ACLs to each user. These users are displayed on the `Users` page of the `web console`. [`Access control`](https://rustdesk.com/docs/en/self-host/rustdesk-server-pro/permissions/) and shared address books are designed on individual users and user groups. One user can log in to multiple devices.
@@ -925,6 +930,13 @@ You need to log in to the RustDesk client first to access address books and perm
![image](https://github.com/user-attachments/assets/189e6c73-eaef-40e0-bba8-fed3db1f758b)
> If a single technician (a unique human/account) installs and uses the client on multiple machines (e.g., their work PC and a laptop) to initiate remote sessions, does this count as one "Login User" or multiple "Login Users"? This distinction is crucial as this is the metric tied to the $1 per additional user cost.
A single technician is always counted as one Login User, regardless of how many devices they install the client on or use to start remote sessions.You only need to create one user account for that technician in the system. Multiple technicians can even share the same login credentials if desired—doing so still counts as one Login User in the license.The "User" concept exists primarily for Access Control Lists (ACL)—to define which technicians may access which remote devices. If you do not require granular access control (i.e., all technicians can access all machines), you do not need multiple user accounts at all. A single admin user is sufficient.
## Concurrent connections
It's the same as the so called channels with teamviewer. Here is how TeamViewer defines concurrent connections: it is the number of individual users who can make outgoing connections simultaneously. You can also call it channel, in the same channel, unlimited sessions are allowed.