Hi @Larry Tung! We recently discovered that RR will filters out for the user all records that doesn't meet the RR criteria including records owned by the user.
E.g. I created a record and ticked a "Private" checkbox to mark it as private and shouldn't be seen by others. I then create a Restriction Rule that only allow users to see records that have not had Private ticked. I assumed that, similar to Sharing Rules, users will still be able to see records where they are the owner, even if it doesn't meet the criteria. So in this case, I should still be able to see that Private record I created but my colleagues will not be able to see it. Turns out I can't see it either!
Is this expected functionality for Restriction Rules? I would have assumed that ownership of a record will bypass restriction rules just like with sharing rules.
This is "working as designed;" the record criteria can prevent an "owner" from seeing the record depending on how you wrote the record criteria. It sounds like you want OR clause support.
See:
- Restriction rules let you enhance your security by allowing certain users to access only specified records.
- When you first get to the Restriction Rule page, you also see the same image as what is in the documentation.
This means regardless of how you got access, such as:
- owner of the record
- granted manual shares
- above someone in the role hierarchy
you have access to the records that meet the record criteria (out of the data you've been granted access to).