All I could find about this issue are some threads scattered over the past couple years that unfortunately contain no real workaround, and without the in-depth knowledge of the core one can not "invent" the easy way to accomplish this - where not being more versed php devel, with only "CPT" (Copy-Paste-Tweak (tm:) approach to others php code makes it even harder
It’s no problem (after grasping the required knowledge, of course:) to setup user groups to limit what their members can list in the resource tree at manager backend, but then all users of the same group share the same permissions over the resources which is not the needed behavior. Without finer-grained user-oriented acl it is not possible to differentiate those at all...
But there must be some way to at least show only those "createdby" resources for a logged-in user, so he/she is then put in a position to e.g. list & edit only own resources within a container.
As a solution there were propositions that this could be best achieved with a plugin - but no actual code was exposed
So it would be great if (time-permitting, of course) The Gurus shared some of their solutions to this problem..
☆ A M B ☆