mirror of
https://github.com/amidaware/tacticalrmm.git
synced 2026-04-26 15:05:57 +03:00
[GH-ISSUE #1838] Mesh Central - Consent #1141
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#1141
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 @Jurgens92 on GitHub (Apr 16, 2024).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1838
Hi,
with the new Consent feature, I would like to request a feature where you can enable or disable this feature based on Workstations/Servers
in my case, I would like to have users gain access to servers without consent feature, however connecting to workstations they need to have it enabled
thanks
@Serenfo commented on GitHub (Apr 16, 2024):
Hi,
You can easily do it with two group on meshcentral one "Workstation" with consent option enable and one "Server" with no consent needed. Move device on specific group and you've your policy :)
@Jurgens92 commented on GitHub (Apr 16, 2024):
that makes sense,
i thought it would be possible this way, with just a bit of manual moving.
thanks for the feedback.
but it would make a great feature, where this can be setup within TRMM, and not mesh.
@dinger1986 commented on GitHub (Apr 23, 2024):
duplicate of #1826 please add comments there