This idea stems from this post in the Esri Community: Re: Restrict editing to related record only; not a... - Page 2 - Esri Community
There are editing workflows in our organization that require the ability for field workers to add, update, and delete related records that have been joined to a parent feature layer. However, we do not want users to be able to add, update, or delete the parent features.
For example, we have a layer for water pipes and a related table for field observations related to the pipes. We publish the water pipes layer with a relationship class to the observation table to Portal. But the edit settings for a Feature Layer apply to both the parent features and the related table. This makes it possible for field workers to create and delete water pipes which is not what we want them to be able to do.
This idea is to allow for more fine-grain editing controls between parent features and related tables so that users can edit related records but not the related parent features.
