My Birthday Month Special: 15% off any Blazer2Role program until November 30. Get my code →
← Back to blog
salesforce admincustom fieldsdata qualityadmin skills

Before You Add a Custom Field in Salesforce: A 4-Question Checklist for Admins

Before You Add a Custom Field in Salesforce: A 4-Question Checklist for Admins

"Can you just add a field?" is one of the most common requests a Salesforce admin hears. Adding the field takes a few minutes. Living with it takes much longer, because every field touches security, data imports, reporting and your org's limits.

This checklist gives you four questions to answer before you build. It is not a reason to say no. It is a way to say yes and be clear about what the field commits the team to.

The 4-question checklist at a glance

Question Why it matters Where it lives in Salesforce
1. Who should see it, and who should not? Visibility reaches far beyond the record page Field-level security (field permissions)
2. Should it be required, and where? Required fields affect imports, integrations and layouts Universally required fields, page layouts
3. Does anyone need its history? History tracking has a per-object limit Field History Tracking
4. What will tell us to retire it? Deleted fields still count against limits for a while Deleted custom fields

1. Who should see it, and who should not?

Field permissions, also called field-level security, let you "specify whether users can view or edit each field for an object." The setting reaches much further than the record page. Salesforce lists where it restricts access, including:

  • Detail and edit pages, related lists and list views
  • Reports
  • Email and mail merge templates
  • Experience Cloud sites and portals
  • Imported data and Salesforce APIs

Checklist: name the profiles or permission sets that need to edit the field, the ones that only need to read it, and the ones that should not see it at all. Pay special attention to reports, because a field visible in a report can be grouped and shared quickly.

2. Should it be required, and where?

There are two kinds of "required." Making a field required on a page layout affects that layout. Making it universally required is much broader: the field "must have a value whenever a record is saved within Salesforce, the Lightning Platform API, Connect Offline, Salesforce for Outlook, the Self-Service portal, or automated processes, such as Web-to-Lead and Web-to-Case."

Salesforce's considerations for universally required fields include:

  • The field "Cannot be removed from a page layout."
  • It is "required across all record types."
  • "You must include universally required fields in your import files or the import will fail."
  • "Quick Create does not enforce universally required fields."

Checklist: if someone asks for a required field, ask whether every import file and integration can supply a value. If not, consider a validation rule with a clear error message instead, or make it required only on the layouts where people enter it. For writing good error messages, see our validation rule examples.

3. Does anyone need its history?

Someone will eventually ask, "Who changed this, and when?" That question can only be answered if field history tracking was turned on. Salesforce lets you "select a combination of up to 20 standard and custom fields per object," and on events and tasks you can track "up to six fields per object."

History is not kept forever either. Without Field Audit Trail, "Salesforce retains field history data for up to 18 months, and up to 24 months via the API."

Checklist: decide now whether the field needs history, and check how many of the tracking slots on that object are already used.

4. What will tell us to retire it?

Deleting a field does not free space immediately. "Deleted custom fields and their data are stored until your org permanently deletes them or 15 days have elapsed, whichever happens first." During that time, "the field counts against the maximum number of custom fields allowed in your org."

Restoring has its own quirks: restored formula fields come back "in a disabled state," and restored fields "don't display in search results immediately."

Checklist: agree on a simple signal for retiring the field, such as "no values entered in six months" or "the process it supports has ended," and write it in the field's description.

How to use the checklist with a requester

Keep it short. Read the four questions back to the person asking, write down the answers, then build. Two habits make this work:

  1. Answer in costs, not opinions. "Making it universally required means every import must include it" is easier to discuss than "I don't think we should."
  2. Know when to skip it. A small, reversible change that nothing depends on does not need a meeting.

This is part of thinking like a product owner for your org, which we cover in why Salesforce admins must think like product managers. If you are new to the role, our guide to your first 90 days as a Salesforce admin shows where requests like this fit into the job.

Practice it in a free org

In a free Developer Edition org, create a test field, turn on history tracking for it, then delete it and open the deleted fields list. Seeing the deleted field still listed makes question four easy to remember, and it is a good example to mention in an interview.

Frequently asked questions

What is field-level security in Salesforce? It controls whether users can view or edit a specific field. It applies across pages, list views, reports, templates, portals, imports and the API.

What is the difference between a required field and a universally required field? A field required on a page layout only applies to that layout. A universally required field must have a value whenever a record is saved anywhere, including the API and imports.

How many fields can I track with field history? Up to 20 standard and custom fields per object, and up to six per object on events and tasks.

What happens when I delete a custom field? The field and its data are stored for up to 15 days, and during that time it still counts against your org's custom field limit.

Where can I read a shorter version? Our Substack post Four Commitments You Make When You Add a Field covers the same four questions in a quick read.


Blazer2Role helps career changers move into Salesforce roles, and we sell coaching and courses. Platform limits and behavior vary by edition and change over time, so check current Salesforce documentation for your org. Drafted with AI assistance under Blazer2Role's editorial direction.

My Birthday Month Special · ends November 30

Take 15% off any program this November.

Dedric's birthday month, your discount. Leave your email and we send you the code BIRTHDAY15. Use it once on any Blazer2Role program at checkout, from coaching to the full course package.

Code valid until November 30, one per person. A coach also follows up with next steps.