mirror of
https://github.com/amidaware/tacticalrmm.git
synced 2026-04-26 15:05:57 +03:00
[GH-ISSUE #1880] Customize MeshCentral permission (No terminal access, no files access, etc) when syncing permission #1171
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#1171
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 @catmandx on GitHub (May 30, 2024).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1880
Originally assigned to: @wh1te909 on GitHub.
Is your feature request related to a problem? Please describe.
At our company, we only allow IT dept to:
We DO NOT allow:
If we DON'T use the Sync Perm with MeshCentral then all IT personel use the same master account
--> We can then limit the feature of the master MeshCentral account to disable Remote Terminal and Remote File access
BUT everyone can access anything in MeshCentral
If we use Sync Perm with MeshCentral:
--> Newly created account doesn't have any server feature restrictions
Describe the solution you'd like
Newly created accounts inherit the features restriction of the master account
OR
Specify MeshCentral features restriction in the TRMM Permission Manager