Permission set priority and mixing different groups

[fritz.]

Hello -

I'm currently implementing a setup at our department and there is one issue that might have to be worked around if what I've noticed is normal.

On the surface it sounds pretty basic. There are about 5 different groups who only want to see assets specific to their group. I can set it up so that there are five permission sets with a relevant metadata field filter in the metadata group.

However, they have asked for there to be a condition where, if an asset comes in that doesn't have a group specified, that it be visible to all five groups so that it can be identified and then have its field set to the appropriate group. There are also a few individuals who would like to see assets from, say, Group 1 and 3, but not group 2,4, or 5.

If you give a permission set a higher priority, then it just overrules the other metadata field setting. That is by design and I see it in multiple instances of the documentation.

But, if both permission sets have the same priority, it doesn't allow for both permission sets to live happily and show the user both assets with each appropriate filter. Instead, it appears to select the permission set with the higher ID and appears to ignore the one with the lower ID.

If it's normal, so be it, but I want to make sure I'm not overlooking something before thinking of a workaround.

[fritz.]

update: as I suspected, this is normal behavior, so don't create permission sets based around multiple choices of the same metadata field if you want to differentiate items.

[sleepingtree]

Fritz-
Did you ever find a long term solution for this? i.e. If a user is a member of two permission sets - how can they see assets from both permission sets?

colin.