[GH-ISSUE #1826] Mesh User Consent Synced With TacticalRMM #1135

Open
opened 2026-03-02 02:21:26 +03:00 by kerem · 2 comments
Owner

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.

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.
Author
Owner

@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.

<!-- gh-comment-id:2044667021 --> @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.
Author
Owner

@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

<!-- gh-comment-id:2124880532 --> @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
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/tacticalrmm#1135
No description provided.