[GH-ISSUE #897] Additional Users to Tie Into Mesh Central #558

Closed
opened 2026-03-02 02:17:14 +03:00 by kerem · 1 comment
Owner

Originally created by @jacksonsystems on GitHub (Dec 23, 2021).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/897

At present TRMM uses one accoun in Global Settings > Mesh Central.

It would be handy if another account could be set up per TRMM User. At the moment only one mesh account can be used for all TRMM users.
For auditing sake, this makes it messy to find out who has accessed what. A seperate mesh login per user would be easier to audit and check logs.

For example, I log into TRMM as tech1, my Mesh Settings in Global Settings are Username and Password for tech1. My engineer may log in as tech2, this would require a user account in mesh to match tech2 added to the Global Settings > Mesh Central for that user.

Originally created by @jacksonsystems on GitHub (Dec 23, 2021). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/897 At present TRMM uses one accoun in Global Settings > Mesh Central. It would be handy if another account could be set up per TRMM User. At the moment only one mesh account can be used for all TRMM users. For auditing sake, this makes it messy to find out who has accessed what. A seperate mesh login per user would be easier to audit and check logs. For example, I log into TRMM as tech1, my Mesh Settings in Global Settings are Username and Password for tech1. My engineer may log in as tech2, this would require a user account in mesh to match tech2 added to the Global Settings > Mesh Central for that user.
kerem closed this issue 2026-03-02 02:17:14 +03:00
Author
Owner

@dinger1986 commented on GitHub (Dec 23, 2021):

please add comments to #182

closing as duplicate

<!-- gh-comment-id:1000504163 --> @dinger1986 commented on GitHub (Dec 23, 2021): please add comments to #182 closing as duplicate
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#558
No description provided.