When you save framework edits that materially change scoring, a blocking modal lists each change and how many clients are affected before you can proceed. This guide explains it.
💡 Tip — Who can use this For platform admins, in the framework editor on save.
Quick reference
| Step | Action |
|---|---|
| 1 | Review the material changes and confirm |
Step 1 — Review and confirm material changes
When you save framework edits, the editor first posts the payload to a preview endpoint. If the diff returns non-empty material changes (added/removed pillars, changed weights, new/removed metrics or flag rules), a blocking modal appears. It lists each change path and the number of affected client workspaces, and requires Confirm & Save to proceed.
Cosmetic-only edits (description fixes, primer text) save with no popup.
📝 Note — The PUT re-runs its own diff After you confirm, the actual save (PUT) re-runs the diff independently to write a version-log entry if the change was material. This is best-effort auditing.
💡 Tip — Read the affected-client count The number of affected workspaces tells you the blast radius of your change. A change affecting hundreds of clients deserves more deliberation than one affecting a handful. If unsure, test on a copy or consult before confirming.