OK, the title doesn't quite say it - but it kind of does.
Say a form template is an agency profile. It's submitted once for an agency, and is a persistent and regularly used source of information regarding that agency going forward. Some of the information may need to be updated on an annual or more frequent basis, and the owner has update permissions when the form is in an "active" state.
However, many agencies may have more than one person who would be needing to update the information. In fact, multiple people might well provide different aspects of this profile. It holds a number of documents as well as text input.
We can't use roles to add permissions for users, because roles are applied to the form template and not to a form instance. There will be many hundred different agencies that fill out profiles, and folks from each agency must not touch other agency submissions, obviously.
This also isn't a situation where we want to change owners on the form - I know and understand that capability, but it isn't appropriate here.
I am thinking that we need something along the line of an "instance access role" which can be defined as an unassigned entity to the form template, but only after a submission can it be populated - similarly to the fact that a form instance cannot have an instance_id or an owner until it has been initially submitted.
At any rate - I assume that others have bumped up against a similar kind of need. One thought is that we could, instead of using the form itself as the primary and permanent agency profile, just use it as a vehicle to upload the data, and have each user who needs to edit the profile use a new instance of the form template, and control which profile they can update by checking their DNN system role memberships ... but that devalues the use of EF as a primary and sufficient tool.
Other users have thoughts and/or solutions for this kind of situation?
Thanks for any feedback -