Hi @tejb54, you can create a privacy rule in Data > Privacy to work with these fields.
So, for the List data type, create a role called “Can Access” (or something like that), where the condition is just like you said “Current User’s SecretKey is This List’s Secret Key.” Then enable everything that user would be able to do (find the List in searches, view fields, etc.)
Now, you should have an opposing role. Either the default “Everyone Else” is that opposing role (where things are disabled/unchecked) or you can create a separate role called “Cannot Access” where the condition is “Current User’s Secret Key is not This List’s Secret Key” and uncheck/disable stuff.
Just make sure that the Everyone Else default role is also figured in to work with your custom roles. When it comes to creating privacy roles, I like to turn everything off for the Everyone Else rule, and create specific roles for each user case so that I know exactly what people do / do not have access to.
Hope this helps!
Gaby at Coaching No Code Apps (formerly Coaching Bubble)
Courses & Products, Tutorials, Private Coaching, and High-level Development
Start Learning Today