I want to create an ACL that is read-only for the portal.

[bonsai]

I want to prevent users from updating records on the portal screen.

I think the easiest way is to use an ACL, but is it possible to create an ACL that only affects the portal?

I'm thinking of a read-only ACL for the table.

Hiding UI policies and actions, and hiding the save button displayed in the portal's form widget—all of these can be solved by making them read-only using ACLs.

[Ankur Bawiskar]

@bonsai 

when you create table.None WRITE ACL, it can't distinguish if the record is opened from native or portal

So the ACL will impact both the places

Why not use onLoad client script and check the URL contains portal name and accordingly make fields readonly?

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[bonsai]

The field issue was resolved using UI policies.

UI actions can also likely be handled by deactivating them.

However, the "Save" button displayed on the form widget cannot be hidden without customizing the widget.

If only ACLs were used, everything would be solved...