Skip to main content
Solved

Custom Rule to Prevent a Role Access to Specific Records

  • January 14, 2026
  • 0 replies
  • 227 views

Forum|alt.badge.img+9

I am trying to create a custom rule for a specific Role that prevents this role the ability to view specific records using the Record ID field.  For some reason I can get this to work for one record, but when I add an additional record ID it seems to break.  Can anyone tell me why and what I am doing wrong?

In the screengrab below, If I only have one Record ID look up (1643) line it works fine.  When I add the second Record ID for 1881 this seems to break the rule.

 

Thanks,

Brian

Best answer by hueyal

Try changing the condition from 'any' to 'all'.  If you have both with any, it would always be true.

Forum|alt.badge.img+9
  • Registered
  • Answer
  • January 14, 2026

Try changing the condition from 'any' to 'all'.  If you have both with any, it would always be true.


Forum|alt.badge.img
  • Registered
  • January 14, 2026

Disregard.


JeffRichey47779
Forum|alt.badge.img+4

Brian,

In addition to the change suggested by hueyal, you might also consider changing your condition to use "is not equal to" rather than "does not contain" because once your database grows large enough your rule will exclude unintended records such as 11643.


Forum|alt.badge.img+9
  • Author
  • Registered
  • January 15, 2026

Thanks everyone.  SMH...I should have known this.  

Brian