mirror of
https://github.com/amidaware/tacticalrmm.git
synced 2026-04-26 15:05:57 +03:00
[GH-ISSUE #897] Additional Users to Tie Into Mesh Central #2500
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#2500
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 @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.
@dinger1986 commented on GitHub (Dec 23, 2021):
please add comments to #182
closing as duplicate