Feature suggestion, Form Folders

What is the general goal of the feature?
Arranging forms in different folders depending on the relevant project to limit the number of forms the field enumerators can access and help keep things organized and prevent errors when different teams works on different forms.

What are the most likely user stories for how and when this would be used by someone on your team?
Currently when you share the server URL with field enumerators, they can download all forms.
To prevent this, you need to create team members and only share relevant forms with relevant members, but this could be hard for large scale data collection, and here comes the rule of project folders\directories.
when field enumerators try import new form they can download all forms which are in the root folder, in addition to forms in any different folder if they input the folder name or the folder name could be shared with the server URL e.g. https://kc.humanitarianresponse.info/accountName/folderName

Can you sketch out graphically how you think this should look/work in practice?
Not really.

How useful would this feature be to other users or organizations?
This will reduce the number of new kobo accounts needed, as all kobo users can organize their forms in folders instead of creating different accounts for different projects.

What can you contribute to making this feature a reality?
Analysis and test support.

Hi @galrajeh, welcome back.

I think there is a similar suggestion for creating folders for forms. You might want to upvote that one too.

2 Likes