[GH-ISSUE #2132] [Feature Request] - Manage MeshCentral Prompt for Consent Policies from TacticalRMM #3270

New issue

Open

opened 2026-03-14 07:00:58 +03:00 by kerem · 2 comments

kerem commented

2026-03-14 07:00:58 +03:00

Owner

Originally created by @joeldeteves on GitHub (Feb 1, 2025).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/2132

We need to be able to manage the MeshCentral "Prompt for consent" option on a per-agent level. This is an important feature for user trust as some people don't want techs to connect without accepting the consent request.

Describe the solution you'd like

Fine grained control: per Group, per Agent, and per Endpoint (all of these are supported in MeshCentral). More importantly, we need to be able to split by Servers and Workstations which is something we can't do in Mesh currently because everything is lumped to a single TRMM group. TLDR; we want unattended access to Servers, but prompt for consent on workstations.
Likewise, we do not want consent to be prompted for background connections and the File manager connections. These are also options available in Mesh.
We should also be able to toggle off at the endpoint level for specific workstations e.g. for test workstations and tech jump stations

TLDR: I'd like the MeshCentral "Prompt for consent" option to be togglable in TacticalRMM and it should behave the exact same way as Automation Policies in terms of being able to block inheritance / override at any level of the app

TLDR2: I'd like this to only apply for screen control, not for background tasks like command prompt / file manager

Describe alternatives you've considered
I've looked into doing it from Mesh - our only option there is to select all endpoints and apply them that way, because everything is lumped into a single group. It's not ideal also in the sense that we have to do this manually for newly added endpoints.

Additional context
See discussion in #Sponsors Discord channel

Originally created by @joeldeteves on GitHub (Feb 1, 2025). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/2132 We need to be able to manage the MeshCentral "Prompt for consent" option on a per-agent level. This is an important feature for user trust as some people don't want techs to connect without accepting the consent request. **Describe the solution you'd like** - Fine grained control: per Group, per Agent, and per Endpoint (all of these are supported in MeshCentral). More importantly, we need to be able to split by Servers and Workstations which is something we *can't* do in Mesh currently because everything is lumped to a single TRMM group. TLDR; we want *unattended* access to Servers, but *prompt for consent* on workstations. - Likewise, we *do not* want consent to be prompted for background connections and the File manager connections. These are also options available in Mesh. - We should also be able to toggle off at the endpoint level for specific workstations e.g. for test workstations and tech jump stations **TLDR:** I'd like the MeshCentral "Prompt for consent" option to be togglable in TacticalRMM and it should behave the exact same way as Automation Policies in terms of being able to block inheritance / override at any level of the app **TLDR2:** I'd like this to only apply for screen control, not for background tasks like command prompt / file manager **Describe alternatives you've considered** I've looked into doing it from Mesh - our only option there is to select all endpoints and apply them that way, because everything is lumped into a single group. It's not ideal also in the sense that we have to do this manually for newly added endpoints. **Additional context** See discussion in `#Sponsors` Discord channel

kerem commented

2026-03-14 07:01:04 +03:00

Author

Owner

@Slouserg commented on GitHub (Feb 7, 2025):

Would be nice.

For now you can set it on the meshcentral side. Hope this helps

@Slouserg commented on GitHub (Feb 7, 2025): Would be nice. For now you can set it on the meshcentral side. Hope this helps

kerem commented

2026-03-14 07:01:09 +03:00

Author

Owner

@joecool1029 commented on GitHub (Dec 9, 2025):

I'm just going to put this in here since it's related, but if the sync permissions with TRMM option is enabled, the consent policy cannot be changed from the Meshcentral interface. You need to turn it off, do the changes per-agent, and then turn it back on again.

@joecool1029 commented on GitHub (Dec 9, 2025): I'm just going to put this in here since it's related, but if the sync permissions with TRMM option is enabled, the consent policy cannot be changed from the Meshcentral interface. You need to turn it off, do the changes per-agent, and then turn it back on again.