[GH-ISSUE #2232] Remote Access: Require client confirmation before session starts (optional setting) #3333

New issue

Closed

opened 2026-03-14 07:08:32 +03:00 by kerem · 3 comments

kerem commented

2026-03-14 07:08:32 +03:00

Owner

Originally created by @Ginetas on GitHub (May 12, 2025).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/2232

Feature Description

Please add an option to TacticalRMM that requires the end-user to confirm or approve a remote session request before the technician can connect.

This should work similar to how tools like AnyDesk, TeamViewer, or MeshCentral (with consent option) operate – where the user sees a popup like:

"A technician wants to access your computer. Do you accept?"

Why this is important

This is a critical feature for privacy and compliance in some regions (GDPR, etc.)
Some clients require transparency before a technician connects
It builds trust, especially for support in sensitive environments (e.g. finance, healthcare)

Suggested Implementation Ideas

A per-agent or global policy to require confirmation
A PowerShell-based consent popup
Integration with existing RMM UI (RustDesk, RDP, or MeshCentral session)

Alternatives

Currently the only workaround is to use MeshCentral externally, which supports this but is not tightly integrated with TacticalRMM features and UI.

Thank you!

This would be a game-changing addition to TacticalRMM for those who need stricter control over access.

Originally created by @Ginetas on GitHub (May 12, 2025). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/2232 ### Feature Description Please add an option to TacticalRMM that requires the end-user to confirm or approve a remote session request before the technician can connect. This should work similar to how tools like AnyDesk, TeamViewer, or MeshCentral (with consent option) operate – where the user sees a popup like: > "A technician wants to access your computer. Do you accept?" ### Why this is important - This is a critical feature for privacy and compliance in some regions (GDPR, etc.) - Some clients require transparency before a technician connects - It builds trust, especially for support in sensitive environments (e.g. finance, healthcare) ### Suggested Implementation Ideas - A per-agent or global policy to require confirmation - A PowerShell-based consent popup - Integration with existing RMM UI (RustDesk, RDP, or MeshCentral session) ### Alternatives Currently the only workaround is to use MeshCentral externally, which supports this but is not tightly integrated with TacticalRMM features and UI. ### Thank you! This would be a game-changing addition to TacticalRMM for those who need stricter control over access.

kerem closed this issue

2026-03-14 07:08:37 +03:00

kerem commented

2026-03-14 07:08:43 +03:00

Author

Owner

@P6g9YHK6 commented on GitHub (May 12, 2025):

right click the take control button.
or go and change the settings of the mesh groups

@P6g9YHK6 commented on GitHub (May 12, 2025): right click the take control button. or go and change the settings of the mesh groups

kerem commented

2026-03-14 07:08:48 +03:00

Author

Owner

@wh1te909 commented on GitHub (May 13, 2025):

you can enable this globally or per device group here, and it will still work with the trmm integration: https://docs.tacticalrmm.com/tipsntricks/#enable-remote-control-options

we are planning to add an option in tacticalrmm so that you don't have to login to mesh to set it, but atm it's just a one time setup you have to do, see docs above

@wh1te909 commented on GitHub (May 13, 2025): you can enable this globally or per device group here, and it will still work with the trmm integration: https://docs.tacticalrmm.com/tipsntricks/#enable-remote-control-options we are planning to add an option in tacticalrmm so that you don't have to login to mesh to set it, but atm it's just a one time setup you have to do, see docs above

kerem commented

2026-03-14 07:08:53 +03:00

Author

Owner

@bcarnazzi commented on GitHub (Aug 8, 2025):

I've created a mesh group but how to make it default or move device to it ?

@bcarnazzi commented on GitHub (Aug 8, 2025): I've created a mesh group but how to make it default or move device to it ?