Skip to main content
Authorization → History lists saved policy versions by day, newest first. History is read-only. To restore one rule, open the version’s Cedar tab and recreate or edit that rule on Policies. To restore a complete saved set, use the policy API to select its version in the deployment. Review its scope and mode before applying it.

Entries

Kontext saves a version for each action on Policies. History shows one entry per version with a title that describes the action: For API saves without an origin, History uses a title that describes the change. When an action also updates the observing set, it can save that set without an action label. History describes that version by its changes too. Examples include “First version”, “Added 2 policies”, “Removed 1 policy”, and “Policies unchanged, source edited”. Each entry shows who saved it, the time, and the first eight characters of its version ID below the title. History marks the version endpoints run now with an “Enforcing now”, “Observing now”, or “Paused” pill. Dashboard actions create separate History entries even when they restore earlier policy text. An API save without origin can reuse an existing version when the source is identical. If the deployment selects that version, History moves the pill to its entry.

Find an entry

Use Search history… to filter by title, version ID, date or person. History shows the newest eight entries. Click Show N older entries to see more, up to the newest 50 versions. To link to an entry’s drawer, add ?version=<id> to the History URL. Use the full version ID.

Inspect a version

Click an entry to open its drawer with these tabs: