Not sure if this belongs in Scholar or Core, but Scholar permits users to manage Embargo on their own objects (i.e. those that they've deposited), and this is the only example of this sort of permissioning in Islandora currently. For better IR-like functionality, would be very helpful to be able to grant users other CRUD permissions on objects/datastreams which they've deposited. I don't believe this should be too difficult as the only "hook" that's theoretically required is the Fedora "Owner" property on a given object, which appears to be functioning as it should (e.g. line 108 in https://github.com/Islandora/islandora_scholar/blob/7.x/modules/islandora_scholar_embargo/islandora_scholar_embargo.module).
For reference, please see http://lib-hf1.lib.sfu.ca/islandoraperm.png – notice that "Manage embargo on own objects" near the bottom is the only such permission that can be applied to only a user's own objects; ideally, editing metadata, replacing or reverting datastreams, and removing objects would also have a separate "only own objects" permission to be granted to authenticated users. As it is, we've effectively only been able to grant the CR- permissions and not the -UD ones to authenticated users because this distinction isn't respected.