Question about Permission Inheritance

Question about Permission Inheritance

avatar

Hello,

I just have a question about permission inheritance. We are just starting to look closely at the granular permission model in RDM, since previously we didn't really use it (all our users up to this point have been admins of the RDM tool itself and have full access to all shared entries within it). But now we are starting to add users that will not have full access, so I am trying to understand how the permissions work.

One thing I'm confused on is the inheritance. I see we have several "levels" we can set permissions to, including "inherited" and "inherited+custom". When I set to "inherited+custom", it shows the people to the right that are inherited, and the people underneath that are "custom" (i.e.explicit permissions set on this object), which is helpful.

However, when I set to "inherited", I notice it only displays the permissions being inherited sometimes but not others. For example, it will show "disallowed" for permissions that are still at their default "disallowed" state on the parent, but for other permissions that have been customized at the parent level, the child folder does not show those as inherited.

In this screenshot, we can see examples of all the above scenarios - the "view" and "edit" permissions both show inherited permissions. However, for some reason even though the "add" permission is also set to "inherit", it shows nothing even though it's parent folder does in fact have an explicit/custom permission configured for "add". The only difference between the "add" and "edit" permissions on the parent is that "add" is customized at the parent while "edit" is not.

ac22dd66-cc62-43d3-a9b5-6a6d6969f006
So I am not sure if this is all by design , or it is a bug or maybe I am missing something here. But I would think, based on how it shows the inherited permissions in the other two scenarios ("view" and "edit"), then it should do the same for "add" since that is also set to "inherited". Is that accurate or is there a reason it is not showing? Any advice is appreciated!

Edit - After some more testing, I see this is consistent - anywhere I have custom permissions configured on the parent, child objects (folders or entries it appears) will show blank when set to "inherited". But, if the same child object is instead set to "custom+inherited" and add a custom permission, then it will show the inherited permission to the right as well.

This is RDM v2026.1.16 using SQL Server data source.

Best regards,

David Willis

ac22dd66-cc62-43d3-a9b5-6a6d6969f006.png

All Comments (1)

avatar

Hello,

Thank you for the detailed report and the additional testing you did.

I was unable to reproduce the behavior on my end, so I was wondering if you could try recreating the entry from scratch and check if the issue persists.

Please let us know what you observe after doing so.

Best regards,

Carl Marien