mirror of
https://github.com/amidaware/tacticalrmm.git
synced 2026-04-27 07:25:56 +03:00
[GH-ISSUE #2052] Possibility to block access to a client/site #3217
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#3217
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 @ShiryokuHorus on GitHub (Oct 31, 2024).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/2052
Hi,
First of all thank you very much for existing. We are starting to use TacticalRMM in my company and it is really great !
I have an "issue" though, i'd like to restrict access to a site to a role and i don't find an easy way of doing so, maybe i'm doing something wrong. I'll explain myself:
I have to roles defined (Admin, Tech)
By default those two roles have access to all client (No client selected, implicit access to every client)
But i have one specific client that i want to restrict access to one user only (Or may be one role).
The way roles works it seems that you can only allow certain site, and not block. Meaning that i could set my roles to allow every client expect the client i want to block access to, but it may be hard to manage when adding new client not to forget to add the client to the roles.
Is there a way to block access to a specific client instead of allowing certain client by choosing them ?
Sorry if its not clear.. !
@dinger1986 commented on GitHub (Oct 31, 2024):
Yeah unfortunately it is setup to allow not block, maybe theres a way the devs can allow that to be inverted, you could open an issue as a feature request?
@ShiryokuHorus commented on GitHub (Oct 31, 2024):
Yes for sure, thanks for reply