Marc Andre Lacas 5/22/2015 7:56:42 AM @Slava I fully understand that this is feasible using behaviors (this is what I mentioned as "managing what part of the form can be shown or not"). I will indeed promote the other idea you mentioned, as it appears to extend the current functionalities in an interesting way. Yet, I still think that having the possibility to create more than one form per table could be a way to easily create "tailored" access to tables.
However the "one form fits all" model has limitations. If I want to reorder the sections for a specific set of users, I would need to create various sections (sometimes duplicating some of them) and then use the criterias to show/hide the related sections depending on who is watching.
A multiple forms approach, would also make it simpler to manage/ to visualize for the admin, and, like Kelly mentioned, it would help create a better, more consistent UI for our users, which is important if we want them to adopt and use the tools we create with TeamDesk.
Maybe the key is having the possibility of naming a set of criterias as "FORM A" , then a second set as "FORM B" and then have a "selection box" in the form editor so you can quickly change from one set to the other. In short, you still have one form, but when you edit it in the "form edit" you can switch from one "layout/design" to the other.
| 
