Deleting policies

Deleting a policy removes it from active enforcement — the AI no longer flags violations against it. This page explains what deletion does, what stays, and who can do it.

What happens when you delete

When you delete a policy:

1. Enforcement stops immediately — the extension no longer flags violations against the deleted policy.
2. The policy is soft-deleted — it and its full history are retained in the system, not permanently erased. Self-serve restore is not available yet (see future capabilities below).
3. Analytics are preserved — past violation data is not deleted. Historical reporting totals stay accurate. The deleted policy shows as “Deleted” (its name and details are masked) in analytics dashboards and CSV exports, but its violations still roll up into the policy area and team totals.

Who can delete

Users with the DELETE_POLICIES permission can delete a policy. Refer to Roles & permissions to see which roles include this permission.

Deleting a policy from the UI

From a policy’s detail view:

1. Click the Delete button (typically in the top-right or in a menu).
2. Confirm the deletion in the dialog that appears.
3. The policy is immediately marked as deleted. You’re redirected to the policies list.

Once deleted, the policy no longer appears in the active policies list, but it may still be visible in historical reports and audit logs.

Deleting multiple policies at once

From the policies library:

1. Select policies using the checkboxes in the table. A toolbar appears showing how many are selected.
2. Click Delete… in that toolbar.
3. If you don’t have delete permission for every selected policy’s area, you’ll see a warning naming how many will be skipped, and the confirmation dialog covers only the policies you’re allowed to delete.
4. Confirm in the dialog that appears. Like single delete, this stops enforcement immediately and can’t be undone from the UI.

After the delete completes, a summary shows how many policies were deleted and, if any were skipped (due to missing permission, or because they no longer existed), how many.

Bulk delete is capped at 200 policies per request. The limit isn’t enforced client-side, so selecting more than 200 rows and confirming returns an error naming the cap — split a larger selection into batches of 200 or fewer.

Important cautions

Deletion cannot currently be undone from the UI. There is no self-serve restore button. If you delete a policy by accident, contact your administrator or support; they can restore it if needed via admin tools.

Think deliberately before deleting. If you only need enforcement to stop, set an expiry date instead: once that day has passed the policy is no longer retrieved for detection, and it stays in the repository (see Policy lifecycle). If you expect to want the policy back, weigh that against deletion being effectively permanent from the UI (no self-serve restore yet — see below).

Soft deletion and future capabilities

Today, deletion is a soft delete: the data stays for compliance and audit purposes, but enforcement stops. Permanent, complete deletion — where the policy is hard-erased and no trace remains — is not available yet. Self-serve restore from the UI is also planned for a future release.

Related

• Policy lifecycle — how policies move between draft, published, and other states
• Revision history — the audit trail every save and delete writes
• Roles & permissions matrix — who can do what