[GH-ISSUE #61] [Feature Request] Add Option to Exclude Specific Sites Instead of Selecting All to Include #41

Open
opened 2026-03-02 02:12:54 +03:00 by kerem · 0 comments
Owner

Originally created by @maffmeier on GitHub (May 14, 2025).
Original GitHub issue: https://github.com/amidaware/rmmagent/issues/61

Description

Currently, when configuring permissions or filters based on Sites (e.g., for scripts, alerts, automation, etc.), the Tactical RMM interface requires users to select all Sites to include, which becomes cumbersome when the goal is simply to exclude a few specific Sites.

Feature Request

Introduce an additional option or toggle to allow excluding specific Sites, rather than selecting all others to include.

Use Case

For organizations managing a large number of Sites, it is much more efficient to exclude a handful of Sites (e.g., test environments or internal-only clients) than to manually select dozens of others. This would greatly improve usability and reduce configuration errors.

Suggested Implementation

  • Provide a toggle: "Include mode" vs. "Exclude mode"
  • In "Exclude mode", allow selecting one or more Sites that should be excluded from the current action, script, policy, or permission
  • Backend and UI logic should then process this accordingly

Benefits

  • Easier management in large-scale deployments
  • Reduces complexity and room for misconfiguration
  • Improves UX by offering a more intuitive way to manage scope

Thank you for considering this improvement!

Originally created by @maffmeier on GitHub (May 14, 2025). Original GitHub issue: https://github.com/amidaware/rmmagent/issues/61 ### Description Currently, when configuring permissions or filters based on Sites (e.g., for scripts, alerts, automation, etc.), the Tactical RMM interface requires users to select all Sites to include, which becomes cumbersome when the goal is simply to exclude a few specific Sites. ### Feature Request Introduce an additional option or toggle to allow excluding specific Sites, rather than selecting all others to include. ### Use Case For organizations managing a large number of Sites, it is much more efficient to exclude a handful of Sites (e.g., test environments or internal-only clients) than to manually select dozens of others. This would greatly improve usability and reduce configuration errors. ### Suggested Implementation - Provide a toggle: "Include mode" vs. "Exclude mode" - In "Exclude mode", allow selecting one or more Sites that should be excluded from the current action, script, policy, or permission - Backend and UI logic should then process this accordingly ### Benefits - Easier management in large-scale deployments - Reduces complexity and room for misconfiguration - Improves UX by offering a more intuitive way to manage scope Thank you for considering this improvement!
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/rmmagent#41
No description provided.