Overview

Policies let you transform alerts that match your criteria: change fields (severity, tags, attributes, …), optionally run a custom tool, on an event trigger or a fixed schedule. They run in priority order (lower number first), similar to notification rules, but they modify alerts instead of sending messages.

Step	What you configure	Documentation
1	General — name, priority, status, trigger, active time window	Creating a policy
2	Conditions — which alerts the policy applies to	Conditions
3	Modifiers — field changes and optional tool execution	Modifiers and tools

Where to find it in the UI

In the sidebar under Management:

• Policies → /policies

Header actions: Refresh and Create policy. The list supports name search and Toggle TQL filter mode — see TQL search and filters.

Permissions

Creating, editing, running, enabling/disabling, and deleting policies require the appropriate permissions in your organization. If Create policy or row actions are missing, contact your administrator.

How policies fit in ToBeAlert

Typical example — downgrade noisy staging alerts:

1. Trigger: On alert creation and any change type.
2. Conditions: environment Equals → Staging AND severity Equals → critical.
3. Modifiers: severity / set → major.
4. Time window: All Day, status active, priority 10.

When a matching alert is created or updated, its severity is adjusted before operators see it in the dashboard.

Policies vs notification rules

	Policies	Notification rules
Purpose	Transform alert data	Send email/Telegram notifications
Route	/policies	/notifications/rules
Condition builder	Same visual builder	Same visual builder
Third tab	Modifiers (+ optional tool)	Actions (method, recipients)
Trigger location	General tab	Conditions tab
Manual test	Run → execution results dialog	Force (disabled in current UI)
Built-in entries	None — all user-created	Some built-in rules (not deletable)

Do not confuse Management → Policies with Service Topology → Weight Policies — those are separate weight-ranking rules without modifiers or custom tools.

License limits

Resource	When limited
Policies	Header shows used/max; Create policy is disabled with Max items reached
Custom tools (policies with Execute custom tool)	Active policies with a tool assigned also count toward the tools limit; tool selector disabled at limit

Related modules

Module	Relationship
Notification rules	Same condition builder; complementary (notify vs transform)
Maintenance windows	Scheduled maintenance — pair policy tuning with window scope
Tools overview	Scripts runnable from the Modifiers tab
Alerts dashboard	See results of policy transformations on alerts

Best practices

1. Lower priority for more specific policies; higher numbers for broad catch-all rules.
2. Test with Run after creating or changing conditions/modifiers.
3. Keep conditions narrow — avoid unintended mass updates to production alerts.
4. Pair with notifications — policy adjusts data; notification rule informs people.
5. Review scheduled policies — ensure time window and cron-like triggers match maintenance expectations.
6. Document each policy in Description — future you (and auditors) will need the intent.