Preventing anonymous submission of data : should be at project level & not account level

Hi :smiley:

Currently, to prevent an anonymous submission of data : it means you only need the link of the form to fill it (on Enketo or on ODKcollect) is at account level.
Example:
If you do nothing,
in ODKCollect you will need to put the following link into the settings about the server :
https://kc.humanitarianresponse.info/nameaccount
And you will have access to the form.

An option exists to ask for the login and the password in order to prevent an anonymous submission of data.
You need to do this :
Account settings > Tick the following box:
image

I am using KOBO Humanitarian response & ODK Collect v1.22.4.

Nevertheless, this feature will forbide every anonymous submissions for all accounts’ forms. Is it possible that you only want to block a free access for a specific project: as one with sensitive datas and not for all your surveys.
The unique solution is to have several accounts.

That’s why preventing anonymous submission of data should be at project level & not account level. It does not make sense otherwise in terms of data protection, this is a huge issue.
It will simplify the use of KOBO and increase possibilities of data protection.

This feature could have the aspect on a new line on projects settings by ticking the same box that currently exists at account level.

Thanks to think about it !!
Chloé