Our org uses an installed package for our partner users to collect and submit data when offline, which they can sync to Salesforce when online. As such, they need create/edit permissions for our custom objects. Our experience site allows them to view all of the created data, but it also allows them to do manual edits that have resulted in serious errors. Is there a way to maintain their edit privileges but just remove the edit button so they can't use them on the Experience Site?
#Experience Site
Lucas is spot on about the layer to target - here's the concrete how. The key is that the Edit button is driven by the page layout's actions, which is completely separate from the object/field edit permission on the profile or permission set. So you can pull the button without touching the access your offline package needs.
The package syncs through the API, not the UI, so removing the on-screen Edit action doesn't affect it at all - the permission stays, only the button goes.
Steps:
1) Clone the page layout your partner users get for the custom object (so internal users aren't affected).
2) On the cloned layout, expand the 'Salesforce Mobile and Lightning Experience Actions' section, click to override the predefined actions, and remove the Edit action (plus any Edit-style quick actions). If that section still shows the default set, you have to click 'override' first before it lets you customize it.
3) Assign that layout to the partner profile (Page Layout Assignment on the object, per profile / record type).
Two things to check depending on how the site is built:
- If your Experience Builder record page uses the standard Record Detail / Record Banner component, it honors the layout actions, so step 2 handles the Edit button.
- If it uses a custom component or a custom Action list on that component, the actions are defined there instead - edit the component's action list in Experience Builder rather than on the layout.
Also worth closing off: inline editing (the pencil on fields) and the Edit row-action in any list views or related lists on the site, since those are other ways to edit. Inline edit can be turned off so they can't bypass the missing button.
Net effect: partner users keep full edit access for the offline sync (via API), but the community UI is effectively read-only - exactly the split you're after.
