mirror of
https://github.com/amidaware/tacticalrmm.git
synced 2026-04-26 15:05:57 +03:00
[GH-ISSUE #629] Popup on remote control - RGPD (GDPR). #2347
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#2347
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 @Nyphew on GitHub (Jul 10, 2021).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/629
Hi there,
Is your feature request related to a problem? Please describe.
Not a technical problem, but with law on RGPD (GDPR) in europe this could be a great improvement.
Describe the solution you'd like
When taking control on remote device, the default action is to connect without notifying. Of course it's not a problem when we connect to a server, but when we want to go on a workstation we really need to notify the user. Would be nice to have an option to choose/set the default behaviour to "notify and ask permission" and use right-click to bypass.
Describe alternatives you've considered
Make a default action which is different for servers and workstations. If we are in the server tab, no need to notify. If we are in the workstation tab, we need to notify.
Additional context
Nothing to add.
Thanks a lot for your work.
Nyphew.
@dinger1986 commented on GitHub (Jul 10, 2021):
This is a mesh request not for tactical. You can search for meshcentral user notifications on google but essentially if you log into mesh central you can enable notifications in the device group.
@Nyphew commented on GitHub (Jul 10, 2021):
Hi dinger1986,
Thanks for your reply, I could create a dedicated group to workstations and change the default behaviour as requested in my first post. Is there a way to manage those meshgroups from tacticalrmm ? Maybe this can be a feature improvment ?
Have a good day.
@dinger1986 commented on GitHub (Jul 10, 2021):
You can change the default behaviour for the tacticalrmm group.
You can't move anything as it won't work in tactical.
Mesh and tactical are 2 separate systems I would doubt this will be implemented.
@Nyphew commented on GitHub (Jul 10, 2021):
Well it's working as intended whereas I have renamed the default "tacticalrmm" group to "servers" and create a new "workstations" group (and moved computers in). Both with different default behavior on "take control" command. I even rebooted the server.
@dinger1986 commented on GitHub (Jul 10, 2021):
Ok.
Fair enough, have you tried adding new machines?
@Nyphew commented on GitHub (Jul 10, 2021):
Yes, I even tried to move from one group to another and the default behaviour is changing and working as expected.
Really thanks for your support because I would have had to stop using this amazing piece of software if I could not achieve this.
++
@dinger1986 commented on GitHub (Jul 10, 2021):
Perfect!
No problems at all!