Clients they do not belong to. #2722

New issue

Open

opened 2026-03-14 05:15:47 +03:00 by kerem · 1 comment

kerem commented

2026-03-14 05:15:47 +03:00

Owner

Originally created by @JSuenram on GitHub (Aug 23, 2022).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1255

I would expect that Automation-Policies are limited the same way as Policy-Overview is?
You should not be able to see Policies created from Users who belong only to specific Clients or Sites.
Also it should not be possible to assign them.

Originally created by @JSuenram on GitHub (Aug 23, 2022). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1255 I would expect that Automation-Policies are limited the same way as Policy-Overview is? You should not be able to see Policies created from Users who belong only to specific Clients or Sites. Also it should not be possible to assign them. ![image](https://user-images.githubusercontent.com/68963439/186144696-776d16fb-3c05-4123-ab6b-212c6d1c5b41.png)

kerem added the

enhancement

label

2026-03-14 05:15:47 +03:00

kerem commented

2026-03-14 05:15:58 +03:00

Author

Owner

@sadnub commented on GitHub (Aug 23, 2022):

Currently, policies don't have any owners assigned since they can be applied anywhere. The only permissions are view/edit Policies. This would take quite a bit of rework to implement, but may be possible in the future

@sadnub commented on GitHub (Aug 23, 2022): Currently, policies don't have any owners assigned since they can be applied anywhere. The only permissions are view/edit Policies. This would take quite a bit of rework to implement, but may be possible in the future