mirror of
https://github.com/amidaware/tacticalrmm.git
synced 2026-04-26 06:55:52 +03:00
[GH-ISSUE #1826] Mesh User Consent Synced With TacticalRMM #3079
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#3079
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 @bc24fl on GitHub (Apr 2, 2024).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1826
Originally assigned to: @wh1te909 on GitHub.
As is, MESH can be configured so that user consent restrictions can be applied to Device Groups, By User, and By Agent. I would like to be able to assign separate users different consent restrictions but to the dynamic user account created by TRMM. The only option currently is to make the change on the Device Group level since TRMM doesn't touch those settings. So in short, exposing user level perms to TRMM.
@davidebonavita commented on GitHub (Apr 9, 2024):
I second this, as SuperUser I can connect to devices even when there's no user currently logged in, but in order to do this I need to change the settings in the Device Group.
There are some other limited users in Tactical that must have user consent enabled all the time.
@P6g9YHK6 commented on GitHub (May 22, 2024):
i would add that the sync needs to be done on a policy level to allow the use of cascading rights
and that mesh need to have the site/client folder structure duplicated to allow more visibility and ease of management