Mediasets, Images Permissions on Objects & Actions

I have a workflow, where I would like to upload an image for an object via an action type. This works nicely. However, if the object property of the image is replaced or the object is deleted, the image file will persist in the media set and pile up.

Is there a way to also delete it from the mediaset or even better, have a retention policy for the medaset that checks if the reference is still in use and do some sort of inner join with the ontology once in a while?

Also, mediasets currently dont support granular permissions but I can actually define the media set property as edits-based and back it by a restricted view. Who can see what now? Can I hide the mediaset in a confidential folder / project / marking and people with access to the restricted view can still see it?

Best

Florian

Hello,

Unfortunately, there isn’t currently a way to delete items if the associated object has been deleted. You can set a retention policy on the entire media set, but it would delete any item after the set time period has passed, even if that media item is still being referenced by an object.

We are looking into a better solution here, but don’t have a timeline yet.

You are correct that you can back an object with a restricted view that has media references. In this case, someone who can see a row with the media reference can see the media item without needing to have any permissions on the media set itself.

Awesome that you can have the media being accessible through the permissions of the restricted view. What if I put a marking on my media set that contains the object-referenced items. Would that mean that the users can still access the object and media which would be permissioned to the restricted view. This way, I would not need to create an additional project.

At the moment, if you put a marking on the media set, users who don’t have the marking will not be able to see the media items on objects, even if the RV policy says they can. We will be releasing a new feature that allows you to configure whether markings should be assumed at the Ontology or not, which should be released in the next month.

2 Likes