Custom policies

A policy set encodes the rules a campaign's results are judged against — which categories are prohibited, which keywords matter, what raises an alert.

Listing and visibility

Policies lists your policy sets with a visibility filter: all, private, public, or pending. Private sets are usable only by your organization.

Creating and editing

Open Policies -> New to author a set. The detail page has a read-only view and an edit panel. Attach a policy set to a campaign so its runs are judged by it.

An organization may mark at most one owned policy set as the default. New campaigns that omit policy_set_id pick up that set automatically. Sending JSON null creates the campaign unbound, so it does not generate alerts. Existing campaigns are not rewritten when the default changes. If no default is set, omitted policy_set_id also leaves the campaign unbound.

On the policy set detail page, Set as default / Remove default toggles the flag. A foreign public set in the catalog cannot be made your default.

Moderation workflow

Policy sets intended to be shared can be submitted for approval. They enter a pending state, are reviewed by an administrator, and become available once approved. You can delete a set you own.

Publication is reversible at any point. While a set is still pending, Cancel request withdraws it from the moderation queue; once it is approved and listed in the shared catalog, Unpublish takes it back out. Either way the set returns to private and stays fully usable inside your own organization.

Campaigns in other organizations that were already attached to a set keep their attachment after you unpublish it — going private stops new attachments rather than breaking existing ones.