Skip to content
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

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

Open
joeldeteves opened this issue Feb 1, 2025 · 1 comment

Comments

@joeldeteves
Copy link
Contributor

joeldeteves commented Feb 1, 2025

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

@Slouserg
Copy link

Slouserg commented Feb 7, 2025

Would be nice.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants