A generic privacy policy rule that allows when an entity is being authorized
as part of a cascading delete from a parent entity. Handles two cases:
When the field has not yet been null'ed out due to a cascading set null. This is often
required for read rules to authorize the initial re-read of the entity being update set null'ed.
When the field has been null'ed out due to a cascading set null. This is often required
the update rules for the field nullification.
These two cases could theoretically be handled by two separate (stricter) rules, but are combined
to simplify configuration since practically there are few cases where having them be combined would
preset an issue.
Example
Billing info owned by an account, but records who created the billing info in creating_user_id. User is a member of that account.
User can delete themselves, and the billing info's creating_user_id field is cascade set null'ed when the user is deleted.
A generic privacy policy rule that allows when an entity is being authorized as part of a cascading delete from a parent entity. Handles two cases:
These two cases could theoretically be handled by two separate (stricter) rules, but are combined to simplify configuration since practically there are few cases where having them be combined would preset an issue.
Example
Billing info owned by an account, but records who created the billing info in creating_user_id. User is a member of that account. User can delete themselves, and the billing info's creating_user_id field is cascade set null'ed when the user is deleted.