Description
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