mirror of
https://github.com/amidaware/tacticalrmm.git
synced 2026-04-26 15:05:57 +03:00
[GH-ISSUE #559] Feature Request: Set Meshcentral Consent/Notifications per automation policy #2301
Labels
No labels
In Process
bug
bug
dev-triage
documentation
duplicate
enhancement
fixed
good first issue
help wanted
integration
invalid
pull-request
question
requires agent update
security
ui tweak
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/tacticalrmm#2301
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Brodur on GitHub (Jun 7, 2021).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/559
I'd love to see the automation policy settings also have the ability to include the notification and consent settings in MeshCentral.
Would also be nice to see individual agent control too of course for overrides and exceptions.
Currently I set these in Mesh manually - would be nice to have them in the dashboard for sensitive clients/devices.
@dinger1986 commented on GitHub (Jun 8, 2021):
The issue with mesh is currently can't be controlled externally.
I'll close this but if you find info on changing these settings using the api or something we can always reopen this.
Otherwise you could open a feature request with mesh and then if they implement that control reopen this
@Brodur commented on GitHub (Jun 9, 2021):
Spawned MeshCentral issue: https://github.com/Ylianst/MeshCentral/issues/2749
@Brodur commented on GitHub (Jun 11, 2021):
As per https://github.com/Ylianst/MeshCentral/issues/2749#issuecomment-859812838
There should be an API available soon!