# Forms: Ability to have questions trigger a task/subtask creation & option to share/manipulate at form level **URL:** \ **Category:** Product Ideas\ **Created:** [27 June 2019 16:29 UTC](https://forum.asana.com/t/forms-ability-to-have-questions-trigger-a-task-subtask-creation-option-to-share-manipulate-at-form-level/53706 "2019-06-27T16:29:37Z")\ **Posts on this page:** 1\ **Showing post:** 7
**Author:** ![Phil\_Seeman](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/phil_seeman/32/81525_2.png) [@Phil\_Seeman](https://forum.asana.com/u/Phil_Seeman)\ **Post date:** [26 October 2019 00:51 UTC](https://forum.asana.com/t/forms-ability-to-have-questions-trigger-a-task-subtask-creation-option-to-share-manipulate-at-form-level/53706/7 "2019-10-26T00:51:02Z")
> [@Christina\_Roberts](#): > > Being able to populate subtasks from a form is really important. FYI you can accomplish exactly this with my [Flowsana](https://flowsana.net) integration. It has an If-Then Rule action of “add subtasks from a template”. If you want the same set of subtasks added for every form submission in the project, you can trigger that rule action with “If a new task is added” which will fire whenever a new form is submitted. Or for added flexibility, you could even have a different set of subtasks be added depending on a form field that you map to a custom field. > [@Christina\_Roberts](#): > > We were told forms would be a solution to locking task templates (task template could be copied and the user can edit the copy, but the task template would remain locked). The above solution handles this as well - the template task containing the subtasks can reside in any project you choose. So you could restrict access to that project to only those users who you want to be able to edit the subtask template(s). --- _[View the full topic](https://forum.asana.com/t/forms-ability-to-have-questions-trigger-a-task-subtask-creation-option-to-share-manipulate-at-form-level/53706)._