Strapi Record Locking Plugin

When you run Strapi in a real team, content conflicts happen fast. Two editors open the same entry, both make changes, one saves last, and data is gone. Strapi does not solve this out of the box.

‍

The Record Locking plugin from Notum fixes that.

‍

What it does

The plugin prevents multiple users from editing the same record at the same time.

‍

When a user opens an entry for editing, the record is locked. Other users can still view it, but they cannot edit it until the lock is released. The admin UI clearly shows who is currently editing the record.

‍

This removes silent overwrites and makes multi user editing predictable.

‍

How it works

The plugin adds a small backend layer and extends the Strapi admin UI.

• Uses WebSockets or polling to track active editors
• Stores record locks on the server
• Shows lock status directly in the admin
• Automatically releases locks when a user leaves or disconnects

No custom workflows. No editorial hacks. Just a simple technical lock.

‍

Compatibility

• Latest version supports Strapi v5
• Fully rewritten in TypeScript
• Older versions are available for Strapi v4

The codebase is small, readable, and easy to extend.

‍

When you should use it

This plugin makes sense if:

• You have multiple editors or admins
• Content accuracy matters
• You already hit overwrite issues
• You want predictable behavior without training editors

If you run Strapi as a single admin CMS, you probably do not need it.

‍

Why we built it

We run Strapi in production for large teams. Record overwrites were a real issue.

This plugin is the simplest solution we found, so we open sourced it.

‍

https://market.strapi.io/plugins/@notum-cz-strapi-plugin-record-locking

‍