kubajal
commented
4 years ago Hi, I'm just a random administrator of a Formtools installation and I can share my experience about editing submissions by clients. There is a module called Submission Accounts which does just what you described. Installing a new module is extremely easy so it should not be a problem to get it up and running. With that module enabled you can configure an ordinary input text field to be treated as the password to the submission, which the client can use to log into the submission afterwards and modify it at any time.
There is a huge concern about this module though as of v2.0.5. The critical problem is that those password fields are not encrypted. Due to the fact that the password field is a normal text field, the password is seen as-is in the submission when the client logs in again just like any other input fields. In other words, the password is displayed in the submission after logging back, rather than being hidden/not sent back at all. The passwords are stored & sent through the internet as plain texts. That definetly can look worrying to the end user.
Some time ago I made a proposition of changes that aim at hidding passwords and encrypting them using MD5 hash: https://github.com/formtools/module-submission_accounts/issues/11. Unfortunately they have not been reviewed by @benkeen yet.
Terrox
I couldn't find this in the docs. I plan to use this for client specifications documents and have a big form with lots of questions that the client can return to later and finish off. I would have a fairly obvious message for fields which need attention and I think that would suit my needs.