Lock Record/Row from editing based on a status field
6
6 Stars Cleaning
Artem Kunytsia somehow like this feature. We need a way to protect agains giant mistakes...
Nate Montgomery @ SmartSuite
Merged in a post:
🔒 Lock records to avoid further Editing
6
6 Stars Cleaning
We really need the ability to Lock certain records for further Editing without authorization (maybe with a password?)
In 2 unfortunate instances, someone from our teams bulk edited +4k past records by mistake.
Would be great to have an option like: If Status is Complete -> Lock the record
Jon Darbyshire
Thank you for posting, 6 Stars Cleaning! I have a few more questions for you:
- Can you provide more details on the level of authorization required to unlock a record for editing?
- Would you like this lock feature to be applied to all records or should it be customizable per record?
- Should the lock be automatically applied when the status is 'Complete', or would you prefer to have manual control over when a record is locked?
6
6 Stars Cleaning
Jon Darbyshire Hi John,
- it would be great if even the Admin need a passkey or something to perform the edit for specific locked records.
- In our case, we need all the Records Created before Yesterday (so basically we'll need some flexibility in choosing which records - again our case will be past created records.
- Manual control would be amazing. Possibly all the Records created before Yesterday.
We like the flexibility that SS offer when editing in Grid View with the Linked Records but the human error is hard to be avoided. We had 2 instances where somone bulk edited +4k records with Linked records by mistake.
Currently it's ultra easy to destroy by mistake any table with thousands of records and linked records in seconds.
Also, it would be helpful a Grid View History Versioning similarly with Google Sheets where you can restore everything how it was 3 days ago for example.
Thank you for listening your customers! SS FTW! 🚀
Artem Kunytsia Jon Darbyshire Tara Darbsyhire
6
6 Stars Cleaning
yes!
Arne B.
It would also be great if this would allow more granular control like:
- lock certain fields when a record gets a certain status
- allow fields to be writable upon a status change
- don‘t allow fields to become writable
- prohibit status change once a certain status is reached.
B
Bongi Simelane
Yes, this is critical. Ideally, once the record is CLOSED, you do not want that record to be addited, not until the person changes status from CLOSED to another status, which will then allow editing.
The user should be able to open the review, but all fields should remian READ-ONLY, not until the user changes the status.
When the use re-opens the record, i.e. changes status from CLOSED to IN REVIEW (as an example), a mandatory prompt reason for re-opening a closed record would be ideal.
This would help a lot in Pharmaceutical sector.
Although it's not ideal to bring competitor here, but Zoho Projects have this feature already in Closed tasks. Please consider this.