Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Possibility to block access to a client/site #2052

Closed
ShiryokuHorus opened this issue Oct 31, 2024 · 2 comments
Closed

Possibility to block access to a client/site #2052

ShiryokuHorus opened this issue Oct 31, 2024 · 2 comments

Comments

@ShiryokuHorus
Copy link

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
Copy link
Collaborator

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
Copy link
Author

Yes for sure, thanks for reply

@amidaware amidaware locked and limited conversation to collaborators Oct 31, 2024
@wh1te909 wh1te909 converted this issue into discussion #2054 Oct 31, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants