DATE:
AUTHOR:
The folks at Scrut
Improvement

Enhanced Policy Editor to save edits securely

DATE:
AUTHOR: The folks at Scrut

What’s new?

We’ve introduced two major enhancements to the Policy Editor:

  1. A concurrent editing lock to prevent multiple users from editing the same policy at the same time

  2. A manual Save option to ensure changes are not lost when auto-save fails

Why it matters

With this update, you can now prevent editing conflicts by locking the policy for others while it's being edited, secure your work with a fallback save option, and safeguard offline edits so that no work is lost during connection drops.

How it works

  • Concurrent editing lock

    • When one user opens a policy for editing, it is locked for all others

    • Anyone else attempting to open it sees a “Another user is editing” message

    • If the editor becomes inactive or disconnects, the lock automatically expires after a timeout

  • Manual save fallback

    • A "Save Now" button appears if auto-save fails (e.g., API issue)

    • Edits made while offline are stored locally

    • Upon reconnecting, the platform will either auto-save the changes or prompt the user to save manually

These updates ensure a more reliable and conflict-free editing experience for teams working on policies.

Need help?

Your Customer Success Manager is always ready to help if you need assistance.
Explore all recent product updates → View now

Powered by LaunchNotes