Then, I will use the WMF extension for now. I understand that you won't prioritize this. Just for future reference, I will document the structure we have come up with : I currently employ already a more hierarchical project/subproject structure that can be use over several semesters and makes it possible for me to reference all students at once:
Mar 13 2017
Mar 10 2017
The different edit/view policy is not the actual problem here. The problem with using spaces to solve the described scenario in an automatic fashion is that a) there is no spaces API b) the view policy for the space would also be a complex policy b.1) There is no API to create complex policies.
Ok, so root problem is more of a user story. Sorry to not getting this right. But this was my first feature request on Phabricator.
From an usability side, it would also be a possibility to create policy objects just in time, when the API user submits a transaction touching a policy:
Root of the Problem: The conduit API does not provide the possibility to create custom policies. Therefore, the fine-grained policy model of phabricator cannot be used in automated workflows.