Apex
Salesforce’s native programming language used to write custom logic, integrate with external systems, and automate complex processes.-
Batch Apex
A feature that allows processing large sets of records asynchronously in chunks, ideal for background data updates and cleanups. -
Chatter
Salesforce’s social collaboration tool that enables teams to share files, post updates, and collaborate in real time. -
Communities
Branded portals in Salesforce for customers, partners, or employees to connect, find answers, and engage with your business. -
Console
A user interface designed for support agents and sales reps to manage multiple records and tabs efficiently in one workspace. -
Custom Object
A user-created object that stores data specific to your business needs, like “Invoices” or “Subscriptions.” -
Data Loader
A client application used to import, export, update, and delete large volumes of data quickly in Salesforce. -
Debug Log
A log that records code execution and errors—helpful for developers troubleshooting Apex code or automation. -
Delegated Administration
Allows certain non-admin users to perform admin tasks, like creating users or resetting passwords, for specific roles or groups. -
Einstein Analytics
A business intelligence tool that helps you visualize, explore, and get insights from your Salesforce and external data. -
Field
A specific data point stored on an object, such as “Phone Number,” “Email,” or “Opportunity Amount.” -
Field-Level Security
Controls whether a user can view or edit specific fields on records, regardless of their access to the object. -
Flow
A visual automation tool used to create guided screens, logic-based processes, and record automation—without writing code. -
Governor Limits
System-enforced limits in Salesforce to prevent one user’s code from consuming too many shared resources. -
Lightning Web Components (LWC)
A modern JavaScript-based framework for building fast, reusable web components on the Salesforce platform. -
Managed Package
A bundle of Salesforce components (apps, objects, Apex classes, etc.) that can be shared, sold, or installed into other orgs. -
Metadata
Information that describes how Salesforce is structured—like objects, fields, page layouts, and automation settings. -
Multi-Currency
Enables organizations to handle transactions in multiple currencies while tracking exchange rates and reporting consistency. -
Object
A table in Salesforce used to store data—either standard (like Accounts or Contacts) or custom (like Projects or Events). -
Opportunity
A record that represents a potential revenue-generating deal or sale in the CRM. -
Page Layout
Controls the placement and visibility of fields, buttons, and related lists on a record detail page. -
Dashboard
A collection of charts, graphs, and tables that visually represent reports for tracking KPIs and performance metrics. -
Lightning Experience
The modern Salesforce user interface designed for speed, responsiveness, and better usability. -
Permission Set
Grants additional access or functionality to users without changing their profile. Can be stacked for flexible permissioning. -
Salesforce Mobile App
An official Salesforce app that gives users access to records, dashboards, and tasks on-the-go. -
SOQL (Salesforce Object Query Language)
Used to retrieve records from Salesforce objects—similar to SQL but tailored to Salesforce’s data model. -
Trigger
A block of Apex code that runs automatically in response to events like record creation, update, or deletion. -
Sandbox
A copy of your production org used for testing, development, or training without affecting live data. -
Process Builder
A no-code tool that lets you automate processes based on record changes using rules and immediate actions. -
Lightning App Builder
A drag-and-drop builder for designing custom pages for Lightning Experience and the Salesforce Mobile App. -
Data Model
Describes how objects and their fields relate to each other in your Salesforce org. -
Knowledge Base
A central repository of help articles, FAQs, and documents used in customer service and self-service portals. -
API
Application Programming Interface—a set of rules that lets external systems communicate with Salesforce. -
REST API
A lightweight API protocol using standard HTTP methods (GET, POST, etc.) to integrate external apps with Salesforce. -
Authentication
The process of verifying a user’s identity before granting access to Salesforce features or data. -
Validation Rule
Checks if data entered into a record meets specific criteria. If not, it prevents the record from being saved. -
Dependent Picklist
A dropdown field where options in one picklist depend on the value selected in another. -
List View
A filtered and sortable view of records based on specified criteria—great for managing data quickly. -
Global Value Set
A reusable set of picklist values that can be used across multiple fields in different objects. -
Sharing Settings
Controls who can view, edit, or delete records—based on ownership, role hierarchy, or criteria. -
Approval Process
Automates the steps required to get a record approved based on certain conditions and user roles. -
Audit Trail
A log of administrative changes made in Setup—like field creation, workflow changes, and new profiles. -
Field History Tracking
Tracks changes made to specific fields on records, including old and new values, user, and timestamp. -
Report
Displays Salesforce data based on filters and groupings—ideal for insights, summaries, and exports. -
Queue
A shared list of records waiting to be worked on, often used for Lead, Case, or Task assignments. -
Record Type
Customizes page layouts and picklist values for different business scenarios within the same object. -
Sharing Rule
Grants broader access to records beyond role hierarchy—for example, sharing all high-value Opportunities with a team. -
Custom Tab
A user-defined tab that appears in the Salesforce app and links to objects, pages, or web content. -
Profiles
Define what users can see and do in Salesforce—object access, field-level permissions, and app visibility. -
Role Hierarchy
Determines data visibility based on a user’s position in the org structure—managers can see their team’s records.