Protect integration-synced CRM fields from accidental edits

Mark CRM standard fields as read-only for a business, so data kept up to date by an integration isn't overwritten by a manual edit.
Lock down the fields your integrations own
From Partner Center or Business App, a partner admin can mark any standard CRM field as "read-only" for a specific business. 
Hidden during Form creation and editing:
 to protect from manual edits 
Visible in tables:
 so everyone can see the data.
Setting carries through Blueprints:
 so you can configure it once and apply it to many accounts.
Why it matters
Before, standard fields could always be edited by hand, even when an integration was keeping them in sync. One well-meaning edit could break that sync and leave the record out of date. Now you decide which fields people can change, so your integrations stay reliable and the data your team - and your clients - rely on stays accurate.
Who it's for
Partners syncing CRM data from another system (such as a field-service, billing, or ERP tool)
Partner admins who manage CRM settings for client accounts
Agencies rolling out a consistent CRM setup across many accounts with Blueprints
How to get started
Note: Requires partner admin access.
In Partner Center or Business App, go to Administration> CRM Objects
 and select the standard field you want to protect.
Mark it as "read-only" and save.
To use the same setting on other accounts, create a blueprint from this account and apply it.
FAQs
Q: Does read-only hide the data?
A: No. The field still shows in tables. It's only hidden from create and edit forms.
Q: Does this apply to every business I manage?
A: It's set per business. Use Blueprints to apply it across accounts.
Q: Can I undo it?
A: Yes. Turn read-only off for the field to make it editable again.