Loading
Salesforce now sends email only from verified domains. Read More
Extend Salesforce with Clicks, Not Code
Table of Contents
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

          Search all of Salesforce Help
          Data Classification Metadata Fields

          Data Classification Metadata Fields

          Record the data owner, field usage, data sensitivity, and compliance categorization for any standard or custom object field. You can also access data classification metadata in the Salesforce API and Apex.

          Required Editions

          Available in: Salesforce Classic and Lightning Experience
          Available in: All editions
          User Permissions Needed
          To edit data classification fields: Customize Application or Modify Data Classification

          You can use the data classification metadata fields on most standard and custom objects. Before you begin, review these limitations.

          • Compliance categorizations don't appear on fields suffixed with __pc when you query the Person Account object. While __pc fields appear in Person Account queries, they reside on the Contact object. To see their compliance categorization, query the Contact object instead. The same limitation applies whether you're using Tooling API (FieldDefinition) or Metadata API (CustomField). Learn more about Person Accounts and their relationship to Contacts.
          • If you're working in Object Manager, these metadata fields aren't available for the User object: Data Owner, Data Sensitivity Level, and Field Usage. To apply them to the User object, use the CustomField Metadata API or the Data Classification Upload tool.
          Field Description
          Compliance Categorization

          The compliance acts, definitions, or regulations that are related to the field’s data. Default values:

          • CCPA—California Consumer Privacy Act
          • COPPA—Children's Online Privacy Protection Act
          • GDPR—General Data Protection Regulation
          • HIPAA—Health Insurance Portability and Accountability Act
          • PCI—Payment Card Industry
          • PersonalInfo—Personal information. For use with the Enhanced Personal Information Management feature. Only available if Enhanced Personal Information Management and Digital Experiences are enabled.
          • PII—Personally Identifiable Information

          The field corresponds to the ComplianceGroup field on the FieldDefinition Tooling API.

          Data Owner

          The person or group associated with this field. The data owner understands the importance of the field’s data to your company and might be responsible for determining the minimum data sensitivity level.

          The field corresponds to the BusinessOwnerId field on the FieldDefinition Tooling API.

          Data Sensitivity Level

          The sensitivity of the data contained in this field. Default values:

          • Public—Available to the public to view but not alter.
          • Internal—Available to company employees and contractors. This data must not be shared publicly, but it can be shared with customers, partners, and others under a non-disclosure agreement (NDA).
          • Confidential—Available to an approved group of employees and contractors. This data isn’t restricted by law, regulation, or a company master service agreement (MSA). It can be shared with customers, partners, and others under an NDA.
          • Restricted—Available only to an approved group of employees and contractors. This data is likely restricted by law, regulation, an NDA, or a company MSA.
          • MissionCritical—Available only to a small group of approved employees and contractors. Third parties who are given access could be subject to heightened contractual requirements. This data is almost always restricted by law, regulation, an NDA, or a company MSA.

          The field corresponds to the SecurityClassification field on the FieldDefinition Tooling API and the FieldSecurityClassification SOAP API.

          Field Usage

          Tracks whether the field is in use. Default values:

          • Active—In use and visible.
          • DeprecateCandidate—Planned for deprecation and no longer in use.
          • Hidden—Not visible and possibly planned for deprecation. Use with caution.

          Changing the value of Field Usage doesn’t hide or expose the field.

          The field corresponds to the BusinessStatus field on the FieldDefinition Tooling API.

          You can customize the values for the Compliance Categorization, Data Sensitivity Level, and Field Usage fields.

          • To edit the Compliance Categorization values, select Edit Compliance Categorization Picklist Values on the Data Classification Settings Setup page or update the ComplianceGroup picklist using the StandardValueSet Metadata API type.
          • To edit the Data Sensitivity Level values, select Edit Data Sensitivity Picklist Values on the Data Classification Settings Setup page or update the SecurityClassification picklist using the StandardValueSet Metadata API type.
          • To edit the Field Usage values, update the FieldBusinessStatus picklist using the StandardValueSet Metadata API type.
          Note
          Note You can also access data classification metadata by querying your Salesforce data. For example, this sample query retrieves values for all data classification metadata fields in account and lead records.
          SELECT Id, DeveloperName, Description, BusinessOwnerId, BusinessStatus, SecurityClassification 
          FROM FieldDefinition 
          WHERE EntityDefinitionId in ('Account','Lead')
           
          Loading
          Salesforce Help | Article