Feature Request: Allow Strategies to be Scoped to User Groups

[kRaiN21]

I would like to propose allowing Strategies to be scoped to specific User Groups.

Currently, a strategy applies to all users connecting to a device. This makes it impossible to assign different in-session permissions to different user roles connecting to the same group of devices.

Use Case:

I need Admins and Supporters to access the same set of devices but with different rights:

"Admins" User Group: Should connect with a Strategy that enables remote configuration changes (enable-remote-config-modification: Y).
"Supporters" User Group: Should connect with a Strategy that disables this feature (enable-remote-config-modification: N).
Proposed Solution:

Allow an optional "User Group" scope within a Strategy's settings. If the connecting user is a member of a targeted group, apply that specific strategy. Otherwise, apply a default strategy.

This would enable true Role-Based Access Control (RBAC) for session permissions and eliminate the need to maintain duplicate device groups for different access levels, which is not a scalable solution. Thank you for considering this enhancement.

[rustdesk]

@21pages

[rustdesk]

Defined by user group does make sense too much. In my opinion, it needs to be session based. It needs to be associated with the cross-group rule (no need to expose all security options).

We need a good reference. Please review implementations in the other vendors first.

[21pages]

Should user-specific session control permissions override the RustDesk client settings, or should they be limited by (i.e., take effect only within) the permission scope defined by the RustDesk client settings?

For example:

If the RustDesk client setting has keyboard enabled, and user1 has keyboard disabled, it makes sense that user1 does not have keyboard access.

But if the RustDesk client setting has keyboard disabled, and user1 has keyboard enabled, does user1 have keyboard access in this case?