ODK central project manager with no/more granular access to data

[seewhy]

I would also support this and have a particular use case,

Restricting web user access to specific forms within a project

Not sure if this is actually a support request or an idea... Please reallocate accordingly 1. What is the issue? Please be detailed. Context: I'm building a plugin for QGIS (yes, another one) that uses the API to download submission data (and hopefully will integrate pyODK shortly, once I can figure out how to manage the Pydantic dependency within QGIS! That will hopefully allow the plugin to work "bi-directionally" with entities when the relevant functions escape into pyODK) I…

But it is more widely applicable to ensure data managers have access to relevant submissions / forms / entities without needing to split data collection into (perhaps unknowable) silos prior to deployment: