Limiting Entity access for App Users and Data Collectors

[ahblake]

@norlowski

In this phase, there are two options for Entity access:

1. Data Collectors and App Users will either be able to access all entities in a project
2. Or only the entities they have created. This should benefit projects with many entities where users only need access to their own.

I have now tried using this in a simple, but very helpful use case (a single project distributed to all my different deployments that collects feedback, collects new questions / views existing questions & answers (and submits clarifications). The app user is unique for each deployment, so some lists eg name are filtered, but others are shared eg the master list of FAQs), a few comments;

• It is possible to have the same 'Created by' label if you assign an App user to "Tracy" and also a web link to "Tracy", but they will not see each other's entities as their __creatorId is different. Expected, possibly could cause confusion but can be easily cleared up by looking at the __creatorId value (and should be setup as 'Tracy (App)' and 'Tracy (Web)' etc)
• Using Enketo for a new submission directly from Central (not a public access link) doesn't (yet) have entity filtering (logged in as project manager), which is useful, but if the form is not compatible with Enketo there's no 'unfiltered' Collect access as far as I know. (I couldn't test WF for this as my form won't load, gives a "Failed to construct 'URL': Invalid URL" error that I haven't solved yet)
• Being able to filter access by properties in phase 3 will be a really nice improvement.

@norlowski

@ahblake does this get closer to solving for your use case more quickly?

eep I missed this a year ago. I think P3 is what I really need for my use cases (access to more than just one owner)