-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Access control isn't allowing device subsets #282
Comments
I guess a solution would be to have an address book for each user group, with set permanent passwords, although they are a bit painful to configure because you need to specify the permanent password for each device each time you create an address book. |
You can create cashier group, server group, office group, tech group, accountant group, admin group, Create cross-group access rules
|
I don't understand your answer, as groups are not assignable to device but to users. Another solution in mind? |
No need to to login on each device, you can just assign on web console. We do not have the other solution yet. |
And we added a new way for bulk assignment. https://github.com/rustdesk/rustdesk-server-pro/releases/tag/1.3.11 346325912-18548235-74d1-41b2-a5a1-3d379eba8965.mp4 |
Mh, still, your solution requires to create an user for each asset type, which isn't logical, and requires more users than needed (licencing...) Please make it so groups can be assigned to devices. |
Hi,
I have an issue I currently can't solve with the possibilities access control gives me :
There are several users configured, which should have access rights to different type of device :
If I assign a strategy to cashier desks so that accountants can access it, I can't make a broader strategy for tech support to include both cashier desks and servers for example
Groups can only be assigned to users
Devices can only be assigned to one user
I cannot wrap my head around how I could solve this with the current way access control works.
Please enlighten me or let's see how this can be changed to be able to have such configurations.
Thanks
The text was updated successfully, but these errors were encountered: