@ Rick
Yes, this is correct. The original design, there was no concept of a user/entry permissions. Grafting this on is complex, as such, I’m taking small steps rather get myself in a corner that I can not get out of. Each release I tackle this in one form or another. Form 2.x was a big step in this direction as the code for this type of permissions is handled by the ore Connections plugin. With that I can make my changes and Form benefit automagically.
Right now, the “bandaid” solution is to not allow users to select visibility options that will lock them out of their data. This will be addressed in future revisions.
As for the very last comment … I’ll add it to my feature request list, not sure I’ll add it though … may as a free extension so it’ll be available to those that do want that ability. Adding it as an extension actually seems like a very good idea, it’ll make sure that I design it in a very flexible way.
