ACL to allow anyone to create records

[Wayne Richmond]

Hi. I have created a custom table called 'u_stolen_items' that I want to allow anyone to be able to create records on. However, because I have the High Security Settings enabled, I believe this is preventing me from having a 'blank' ACL to allow this. I have created an ACL rule for 'create' where there are no conditions, however, this doesn't work (I assume because of the aforementioned High Security Settings). I have tried using 'true;' in the Script but that also didn't work. I tried adding the 'public' rule but this also doesn't work. Does anyone have any ideas?

[Wayne Richmond]

Hi Rohit,

This does allow users to create records, thanks. However, the desired result should be that the user can only view their own records after it's been created. This new read ACL allows users to view all records.

[chirag_bagdai]

Hello,

For read ACL you can add condition in condition builder,   Please find below screenshot :

[chirag_bagdai]

Also, I would say you should use "snc_internal" role instead of using "public" role reason is explained by Dave.

[Dave Smith1]

Interesting... I wasn't aware of this role, but I see it requires a plugin (com.glide.explicit_roles) before snc_external and snc_internal roles become available.

That's useful information. I've no idea why there seems to be slightly conflicting approaches to defining authenticated/anonymous connections, but it's good to know about these other roles should they trip you up in future!

[chirag_bagdai]

I think, the plugin will be activated automatically if the instance version is after H.  

The reason for keeping "snc_internal" is if the ACL doesn't have any role, this will be added automatically for security reason.