The Create Audit Fields feature in Salesforce allows System Administrators to grant users the ability to set system audit fields (such as Created By, Created Date, Last Modified By, and Last Modified Date) when inserting records through API tools like Data Loader or Salesforce Flows. This is useful for data migrations where you need to preserve the original creation timestamps and authors from a source system.
Available in: Essentials, Enterprise, Performance, Unlimited, and Developer Editions
Important: While Create Audit Fields is a low-risk feature, Salesforce recommends reviewing the available documentation before enabling it. Key reference articles are listed in the Additional Resources section below.
There are two organization-wide permissions associated with this feature:
Note: With these permissions, Lightning and API users can fill audit fields on record creation only through API tools. Edits cannot be made after the record is created.
In Salesforce Classic, APEX code cannot be used to update Lead record owners to inactive users, even when users have the "Set Audit Fields upon Record Creation" and "Update Records with Inactive Owners" permissions assigned.
User Interface in the Quick Find box and select User InterfaceAfter enabling the org-wide permissions, grant the following permissions to users with custom profiles. Note: Standard profiles cannot receive these permissions — use a permission set instead (see Step 3).
If your users are on standard profiles (which cannot be modified), create a Permission Set to assign these permissions:
Note: Create Audit Fields can be enabled for Professional Edition after the Salesforce API has been provisioned. See Salesforce Editions with API Access for more information.
000386699

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.