This has been raised by @Nicolai-vKuegelgen. It is slightly illogical that an owner or delegate can see the landing zones of others in the UI and perform actions such as moving and deleting, but they do not have actual iRODS access to the zone collection.
I don't really see a harm in providing owners and delegates with this currently missing access.
Implementation-wise this would be relatively simple: just add owners and delegates to where we enable/disable zone access in landing_zone_create and landing_zone_move taskflows.
Tagging this for the next major version, unless I hear objections from anyone. I'll write a full spec after the Easter holidays.
This has been raised by @Nicolai-vKuegelgen. It is slightly illogical that an owner or delegate can see the landing zones of others in the UI and perform actions such as moving and deleting, but they do not have actual iRODS access to the zone collection.
I don't really see a harm in providing owners and delegates with this currently missing access.
Implementation-wise this would be relatively simple: just add owners and delegates to where we enable/disable zone access in
landing_zone_createandlanding_zone_movetaskflows.Tagging this for the next major version, unless I hear objections from anyone. I'll write a full spec after the Easter holidays.