Advanced agent settings and organization overrides

Advanced settings allow administrators to configure agent‑level behavior limits and manage organization‑specific overrides in Kaseya MDR. These settings control how the agent operates on endpoints—such as resource usage limits and logging verbosity—not how detections, investigations, or responses work. They are intended for governance, performance tuning, and environment‑specific adjustments.

Advanced settings allow administrators to configure agent‑level behavior limits and manage organization‑specific overrides in Kaseya MDR. These settings control how the agent operates on endpoints—such as resource usage limits and logging verbosity—not how detections, investigations, or responses work. They are intended for governance, performance tuning, and environment‑specific adjustments.

Advanced settings are part of the Settings experience and apply at either:

  • The global default level

  • The organization override level

Deploying agents explains how the agent is installed. Advanced agent settings explain how the agent behaves once it is deployed.

What these settings are

Advanced settings allow you to:

  • Control agent resource usage (CPU and memory)

  • Adjust agent logging verbosity

  • Configure agent error‑reporting behavior

  • Apply organization‑specific overrides when required

These settings help ensure the agent operates safely and predictably across different environments.

Advanced settings do not:

  • Change detection logic

  • Suppress alerts or investigations

  • Affect Power Filters or allowlisting

  • Override SOC‑managed detection or response decisions

If you are looking to manage alert noise or visibility, use Power Filters or Application configurations instead.

Accessing Advanced settings

Advanced agent settings can be configured at both the global level and the organization level.

Organization‑level settings

Organization‑level Advanced settings are accessed from the Settings tab within a specific organization. This view allows administrators to apply organization‑specific overrides to agent behavior without modifying global defaults.

To access organization‑level Advanced settings:

  1. From the side navigation menu, click Organizations.

  2. Click the Edit Organization icon (pencil icon) for the organization you want to modify.

  3. Open the Settings tab.

  4. Locate the Advanced settings section.

Changes made from this view apply only to the selected organization when Override global settings is enabled. If no override exists, the organization continues to inherit the global default settings.

Global Settings

Advanced agent settings are also managed at the global level from the main Settings area.

To access Advanced settings:

  1. From the side navigation menu, click Settings.

  2. Select Advanced Settings.

The page is organized into two main areas:

  • Agent settings

  • Organization overrides

NOTE  These settings apply only after agents are deployed. For installation methods and deployment confirmation, see Deploying agents.

Agent settings

Agent settings define baseline operational limits for the Kaseya MDR agent. These settings apply by default unless an organization‑level override is configured.

Available agent settings

The following agent settings are available:

  • Maximum CPU usage: Defines the maximum percentage of CPU the agent is allowed to consume

  • Maximum memory usage: Defines the maximum amount of memory the agent may use

  • Maximum sustained memory usage (seconds): Specifies how long elevated memory usage is allowed before limits are enforced

  • Verbosity: Controls the level of detail included in agent logs.

    Available levels include the following:

    • Trace

    • Debug

    • Info

    • Warning

    • Error

    • Fatal

    Verbosity controls how much detail the agent includes in its logs.

    • Lower verbosity levels reduce log volume and overhead.

    • Higher verbosity levels increase detail and are typically used for investigation or troubleshooting.

    Changes to verbosity should be made cautiously and reviewed after use.

  • Automatically report agent errors: When enabled, agent errors are automatically reported.

These settings are intended to balance visibility, diagnostics, and endpoint performance.

Organization overrides

Organization overrides allow administrators to apply Advanced agent settings to a specific organization without modifying global defaults. Overrides explicitly define cases where an organization should not inherit global agent behavior.

Creating an organization override from Global Advanced settings

From the global Advanced settings page, administrators can create organization‑specific overrides without navigating into an organization.

To create an organization override:

  1. Select + New override.

  2. Choose the organization to which the override will apply.

  3. Configure the required agent settings.

  4. Select Save to create the override.

When an override exists:

  • The organization no longer inherits the global defaults for those settings.

  • Agent behavior for that organization is determined by the override.

Overrides are typically used for environment‑specific requirements or temporary adjustments.

Managing overrides from an organization

When configuring Advanced settings from an organization’s Settings tab, the override applies implicitly to that organization.

To manage an override from this view:

  1. From the side navigation menu, click Organizations.

  2. Click the Edit Organization icon (pencil icon) for the organization you want to modify.

  3. Open the Settings tab.

  4. Enable Override global settings.

  5. Adjust the required agent settings.

  6. Select Save to apply changes.

Disabling Override global settings removes the organization‑level override and restores inheritance from the global defaults.

Saving and resetting changes

  • Changes take effect when you select Save.

  • If you navigate away without saving, changes are not applied.

  • You can use Reset to Default Settings to revert agent settings back to the global defaults.

Changes should be made deliberately and reviewed periodically.

How this fits with other settings

Advanced settings work alongside other configuration areas in Kaseya MDR:

  • Application configurations define baseline detection and integration behavior.

  • Power Filters manage what activity is surfaced for investigation.

  • Advanced agent settings control how the agent operates on endpoints.

  • The SOC manages detection logic and response decisions.

Understanding these boundaries helps avoid unintended side effects and keeps configuration changes scoped correctly.

Best practices

  • Use default settings unless there is a clear operational reason to change them

  • Make incremental changes and observe impact before adjusting further

  • Document why organization overrides are created

  • Review overrides periodically to ensure they are still required

  • Coordinate changes with Support if troubleshooting agent performance issues

Related articles

After reviewing or adjusting Advanced settings, you may want to:

  • Validate agent behavior across affected endpoints

  • Review whether organization overrides are still necessary

  • Ensure settings align with your operational and performance requirements

For related information, see:

  • Deploying agents: Use this when readers need to understand how agents are installed and associated with organizations, before any advanced settings or overrides apply. This article explains deployment mechanics and explicitly separates deployment from agent behavior configuration

  • Global defaults and organization overrides: Explains the inheritance model used across SIEM, including why global defaults apply, when organization overrides take effect, and how scope affects behavior

  • Application Configurations: Use this when readers need to tune detection and integration behavior rather than agent performance. This article helps prevent misusing agent settings to solve detection or noise issues.