Automatically match privileges between items in a relationship class.
Sister idea to: Relationship classes: Let us read the origin table... - Esri Community
The body of the ideas is almost the exact same, based off the same event.
This has bitten several colleagues recently.
As it currently stands (3.1), when you
The privileges were applied to a feature dataset and therefore the items within it, but not to the related tables corresponding to those items. Note: The items in the dataset were the origin tables.
Users could see the feature dataset and the items within, but when they were added to the map, the "adding data" popup would appear, spin for a bit, then close before hitting the "finishing up" stage and actually adding to the map. Their records could also not be viewed in Catalog.
We could not figure out what the problem was until someone realized that the related standalone table did not have the same privileges applied.
No error message was given.
Updating the privileges for the related table fixed it.
So there are two actual problems here:
1) This idea: Items participating in a relationship class do not have privileges automatically applied
and
2) Separate idea: Having privileges unevenly applied to items in a relationship class makes it so that none of the data can be viewed.
Please automatically match privileges for items in a relationship class, or at least match privileges applied to the origin table to the destination table.*
*This is because the destination table had no issues itself-- if you apply privileges to just it, works just fine.