rustdesk / rustdesk/rustdesk-server-pro

Feature request : Address Book and Access Method

Open
#270 2 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Shell
Stars
317
Forks
119
PR merge metrics
No merged PRs in 30d

Description

Hello,

You made a great job here and wanted to use this solution in our enterprise environment. We are missing a few features to switch over to this software and the integration of the basic business plan is what we are looking for.

The address book

The address book is pretty cool and functionnal, but the end user has to create his own address book in order to save it back on the server. A cool feature would be to show directly all the PC's he is allowed to control from the same server. Let me explain a bit :

For exemple my company has 300 Pc's and 5 users allowed for remote control. We made some groups for those PC's (Accounting, production, commercial, etc.) and allowed one user to it.

  • Can thoses PC's show up in his address book automatically ?
Access grant

Another cool feature would be the access method. Currently, i managed to access one remote PC with a custom password. This will end up with a hudge amount of passwords stored in a Keepass file and will finally always be de-synchronized between the team.

  • Could this access method be like "Access in granted with a local admin account" ?
    For exemple, LogMeIn is using this feature and this is pretty confortable.

I hope this features will end up in the roadmap before our next "remote control software" renewal so we can switchover soon !

Thank you and have a nice day!

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are identified. Start by locating the existing server-side address-book and access-grant implementations, then inspect how groups, permitted PCs, and credentials are represented. Confirm the scope and acceptance criteria with maintainers before considering implementation.

Written by the indexing model from the issue text.

Assessment

Domain
authorization, backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.