Skip to main content
Editing a Guard Policy does not change what a Guardian enforces until you re-apply the new version. This is the most common “my change didn’t work” cause.

​
What happens when you edit

Saving any rule change creates a new version. The new number only has to be unique for that policy — it need not be higher than the last, so you can publish in any order or fill in between numbers; only duplicates are rejected. The Guardian keeps using the version pinned to it — usually the older one — so live behavior is unchanged until you re-point it.

​
Re-point the Guardian

1

Open the Guardian's Policies

Open your Guardian → Policies. The assigned policy shows its current version (e.g. v0.1.0).
2

Edit Policy Version

Use the version control on the policy row to open Edit Policy Version.
3

Pick the new version

Select the newer version (e.g. v0.1.1) and choose Update Version.
Re-point the Guardian to v0.1.1

Re-point the Guardian to v0.1.1

​
Verify

Re-run a test call (see Add a PII policy step 4). If behavior still hasn’t changed, confirm the assigned version matches the version you edited, and check the call in Opticon.
Check the call in Opticon

Check the call in Opticon

Pinning is per Guardian: applying a version to one Guardian doesn’t move any other Guardian that uses the same policy — each keeps its own pin. If you opened the policy from a Guardian’s own assigned-policy card, the editor offers a shortcut after saving — apply to this Guardian now or save only.
Versioning lets you stage changes safely: edit and review a new version, then flip the Guardian to it (and roll back by re-pointing to the previous version).