Implementing Data Locking Measures

I’m interested in exploring options to enhance data integrity by implementing measures to prevent or restrict editing, even for project owners. Are there any existing functionalities or recommended practices to ensure that submitted records remain unaltered once collected?

Your insights and recommendations would be greatly appreciated.

Thank you.

Hi @Ahmad, maybe explain a bit more about this so that we could understand your issue? Kindly please also provide some context here so that we could relate for better understanding!

Thank you @Kal_Lam ,

We are currently in the process of creating approximately 10 surveys in KOBO. It is important for us to ensure that the data cannot be edited/changed post-submission.

While the existing sharing settings in KOBO largely meet our requirements, there is one crucial aspect that needs addressing. Presently, the Survey/Project owner still have the ability to edit submissions. We are exploring ways to restrict this capability either through adjusting settings or by implementing specific design features within the form itself. For instance, incorporating a calculated field that flags duplicate submissions could serve as a preventive measure.