[GH-ISSUE #2430] Add ability to exempt inheritance on single items for single agents #3432

Open
opened 2026-03-14 07:19:28 +03:00 by kerem · 0 comments
Owner

Originally created by @sbsroc on GitHub (Mar 8, 2026).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/2430

Is your feature request related to a problem? Please describe.
It would be handy to exempt an agent from inheriting a single check or task. Some of my automation policies are a long list and having to duplicate it and remove a single check or task then having to maintain all of the variations would get tedious.

Describe the solution you'd like
It seems reasonable to go to an client, right-click on the check or task and choose "exempt" or "block inheritance" and it show in the list with a strikethrough and be disabled from being deployed to the agent.

Describe alternatives you've considered
Making multiple duplicate policies with alterations and having to add/remove and modify the checks and tasks equally on each policy sounds tedious.

Additional context
There are some computers that have low memory, but it's soldered on board and cannot be upgraded. I don't need to be notified constantly about the memory being over 80%, for example. The customer accepts that this computer is low powered and chooses not to upgrade it.
There are other examples of computers that need all checks and tasks except one, and this would be a huge help to my workflow.

Originally created by @sbsroc on GitHub (Mar 8, 2026). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/2430 **Is your feature request related to a problem? Please describe.** It would be handy to exempt an agent from inheriting a single check or task. Some of my automation policies are a long list and having to duplicate it and remove a single check or task then having to maintain all of the variations would get tedious. **Describe the solution you'd like** It seems reasonable to go to an client, right-click on the check or task and choose "exempt" or "block inheritance" and it show in the list with a strikethrough and be disabled from being deployed to the agent. **Describe alternatives you've considered** Making multiple duplicate policies with alterations and having to add/remove and modify the checks and tasks equally on each policy sounds tedious. **Additional context** There are some computers that have low memory, but it's soldered on board and cannot be upgraded. I don't need to be notified constantly about the memory being over 80%, for example. The customer accepts that this computer is low powered and chooses not to upgrade it. There are other examples of computers that need all checks and tasks except one, and this would be a huge help to my workflow.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/tacticalrmm#3432
No description provided.