If I have an edits only object type, and am setting one of the properties to be the UserID on object creation within an Action can I use a restricted view to lock down read access to the author of that Object?
How would I set that up?
Yes, in this case you would need to make sure that the backing datasource is the restricted view. When setting up the restricted view’s granular policy, include “The User’s User ID is equal to column userID.” as one of the rules in the policy.
With this in place, the objects of this Object Type will now be restricted to just users whose ID matches the object property.
To clarify on this one - I have a backing datasource with values coming from a pipeline. I have a column in that backing datasource that used to be backing a property, but I’ve now changed that property to be edit-only. If I set up a policy in the backing RV based on this property, will the policy be evaluated based on the user edits (which wouldn’t exist in the backing dataset) or will it be evaluated based on data from the pipeline (which is not reflected in the object, given that property is now edit-only). Thanks!