Salesforce Customizing Objects, Fields, and Page Layouts

Every business is different. A logistics company needs fields that a hospital does not. A real estate firm tracks properties in a way a software company never would. Salesforce is built to adapt — administrators customize objects, add fields, and arrange page layouts to match exactly how each business operates. No coding is required for any of this.

Why Customization Matters

Out of the box, Salesforce comes with standard objects and standard fields. These cover common business needs well, but they rarely cover everything. Customization lets your Salesforce org speak your company's language — using the field names, picklist values, and page layouts your team recognizes from day one.

Creating Custom Fields

You add a custom field to any object through Setup. Navigate to Object Manager → [Object Name] → Fields and Relationships → New. The Field Creation wizard walks you through these steps:

Step 1: Choose a Data Type

Pick what kind of information the field holds. Common choices:

• Text — a short word or phrase (up to 255 characters)
• Text Area (Long) — paragraphs of text (up to 131,072 characters)
• Number — a numeric value
• Currency — a money value that respects the org's currency settings
• Date / Date-Time — a calendar date or a date plus time
• Picklist — a drop-down with predefined options
• Multi-Select Picklist — allows selecting multiple options
• Checkbox — a true/false toggle
• Formula — a calculated value based on other fields
• Lookup / Master-Detail — a link to another record

Step 2: Set the Field Label and API Name

The Label is what users see on the screen (e.g., "Contract Signed Date"). The API Name is what developers use in code (e.g., Contract_Signed_Date__c). The __c suffix is automatically added to every custom field API name.

Step 3: Set Field-Level Security

Choose which Profiles can see and edit the new field. You can make a field visible to all users, read-only for some, or completely hidden from others.

Step 4: Add to Page Layouts

Choose which page layouts include this field. A field that is not on a layout is invisible to users — even if they have field-level security access to it.

Custom Objects

When no standard object fits your need, you create a Custom Object. Navigate to Setup → Object Manager → Create → Custom Object. You define:

• The object's label (singular and plural)
• The API name (ends in __c)
• The Record Name field — usually a text name or an auto-generated number
• Optional features: allow reports, allow activities, track field history

Examples of Custom Objects

Page Layouts

A Page Layout controls which fields, related lists, and buttons appear on a record page — and in what order. Every object has at least one page layout, and administrators can create multiple layouts for the same object to serve different user groups.

The Page Layout Editor

You open the Page Layout Editor from Setup → Object Manager → [Object] → Page Layouts. The editor is a drag-and-drop canvas:

  ┌──────────────────────────────────────────────────────┐
  │  PALETTE (available fields, buttons, related lists)  │
  ├────────────────────────┬─────────────────────────────┤
  │  LEFT COLUMN           │  RIGHT COLUMN               │
  │  Account Name          │  Account Owner              │
  │  Phone                 │  Industry                   │
  │  Website               │  Annual Revenue             │
  ├────────────────────────┴─────────────────────────────┤
  │  RELATED LISTS                                       │
  │  Contacts | Opportunities | Cases | Files            │
  └──────────────────────────────────────────────────────┘

You drag fields from the palette into the canvas to place them. You drag them out to remove them. You reorder by dragging up or down. Changes take effect immediately for all users assigned to that layout.

Assigning Page Layouts to Profiles

In Salesforce Classic-style layout assignments, you assign specific page layouts to specific Profiles — so sales reps see a different Account layout than support agents see. This is done through the Page Layout Assignment table inside the Page Layouts section.

Lightning App Builder and Record Pages

In Lightning Experience, record pages are built with the Lightning App Builder — a more powerful visual editor. Instead of just arranging fields, you arrange entire components: related lists, charts, Chatter feeds, custom components, and more. You access it from Setup → Lightning App Builder.

Lightning record pages can be assigned to:

• A specific Profile (role-specific views)
• A specific App (different layout per Salesforce app)
• A specific Record Type (different layout per business process)

Record Types

A Record Type lets you have different business processes, picklist values, and page layouts for the same object. For example, a company that sells both products and services might have two Opportunity Record Types:

• Product Sale — shows product-related fields, uses a product-focused page layout
• Service Contract — shows service fields, uses a different page layout with different stage values

When a user creates a new Opportunity, Salesforce prompts them to choose the Record Type first. The chosen Record Type determines which fields and layout they see.

Field History Tracking

Salesforce can track changes to specific fields over time. When you enable Field History Tracking on an object (up to 20 fields per object), Salesforce logs every change: who changed the value, when they changed it, and what the old and new values were. This history appears in the "Field History" related list on the record and is very useful for auditing and compliance.

Key Points

• Custom fields extend standard objects; custom objects handle entirely new data categories.
• Every custom field and object API name ends in __c.
• Page Layouts control what users see on a record — drag-and-drop in the layout editor.
• Lightning App Builder creates richer record pages with full components, not just fields.
• Record Types allow different processes, picklist values, and page layouts within the same object.