Platform App Builder key terms

A collection of tabs, objects, and related settings that gives users a focused workspace for one business process. Admins build apps in Setup and control which users can open them.

A database table inside Salesforce that stores records of one type, such as accounts or invoices. Each object has fields that define the data it can hold.

An object an admin creates to store data unique to the business, identified by the __c suffix in its API name. It comes with standard features such as page layouts, reports, and sharing settings.

An object delivered with Salesforce, such as Account, Contact, or Opportunity, that ships with predefined fields and behavior. You can extend it with custom fields and customize its layouts.

A single data attribute on an object, such as a text, number, or date value. Fields define what information each record can store and how it appears on layouts.

One row of data in an object, such as a single contact or a single case. A record holds values for the object's fields and can be linked to records in other objects.

A setting assigned to every user that defines baseline permissions: which objects and fields they can access, which apps they see, and other defaults tied to their user license.

The modern Salesforce user interface built from pages and components, configured with the Lightning App Builder. It replaced the older Salesforce Classic interface for most users.

A loosely coupled link from one object to another where the parent field is optional and deleting the parent does not delete the child. Useful for optional or non-cascading connections.

A tightly coupled link where a child record cannot exist without its parent, the parent field is required, and deleting the parent deletes the children. Sharing and ownership follow the parent record.

A custom object with two master-detail relationships, used to create a many-to-many link between two other objects. For example, a membership object joining contacts and campaigns.

A field on a parent record that calculates a count, sum, minimum, or maximum of related child records. It is available only when a master-detail relationship connects the two objects.

A read-only field whose value Salesforce calculates from other fields, merge fields, or functions. It is evaluated when the record is displayed or referenced rather than stored as data.

A setting that lets different users see different picklist values, page layouts, and business processes for the same object. Record types are assigned through profiles or permission sets.

Settings that control whether a user can view or edit a specific field, regardless of what the page layout shows. Field-level security is configured on profiles and permission sets.

The baseline sharing setting for each object that sets the most restrictive level of record access, such as Private or Public Read/Write. Other sharing tools can only widen this access.

A custom field flagged as an external ID that stores a unique identifier from another system. It is used to match records during upserts and data imports.

A client application for bulk importing, updating, upserting, exporting, or deleting large volumes of records. It works with CSV files and handles thousands to millions of rows.

A browser-based tool for importing up to 50,000 records for common objects and straightforward imports, with built-in duplicate matching against existing records.

A condition that must be false before a record can be saved. When the condition evaluates to true, Salesforce blocks the save and shows the error message you define.

A declarative automation built in Flow Builder that can collect input, run logic, update records, and call other actions. It can run on a schedule, from a button, or when records change.

A legacy point-and-click tool for automating record changes with criteria and actions. Salesforce now recommends Flow instead, but exam questions may still reference its behavior.

An older automation feature that fires field updates, email alerts, tasks, or outbound messages when criteria are met. It cannot create records and is being retired in favor of Flow.

A structured approval workflow with steps, designated approvers, and actions that run when a record is submitted, approved, rejected, or recalled.

A formula on one object that references fields on a related object through a lookup or master-detail relationship, giving access to parent or child data without creating extra fields.

A drag-and-drop tool for building Lightning pages and apps from standard and custom components, with visibility rules that target different users, record types, and devices.

A page built in the Lightning App Builder that controls how a record detail view looks. Admins can assign different pages to specific apps, record types, or users.

A setting that controls which fields, buttons, and related lists appear on a record page. Layouts are assigned by profile and record type and are still used in Lightning.

A small set of key fields shown in the highlights panel, in mobile cards, and in feed items so users see the most important information about a record at a glance.

A button or link that lets users quickly create or update records, log calls, or send email from a record page or a related list without leaving the current context.

A quick action available from the Salesforce header anywhere in the app, not tied to a specific record or object page. Useful for logging calls or creating records from anywhere.

A navigation item in an app that opens an object's list view, a custom page, or a web page. Admins add tabs to apps to control which areas users can reach.

A separate copy of a production org used for development, testing, and training without risking live data. Types include Developer, Developer Pro, Partial Copy, and Full.

A bundle of metadata components sent from one related org to another, such as sandbox to production. Components are added manually and dependencies must be resolved before deployment.

The process of moving metadata such as objects, fields, and flows from one org to another, using change sets or tools like the Metadata API.

A namespaced package distributed to other orgs or through AppExchange. Subscribers cannot edit its components, and the developer can release upgrades that install cleanly.

A package that delivers components without a namespace and cannot be upgraded after installation, because the subscriber can freely edit everything it contains.

A collection of additional permissions and settings assigned to users to grant access beyond their profile. It adds object, field, or system permissions without creating new profiles.

A relationship where one metadata component requires another, such as a field requiring its object or a layout requiring a field. Unresolved dependencies block a change set deployment.