A-Z dictionary

An Account in Salesforce represents a company, organization, or individual that you do business with. It is one of the most fundamental standard objects and serves as the central hub for tracking all interactions, opportunities, cases, and relationships with your customers, partners, and competitors.

An Account Assignment Rule is a rule within Salesforce Enterprise Territory Management that automatically places an Account into one or more sales territories based on field criteria - for example, BillingState, Industry, AnnualRevenue, or a custom flag. Admins build each rule as a set of filter conditions on the Territory record; when accounts are created or updated (or when a manual 'Run Rules' job executes), Salesforce evaluates the rules and assigns matching Accounts to the territory, which in turn drives territory-based sharing and ownership.

An Account Contact Relationship in Salesforce (AccountContactRelation in the API) is a standard junction object that links a Contact to multiple Accounts beyond the Contact's single primary AccountId. Each Account Contact Relationship holds a ContactId, an AccountId, an IsActive flag, an IsDirect flag (true for the Contact's primary Account, false for secondary relationships), a Roles multi-select picklist, an optional StartDate and EndDate, and Org-wide-default sharing inherited from the parent records. This object solves the long-standing limitation that a Contact can have only one primary Account: with Account Contact Relationships enabled, a single Contact (for example, a board member who serves on the boards of three different organizations) can be related to multiple Accounts simultaneously, each with its own role and active period. Salesforce automatically creates one direct Account Contact Relationship for the Contact's primary AccountId; admins or users add additional indirect relationships as needed. The object is foundational to Salesforce industry clouds (Financial Services Cloud, Health Cloud, Nonprofit Cloud) where person-to-organization relationships are routinely many-to-many.

Account Settings is a Setup page where administrators configure organization-wide defaults for the Account object. Options include enabling or disabling Account Teams, allowing users to relate a Contact to multiple Accounts, and controlling whether Account hierarchies display in the Account record detail.

An Account Team is a group of users who collaborate together on an Account record. Each team member is assigned a specific role, such as Account Manager, Executive Sponsor, or Technical Advisor, and can be granted different levels of access to the Account and its related records.

An Account Team Member in Salesforce (AccountTeamMember in the API) is a standard junction object that adds a User to an Account Team and grants that user configurable access to the parent Account and its related Opportunities, Cases, and Contacts. Each Account Team Member record holds an AccountId, a UserId, a TeamMemberRole picklist (Account Manager, Executive Sponsor, Lead Qualifier, Pre-Sales Consultant, etc.), and four access-level fields: AccountAccessLevel, OpportunityAccessLevel, CaseAccessLevel, and ContactAccessLevel - each set independently to Read, Edit, or No Access. Account Team Members are the core mechanism Salesforce provides for collaborative selling, where multiple users with different specialties (sales rep, solutions engineer, customer success manager, executive sponsor) need shared visibility and edit access to a strategic account without using broader sharing rules. Salesforce also supports Default Account Teams configured per User - a preset list that automatically adds standard team members to every new Account a user owns.

An Action Layout controls which quick actions appear on a record page and how those actions are organized. Administrators use Action Layouts to customize the set of actions available to users in the Salesforce publisher, such as creating tasks, logging calls, or updating fields directly from a record.

Action Link Templates define reusable action links that can be attached to feed elements in Chatter. An action link is a button on a feed post that lets users take actions such as calling an API, downloading a file, or navigating to a URL directly from their Chatter feed. Templates allow developers to define these actions once and apply them across multiple posts.

An Action Plan in Salesforce is a predefined set of tasks that can be applied to one or more records to standardize repeatable business processes. When an Action Plan is assigned, it automatically generates a series of tasks with due dates, assignees, and dependencies so that nothing falls through the cracks.

An Action Plan Template is a reusable blueprint that defines a standard set of tasks, their order, timing, and assignees. Once created, the template can be applied repeatedly across different records to ensure consistent execution of business processes like onboarding, renewals, or compliance checks.

An Action Strategy is a set of business rules built using Salesforce Strategy Builder that powers the Next Best Action feature. It evaluates data about a customer or record and recommends the most relevant actions, offers, or steps for a user to take at a given moment.

The Actionable Relationship Center (ARC) is an interactive visual component that displays the relationships between records in a graphical, network-style layout. It allows users to see how Accounts, Contacts, and other entities are connected and to take actions directly from the visualization.

Actions & Recommendations is a Lightning component that surfaces Next Best Action suggestions and Einstein recommendations directly on record pages. It displays a prioritized list of recommended actions, offers, or steps for users to take based on strategy rules and AI-driven insights configured by the administrator.

Activation in Salesforce refers to the process of enabling a feature, configuration, or process so that it becomes live and functional in the production environment. Many Salesforce features require an explicit activation step after they have been built or configured, such as activating a Flow, a Price Book, or a custom platform feature.

In Salesforce Data Cloud, an Activation is the mechanism that sends a segment of unified customer profiles - along with selected attributes - to a downstream system so teams can act on it. Common destinations include Marketing Cloud Engagement, ad audiences (Google, Meta, LinkedIn), Salesforce CRM objects, Amazon S3, and custom HTTPS endpoints. Each one bundles a source segment, an Activation Target, a refresh cadence, and the specific DMO attributes and related objects to include in the outbound payload.

An Activity in Salesforce is an umbrella term for tasks, events, calls, and emails that are tracked on records. Activities represent the interactions and to-do items associated with Accounts, Contacts, Leads, and Opportunities. They are divided into Open Activities (upcoming) and Activity History (completed).

Activity History is a related list on a record that displays all completed activities, including past tasks, logged calls, sent emails, and events that have already occurred. It provides a chronological record of every interaction that has taken place with a customer or on a particular record.

Activity Settings is a Setup page where administrators configure organization-wide behavior for tasks and events. Settings include enabling Shared Activities (allowing a task or event to be related to multiple contacts), controlling whether users can relate events to multiple people, and managing activity reminder defaults.

An Add-on in Salesforce is an additional product, feature, or capacity that can be purchased on top of a base Salesforce subscription. Add-ons extend the functionality of your org beyond what is included in your standard license, such as additional storage, API calls, or premium features like Salesforce Shield.

A Salesforce Administrator, commonly called a System Administrator or simply Admin, is a person responsible for configuring, customizing, and managing a Salesforce org. Admins handle user management, security settings, data model changes, automation, and overall platform maintenance to ensure the org meets the organization's business needs.

An Advanced Function in Salesforce refers to a sophisticated formula or analytical operation used in reports, dashboards, or CRM Analytics (Tableau CRM). These functions go beyond basic arithmetic to include windowing functions, running totals, comparisons across groupings, and statistical calculations.

Advanced Search in Salesforce allows users to search for records across multiple objects using specific criteria, filters, and field-level conditions. Unlike Global Search, which performs a broad keyword lookup, Advanced Search lets users narrow results by object type, date ranges, record owners, and other field values.

After Conversation Work (ACW) is a configurable period of time given to service agents immediately after a customer interaction ends, during which the agent can complete wrap-up tasks without being assigned a new interaction. This time is used for writing notes, updating case fields, setting follow-up tasks, or dispositioning the conversation.

Age in Salesforce is a calculated value representing the number of days a record has been open or in a particular state. It is commonly used in reports and dashboards to track how long Cases, Opportunities, or Leads have been active, helping teams identify stale records and prioritize their workload.

In Salesforce, the term Agent has two distinct meanings that coexist in modern orgs. (1) A service representative - a human user whose role is to handle customer inquiries through phone, chat, email, or messaging, typically working in the Service Console. (2) An Agentforce AI agent - an autonomous, LLM-powered worker defined in Agentforce Studio that performs tasks (resolve support questions, draft emails, update records, orchestrate workflows) using natural language and grounded CRM data. Both types are first-class on the platform; the context usually makes clear which is meant.

An Agent Action is a specific, discrete task that an Agentforce AI agent can perform when interacting with users or processing requests. Each action is defined with a description, inputs, and outputs, and is mapped to an underlying capability such as a Flow, Apex class, or prompt template. Agent Actions are the building blocks of an AI agent's functionality.

Agent Builder is a setup tool in Salesforce that provides a guided interface for creating, configuring, and customizing Agentforce AI agents. It allows administrators and developers to define an agent's topics, actions, guardrails, and channels without writing code, making it easier to build autonomous AI agents that interact with customers or employees.

Agent Capacity in Salesforce refers to the maximum number of work items or conversations that a service agent can handle simultaneously. It is configured within Omni-Channel and determines how work is distributed to agents based on their current workload, ensuring no agent is overburdened while maintaining efficient utilization of available resources.

Agent Console is a legacy Salesforce interface that provides service agents with a single screen to view and manage multiple customer records at the same time. It displays a list view at the top of the screen and the details of a selected record at the bottom, enabling agents to work through cases and customer issues efficiently without navigating between separate pages.

An Agent Topic in Agentforce defines a specific subject area or domain of responsibility for an AI agent. Topics group related actions and instructions together, telling the agent what it should handle (for example, 'Order Management' or 'Returns'). Each topic includes a description, scope, instructions, and a set of associated actions that the agent can execute when a conversation falls within that topic.

Agentforce is Salesforce's platform for building and deploying autonomous AI agents that can take actions across sales, service, marketing, and commerce. Powered by the Atlas Reasoning Engine, Agentforce agents understand natural language, reason through multi-step tasks, and execute actions grounded in your organization's trusted CRM data, operating within defined guardrails and escalating to humans when needed.

Agentforce Agents is a Setup area where administrators and developers create, configure, and manage AI-powered autonomous agents. Each Agentforce Agent is defined with a set of topics, actions, and guardrails that determine what it can do, and it uses the Atlas Reasoning Engine to plan and execute multi-step tasks on behalf of users or customers.

Agentforce Assets is a Setup area for managing the reusable building blocks that power Agentforce AI agents, including prompt templates, agent actions, topics, and guardrails. These assets can be shared across multiple agents, enabling consistent behavior and reducing development effort.

Agentforce Data Library is a Setup feature that manages the knowledge and data sources available to Agentforce AI agents for grounding their responses. It allows administrators to configure which Salesforce objects, knowledge articles, files, and external data sources an agent can reference when answering questions or performing tasks.

Agentforce for Sales is a pre-built Agentforce solution designed to assist sales teams by autonomously handling tasks such as researching accounts, preparing for meetings, drafting follow-up emails, and nurturing leads. It uses AI to analyze CRM data and guide sellers with personalized recommendations and next steps throughout the sales cycle.

Agentforce for Service is a pre-built Agentforce solution that handles customer service inquiries autonomously across channels like chat, email, and messaging. It resolves common issues such as order tracking, returns, and FAQs by reasoning over Knowledge articles, case history, and customer data, and seamlessly escalates to human agents when the situation requires it.

Agentforce Specialist Certification is a Salesforce professional credential that validates a candidate's expertise in designing, building, and deploying Agentforce AI agents. The certification covers topics such as agent configuration, topic and action design, prompt template creation, guardrails, testing, and deployment of autonomous agents within the Salesforce ecosystem.

Agentforce Studio is a centralized workspace in Salesforce Setup where administrators and developers browse, create, and manage Agentforce AI agents and their components. It provides access to pre-built agent templates, a library of actions and topics, and tools for assembling and configuring agents for deployment across various channels.

Agentforce Testing Center is a Setup tool that allows developers and administrators to test Agentforce AI agents before deploying them to production. It provides a simulated conversation environment where testers can input sample utterances, review how the agent selects topics and actions, evaluate response quality, and identify issues in the agent's reasoning or behavior.

Agentforce Vibes Extension is a development tool that integrates Agentforce capabilities into external development environments. It allows developers to build, test, and debug Agentforce agent configurations and prompt templates directly from their IDE, streamlining the agent development workflow.

Agentforce Vibes IDE is an integrated development environment for building and testing Agentforce AI agent configurations. It provides a visual interface for designing agent topics, actions, and conversation flows, along with testing tools to simulate agent interactions before deployment.

An AI Model in Salesforce is a machine learning or large language model registered and configured for use within the Einstein 1 Platform, the AI layer that powers Agentforce. AI Models can be Salesforce-hosted foundation models (the capability formerly marketed as Einstein GPT), third-party models from providers like OpenAI, Anthropic, or Google accessed through Salesforce's LLM Gateway, or custom models brought in via Bring Your Own Model (BYOM). They are managed in Einstein Studio (Model Builder) and invoked by prompt templates, Agentforce agent actions, and Einstein predictions.

The AJAX Toolkit is a JavaScript wrapper around the Salesforce SOAP API that allows developers to execute API calls directly from web pages, including Visualforce pages, S-Controls, and custom buttons. It provides both synchronous and asynchronous JavaScript methods for querying, creating, updating, and deleting Salesforce records from the client side.

All Sites is a Setup page that displays a consolidated list of every Salesforce site in the org, including Experience Cloud sites, Salesforce Sites, and Site.com pages. It provides administrators with a single view to manage site URLs, activation status, and configuration details for all web properties hosted on the Salesforce platform.

Amazon Connect in Salesforce refers to the integration between Amazon's cloud-based contact center service and Salesforce Service Cloud. This integration allows organizations to use Amazon Connect's telephony infrastructure (including IVR, call routing, and voice capabilities) while leveraging Salesforce as the agent desktop, enabling screen pops, automatic call logging, and unified customer data access.

Amount Without Adjustments is a field in Salesforce's Collaborative Forecasts that displays the raw forecast amount for a forecast category based solely on the underlying Opportunity amounts, before any manual adjustments have been applied by the forecast owner or managers. It provides the unadjusted baseline figure for comparison.

Amount Without Manager Adjustment is a field in Salesforce's Collaborative Forecasts that shows the forecast amount including any adjustments made by the forecast owner but excluding adjustments made by managers above them in the forecast hierarchy. It lets managers see what their reps have forecasted before managerial overrides.

Amount Without Owner Adjustment is a field in Salesforce's Collaborative Forecasts that shows the forecast amount excluding any adjustments made by the forecast owner themselves. It represents the sum of the raw Opportunity amounts in the relevant forecast category, before the owner has applied their own judgment adjustments.

Analytics Groups is a Setup feature that controls user access to CRM Analytics (formerly Tableau CRM) applications, dashboards, and datasets. Administrators create groups and assign users to them, then grant each group specific permissions such as viewing, editing, or managing analytics assets.

In Salesforce, Annuity refers to a forecasting type that represents recurring revenue. When an Opportunity's Type is set to an annuity-based value, the forecast calculates revenue by multiplying the Opportunity amount by the number of periods remaining in the forecast, reflecting ongoing revenue streams rather than one-time transactions.

An Anonymous Block in Apex is a segment of Apex code that is not stored in Salesforce metadata and is executed on the fly. Anonymous blocks can be run using the Developer Console's Execute Anonymous window, the Salesforce CLI, or the SOAP API. They are commonly used for one-time data fixes, testing code snippets, and debugging, and they execute in the context of the running user.

An Anti-Join in SOQL is a type of semi-join query that returns records from a parent object where no matching child records exist. It uses the NOT IN operator with a subquery to filter out records that have related records in another object. For example, selecting Accounts that do not have any related Opportunities.

Apex is Salesforce's proprietary, strongly-typed programming language that runs on the Lightning Platform. Syntactically similar to Java, Apex allows developers to write custom business logic, including triggers, classes, and web service integrations, that execute on Salesforce servers in a multitenant environment with built-in governor limits.

Apex Classes is a Setup page that lists all Apex classes in the org, including their namespace, API version, status, and size. Administrators and developers use this page to view, create, edit, compile, and manage Apex classes, as well as to schedule Apex jobs and check code coverage.

The Apex Connector Framework allows developers to create custom adapters for Salesforce Connect that enable external data to be accessed as External Objects. By implementing the DataSource.Provider, DataSource.Connection, and related Apex classes, developers can query, search, and perform CRUD operations on data stored in external systems as though it were native Salesforce data.

An Apex Controller is an Apex class that provides the data and business logic for a Visualforce page. It handles user interactions, executes queries, performs DML operations, and controls page navigation. Salesforce provides Standard Controllers for each object, and developers can write Custom Controllers or Controller Extensions to add custom behavior.

Apex Exception Email is a Setup page where administrators specify email addresses that receive notifications when unhandled Apex exceptions occur. When Apex code throws an error that is not caught by a try-catch block, Salesforce sends an automated email with the exception details, stack trace, and the user context in which the error occurred.

Apex Flex Queue is a Setup page that displays batch Apex jobs that are waiting in the flex queue before being processed. The flex queue holds up to 100 batch jobs in a "Holding" status when the system's five concurrent batch processing slots are full. Administrators can reorder jobs in the queue to prioritize critical batch processes.

Apex Jobs is a Setup page that displays the status and details of all asynchronous Apex jobs, including batch jobs, future methods, queueable jobs, and scheduled Apex. It shows job status, start time, number of batches processed, and any errors encountered during execution.

An Apex Page (more commonly known as a Visualforce Page) is a page built using Visualforce markup that can include HTML, CSS, JavaScript, and Visualforce component tags. Apex Pages use a tag-based syntax similar to HTML and are rendered by the Salesforce platform. They can reference Apex controllers to display dynamic data and handle user interactions.

Apex Settings is a Setup page that controls organization-wide settings for Apex code execution. Options include enabling or disabling compiled Apex debugging, setting the default API version for new Apex code, and configuring settings like allowing deployments with reduced test coverage in sandboxes.

Apex Test Execution is a Setup page that allows administrators and developers to run Apex test classes and test methods in the org. It provides options to run all tests, selected test classes, or a test suite, and displays real-time results including pass/fail status, code coverage percentages, and error details for failed tests.

Apex Triggers is a Setup page that lists all Apex triggers in the org along with their associated objects, API version, and status (Active or Inactive). Triggers are pieces of Apex code that execute before or after data manipulation events like insert, update, delete, and undelete on Salesforce records.

Apex-Managed Sharing is a programmatic method of granting record access using Apex code. Developers write Apex to insert sharing records (such as AccountShare or CustomObject__Share) with a reason field set to a custom Apex sharing reason. Unlike standard sharing rules, Apex-managed sharing records can only be created or deleted by Apex code and are preserved during sharing recalculations.

ApexGuru Insights is a Setup feature that uses AI to analyze Apex code in the org and provide recommendations for improving performance, security, and best practices. It scans for common issues like SOQL queries inside loops, hardcoded IDs, and inefficient patterns, then presents actionable suggestions to developers.

API (Application Programming Interface) in the Salesforce Setup context refers to the configuration page where administrators manage API access settings for the org, including viewing API usage, enabling or disabling API access, and monitoring API request limits. Salesforce provides REST, SOAP, Bulk, Streaming, and Metadata APIs for programmatic data access.

API Catalog is a Setup feature that provides a centralized directory of all available APIs within the Salesforce org. It allows administrators and developers to browse, search, and discover APIs exposed by the platform, custom Apex REST services, and external services registered in the org.

API Manager in Salesforce is a setup tool used to manage the APIs exposed by MuleSoft Anypoint Platform within the Salesforce ecosystem. It provides capabilities for creating, publishing, and managing API proxies, setting rate limits and policies, and monitoring API usage, enabling organizations to govern their API strategy across connected systems.

API Version in Salesforce refers to the specific release version of the Salesforce API that a piece of metadata (such as an Apex class, trigger, Visualforce page, or Lightning component) is associated with. Each Salesforce release introduces a new API version number, and metadata components retain their assigned version to ensure backward compatibility. Administrators and developers can update the API version to access newer platform features.

API-Led Connectivity is an architectural approach promoted by MuleSoft (a Salesforce company) that organizes integrations into three layers of APIs: System APIs (connecting to backend systems), Process APIs (orchestrating business logic), and Experience APIs (serving data to end-user applications). This layered approach promotes reusability, agility, and governance across an organization's integration landscape.

An App in Salesforce (also called a Lightning App or Classic App) is a collection of tabs, objects, and other components grouped together to support a specific business function. Apps appear in the App Launcher and provide focused navigation for users. For example, a Sales app might include Leads, Opportunities, Accounts, and Reports tabs, while a Service app includes Cases, Knowledge, and the Console.

App Launcher is the waffle-shaped icon menu in Salesforce Lightning Experience that provides users with access to all the apps, custom apps, and items available to them based on their profile and permissions. Users click the App Launcher to switch between different Salesforce apps, search for specific apps, and access individual objects or items directly.

App Manager is a Setup page where administrators create, edit, and manage Lightning apps and Classic apps in the org. From here, admins can configure an app's navigation items, utility bar, branding, and the profiles that have access to each app. It provides a centralized view of all applications available in the org.

App Menu is a Setup page where administrators control which apps appear in the App Launcher for users across the org. Admins can reorder apps, hide or show specific apps, and set the default app visibility, determining the lineup of applications that all users see when they open the App Launcher.

AppExchange is Salesforce's official marketplace for third-party applications, components, and consulting services. It offers thousands of pre-built solutions that extend Salesforce functionality, ranging from free components to enterprise-grade applications. Every listing undergoes a security review before being published.

An AppExchange Listing is a published entry on Salesforce's AppExchange marketplace that represents an app, component, bolt solution, flow, or consulting service available for installation or purchase. Each listing includes a description, screenshots, pricing, reviews, ratings, and security review status, allowing customers to evaluate solutions before installing them.

AppExchange Marketplace is the Setup entry point for accessing Salesforce's official marketplace of third-party applications, components, and consulting services. From this page, administrators can browse, install, and manage apps and solutions that extend their Salesforce org's capabilities without custom development.

An AppExchange Publishing Organization is a Salesforce org designated by an ISV (Independent Software Vendor) as the source org from which managed packages are uploaded and published to the AppExchange. It is where the package's namespace is registered and where new versions of the managed package are developed, tested, and released.

AppExchange Security Review is a mandatory evaluation process that all paid and certain free AppExchange listings must pass before being published. Salesforce's security team examines the package's code for vulnerabilities such as SOQL injection, cross-site scripting (XSS), CRUD/FLS enforcement, and other security concerns to ensure it meets Salesforce's security standards.

AppExchange Upgrades refers to the process of updating an installed AppExchange managed package to a newer version. When a publisher releases a new version, subscribers receive a notification and can install the upgrade, which updates the package components while preserving customizations and data. Push upgrades allow publishers to automatically upgrade subscribers' packages.

Apple Messages for Business is a Salesforce Service Cloud messaging channel integration that enables customers to communicate with businesses through the Apple Messages app on iPhone, iPad, and Mac. Agents receive and respond to these conversations within the Salesforce Service Console using Omni-Channel routing, providing a native iMessage-like experience for customer support.

Application Lifecycle Management (ALM) in Salesforce refers to the end-to-end process of managing the development, testing, and deployment of applications on the Salesforce platform. It encompasses planning, development in sandboxes, version control, testing, staging, and releasing changes to production using tools like Change Sets, Salesforce DX, DevOps Center, and CI/CD pipelines.

Application Network is a MuleSoft concept referring to the interconnected web of reusable APIs, integrations, and microservices that an organization builds over time using API-Led Connectivity. Each new API added to the network increases the value of the entire ecosystem, enabling faster development of new digital experiences by composing existing APIs rather than building from scratch.

Application Programming Interface (API) is a set of protocols and tools that allows different software applications to communicate with each other. In Salesforce, APIs provide programmatic access to org data and functionality. Salesforce offers multiple APIs including REST API, SOAP API, Bulk API, Streaming API, Metadata API, and Tooling API, each designed for different integration patterns and use cases.

Application Test Execution is a Setup page for running and managing test suites that validate the functionality of Salesforce applications. It allows administrators to execute predefined test cases, monitor test progress in real time, and view results to ensure that customizations and configurations work as expected.

Application Test History is a Setup page that maintains a historical record of all application test executions in the org. It displays past test runs with their dates, pass/fail results, duration, and the user who initiated each run, enabling teams to track testing trends over time.

Appointment Scheduling in Salesforce (also known as Lightning Scheduler) is a feature that allows organizations to manage the scheduling of appointments between customers and service resources. It provides tools for defining service territories, available time slots, work types, and service resources, and includes self-service scheduling capabilities for customers through Experience Cloud sites.

An Approval Action in Salesforce is an automated action that executes at a specific point in an Approval Process. Approval Actions can include field updates, email alerts, outbound messages, and tasks. They are configured to fire at different stages: upon initial submission, upon final approval, upon final rejection, or upon recall of the approval request.

An Approval Process in Salesforce is an automated process that an organization uses to approve records. It specifies the sequence of steps required for a record to be approved, including who must approve it at each step, the actions to take when a record is submitted, approved, rejected, or recalled, and the entry criteria that determine which records enter the process.

An Approval Process Diagram is a visual representation (flowchart) of an Approval Process displayed in Salesforce Setup. It shows the flow of the approval process including entry criteria, approval steps, approvers at each step, and the approval/rejection paths. The diagram helps administrators understand and troubleshoot the logic of multi-step approval workflows.

An Approval Request is a notification sent to a designated approver when a record is submitted for approval through a Salesforce Approval Process. The request appears in the approver's Items to Approve list, as an email notification, and optionally as a Chatter post, allowing the approver to approve or reject the record.

Approval Steps are the individual stages within a Salesforce Approval Process that define who must approve a record and in what order. Each step specifies criteria for the step to apply, the designated approvers (such as a manager, a specific user, or a queue), and what happens if the step is approved or rejected. Steps execute sequentially.

Approvals in Chatter is a feature that posts approval requests directly to an approver's Chatter feed, allowing them to approve or reject records without leaving the feed. When an approval request is submitted, a Chatter post with Approve and Reject buttons appears in the designated approver's feed, streamlining the approval workflow within the collaboration tool.

An Archived Article in Salesforce Knowledge is a published Knowledge article that has been moved to an archived state. Archived articles are no longer visible to users through search or browsing in the Knowledge base, but they are retained in the system for reference and can be restored to draft or published status if needed.

An Article in Salesforce Knowledge is a document that contains information to help service agents and customers find answers to questions. Articles are created using Knowledge Article Types (or Record Types in Lightning Knowledge), go through a publishing lifecycle (draft, published, archived), and can be made available on internal apps, customer portals, and public Knowledge bases.

Article Manager in Salesforce Knowledge is the interface where Knowledge users create, edit, publish, archive, and manage Knowledge articles. It provides search and filter capabilities for finding articles across all states (draft, published, archived) and allows users with appropriate permissions to perform actions like editing, translating, and assigning articles for review.

Article Publication in Salesforce Knowledge refers to the process of making a Knowledge article available to its intended audiences. When an article is published, it transitions from draft to published status and becomes visible according to its channel settings (Internal App, Customer, Partner, or Public Knowledge Base). Publication can be immediate or scheduled for a future date.

Article Review in Salesforce Knowledge is a workflow step where a draft or updated article is routed to a designated reviewer or approval queue before publication. The review process ensures content accuracy, consistency, and compliance with organizational standards. Reviewers can approve the article for publication, reject it with feedback, or request revisions.

An Article Type in Salesforce Knowledge (Classic Knowledge) is a template that defines the structure and layout of a category of Knowledge articles. Each Article Type has its own set of custom fields, page layouts, and workflow rules. For example, an organization might have Article Types for FAQs, How-To Guides, and Troubleshooting articles, each with different fields and layouts. In Lightning Knowledge, Article Types have been replaced by Record Types on a single Knowledge object.

An Article-Type Layout in Salesforce Knowledge defines the arrangement of fields and sections on a Knowledge article page for a specific Article Type. Administrators configure Article-Type Layouts to control which fields appear when agents or customers view or create articles, similar to how Page Layouts work for standard and custom objects.

An Article-Type Template in Salesforce Knowledge determines the overall visual template used to render articles of a specific Article Type. Salesforce provides several built-in templates (such as Tab, Table of Contents, and Custom) that control how the article's fields and sections are displayed to end users when they view the published article.

An Asset in Salesforce is a standard object that represents a specific product or item that has been purchased by or installed for a customer. Assets are linked to Accounts, Contacts, or both, and track details such as serial number, purchase date, install date, and status. They are commonly used in service and field service scenarios to manage warranties, service contracts, and installed products.

Asset Hierarchy in Salesforce is a parent-child relationship structure that allows assets to be organized in a tree-like hierarchy. A parent Asset can have multiple child Assets, representing complex products or systems made up of subcomponents. For example, a server rack (parent Asset) might contain individual servers (child Assets), enabling organizations to track and service components at any level.

An Asset Relationship in Salesforce is a junction object that defines how two Asset records are connected to each other beyond the standard parent-child hierarchy. It allows organizations to model complex relationships between assets, such as 'is compatible with,' 'is replaced by,' or 'depends on,' with each relationship having a defined type and direction (related asset from and related asset to).

An Assigned Approver in Salesforce is the user designated to approve or reject a record at a specific step in an Approval Process. Assigned approvers can be a specific user, the record owner's manager (via the management hierarchy), a queue, or dynamically determined by a related user field on the record. Each approval step can have one or more assigned approvers.

Assignment in Salesforce refers to the process of assigning ownership of a record (such as a Lead, Case, or Account) to a specific user or queue. Assignment can happen manually, through Assignment Rules (for Leads and Cases), territory rules, or programmatically via Apex and Flow. Proper assignment ensures that records are routed to the right people for timely action.

Asynchronous Calls in Salesforce refer to API calls or code executions that do not block the calling process and return results at a later time. In the context of the AJAX Toolkit, asynchronous calls allow JavaScript to make SOAP API requests without freezing the browser. In Apex, asynchronous processing includes future methods, queueable Apex, batch Apex, and scheduled Apex, which execute outside the main transaction.

The Atlas Reasoning Engine is the AI brain behind Agentforce agents. It is the core reasoning system that takes a user's request, evaluates the available topics and actions, creates a plan, and executes the necessary steps to fulfill the request. Atlas uses chain-of-thought reasoning, retrieval augmented generation (RAG), and CRM data grounding to produce accurate, context-aware responses within the guardrails defined for each agent.

An Attachment in Salesforce is the legacy standard object (Attachment in the API) that stores a single file uploaded to a parent record through the classic Notes & Attachments related list. Each Attachment record contains the file's Name, binary Body (up to 25 MB, base64-encoded), ContentType (MIME type), BodyLength, a polymorphic ParentId pointing to almost any standard or custom record, an OwnerId, an IsPrivate flag, and an optional Description. Attachments are tightly coupled to a single parent - there is no built-in way to share one file across multiple records, and the file disappears if the parent record is deleted. Salesforce Files (ContentDocument and ContentVersion) replaced Attachments as the modern file-storage model, offering multi-record sharing, version history, preview rendering, external sync, and rich permission controls. Salesforce continues to support the Attachment object indefinitely for backward compatibility, but new file uploads through Lightning Experience and most current APIs default to Files instead.

An Audience Channel in Salesforce Marketing Cloud refers to a specific advertising or marketing channel (such as Facebook, Google Ads, Instagram, or email) through which audience segments are activated and targeted. Audience Channels are used within Advertising Studio and other Marketing Cloud tools to push CRM-based audience segments to external advertising platforms for targeted campaigns.

Audit Trail Export Dashboard is a Setup feature that provides a visual overview and export capability for the Setup Audit Trail, which logs the last six months of configuration changes made in the org. It allows administrators to filter, review, and export change history for compliance and troubleshooting purposes.

An Aura Component is a reusable UI building block created using Salesforce's legacy Aura framework. Aura components use a proprietary markup language (.cmp files), JavaScript controllers, and helpers to define interactive interfaces. While still supported, Salesforce recommends Lightning Web Components (LWC) for all new development due to better performance and alignment with modern web standards.

Auth. Providers (Authentication Providers) is a Setup page where administrators configure external identity providers that Salesforce can use for single sign-on (SSO) and social sign-on authentication. Supported providers include Google, Facebook, LinkedIn, Twitter, Apple, Microsoft, and custom OpenID Connect providers. Auth. Providers enable users to log in to Salesforce or Experience Cloud sites using their existing credentials from these external services.

Authorized Email Domains is a Setup page where administrators specify which email domains are approved for use in the org. When configured, only users with email addresses from authorized domains can log in, helping organizations enforce security policies and prevent unauthorized access from personal email accounts.

Auto Number is a custom field type in Salesforce that automatically generates a unique, sequential number for each new record created on an object. Administrators define the display format (such as a prefix and number of digits, like 'CASE-{0000}'), and Salesforce increments the number automatically. Auto Number fields are commonly used for Case numbers, Invoice numbers, and other identifiers that require unique sequential values.

An Auto-Response Rule in Salesforce is a rule that automatically sends a predefined email response when a Lead or Case is created through a web form (Web-to-Lead or Web-to-Case). Administrators define criteria-based entries that match incoming records and associate each entry with an email template. The first matching entry determines which auto-response email the submitter receives.

An Autolaunched Flow in Salesforce is a type of Flow that runs in the background without any user interaction. It does not have screens and is triggered automatically by another process, such as a record change (Record-Triggered Flow), a platform event, a schedule, or an Apex invocation. Autolaunched Flows are used to automate business logic like field updates, record creation, and callouts without requiring user input.

Automated Actions in Salesforce refer to the set of actions that execute automatically as part of workflow rules, processes, or approval processes without user intervention. These include email alerts, field updates, outbound messages, and task creation. Automated Actions fire when their associated rule or process criteria are met.

Automatic Number Identification (ANI) in Salesforce CTI (Computer-Telephony Integration) is the telephony feature that identifies the phone number of an incoming caller. Within Salesforce, ANI data is used to perform screen pops, matching the caller's phone number to existing Contact, Account, or Lead records so the agent sees the caller's information before answering.

Automation App is a Salesforce application that consolidates automation tools and features into a single workspace. It provides quick access to Flows, Process Builder, Approval Processes, and other automation components, allowing administrators to build, manage, and monitor all business automations from one central location.

An Autonomous Agent in Salesforce is an AI-powered Agentforce agent that can independently handle tasks and interact with users without constant human oversight. Autonomous agents use the Atlas Reasoning Engine to understand requests, reason through multi-step processes, and execute actions within defined guardrails. They can operate across channels like chat, email, and Slack, escalating to humans only when needed.

Background Jobs is a Setup page that displays system-initiated background processes running in the org. These include data calculation jobs, sharing rule recalculations, and other platform maintenance tasks that run asynchronously without user intervention.

Basic Data Import is a simplified Setup tool for importing records into standard objects like Accounts, Contacts, and Leads using a CSV file. It provides a guided, wizard-style interface that maps CSV columns to Salesforce fields and handles duplicate checking during the import process.

Batch Apex is an Apex programming pattern that allows developers to process large volumes of records asynchronously by breaking them into manageable chunks (batches) of up to 2,000 records each. A Batch Apex class implements the Database.Batchable interface and defines three methods: start (to collect records), execute (to process each batch), and finish (to perform post-processing). Batch Apex jobs have higher governor limits than synchronous transactions.

A Batch in the Bulk API is a set of records sent in a single request within a Bulk API job. Each job can contain multiple batches, and each batch can hold up to 10,000 records (Bulk API 1.0). Batches are processed asynchronously on the server, and their status (Queued, InProgress, Completed, Failed) can be monitored via the API. The Bulk API is designed for loading or deleting large datasets efficiently.

Best Answer in Salesforce is a designation given to a reply in a Chatter Questions post or Chatter Answers community that the question asker (or a moderator) selects as the most helpful response. The best answer is highlighted and pinned to the top of the replies, making it easy for other users with the same question to find the solution quickly.

Best Case Amount in Salesforce Collaborative Forecasts is a forecast category and associated amount that represents the optimistic revenue estimate. It includes Opportunities in the Best Case forecast category, which are deals that might close but are less certain than committed deals. The Best Case Amount rolls up through the forecast hierarchy to give managers an optimistic view of potential revenue.

A Beta Managed Package in Salesforce is a pre-release version of a managed package that is uploaded to the AppExchange or shared with testers for evaluation before the final release. Beta packages allow ISVs to test their applications in subscriber orgs, gather feedback, and identify issues. Unlike released managed packages, beta managed packages cannot be upgraded and must be uninstalled before installing the final version.

Big Objects is a Setup feature for managing Salesforce Big Objects, which are designed to store and manage massive volumes of data (billions of records) on the Salesforce platform. Unlike standard objects, Big Objects are optimized for large-scale data storage and retrieval using a defined index, making them suitable for historical archiving and audit data.

A Blank Lookup in Salesforce refers to a lookup field that has no value (is null/empty). Blank lookups are commonly referenced in report filters, list views, and SOQL queries to find records that are not associated with a related record. For example, filtering for Contacts where Account equals blank identifies orphaned Contacts not linked to any Account.

Boolean Operators in Salesforce are logical operators (AND, OR, NOT) used to combine multiple search terms or filter criteria. In Salesforce Search, boolean operators refine results (e.g., 'solar AND panel' finds records containing both words). In report filters and SOQL WHERE clauses, they combine conditions. In validation rules and formulas, they perform logical evaluations that return TRUE or FALSE.

A Bot Action in Salesforce Einstein Bots is a specific operation that a chatbot performs during a conversation. Bot Actions include things like sending a message to the user, asking a question, setting a variable, calling an Apex class, invoking a Flow, querying Salesforce records, transferring to an agent, or making an API callout. Actions are the building blocks of bot dialog steps.

Bot Builder in Salesforce is the visual, drag-and-drop interface used to design and configure Einstein Bot conversations. It allows administrators to create dialogs (conversation flows), define intents, map entities, configure actions, set up variables, and design the conversational logic that determines how the bot responds to customer inputs across messaging channels.

A Bot Dialog in Salesforce Einstein Bots is a defined conversation flow within the bot that handles a specific topic or intent. Each dialog consists of a sequence of dialog steps (such as messages, questions, actions, and rules) that guide the conversation. Dialogs can call other dialogs, enabling modular conversation design. For example, a bot might have separate dialogs for 'Check Order Status,' 'Reset Password,' and 'Transfer to Agent.'

Bot Performance in Salesforce is a dashboard and reporting feature that provides analytics on how Einstein Bots are performing. It displays metrics such as total sessions, resolution rate, average session duration, transfer-to-agent rate, most-used dialogs, and customer satisfaction scores. These insights help administrators identify bottlenecks, improve dialog flows, and measure the bot's impact on case deflection.

A Bot Version in Salesforce Einstein Bots represents a specific iteration of a bot's configuration. Each time changes are made to a bot's dialogs, settings, or actions, they are saved as part of the current version. Administrators can activate a version to make it live, deactivate it, or create new versions while preserving previous configurations. Only one version of a bot can be active at a time.

Branch Management in Salesforce CRM Analytics (Tableau CRM) refers to the capability of managing different versions or branches of analytics assets such as dataflows, recipes, and dashboards. It allows teams to create development branches, make changes without affecting production analytics, and merge approved changes back, supporting a more controlled development lifecycle for analytics content.

A Briefcase in Salesforce is a set of rules that defines which records are available for offline access in the Salesforce mobile app or Field Service mobile app. Briefcases are created using Briefcase Builder and specify the objects, record filters, and related records that should be downloaded to a mobile device so field workers and mobile users can access critical data without an internet connection.

Briefcase Builder is a Setup tool that allows administrators to define which Salesforce records are available offline in the Salesforce Field Service mobile app. Administrators create briefcase rules that specify which records (filtered by criteria) should be primed for offline access, ensuring field workers have the data they need even without internet connectivity.

Bucketing in Salesforce Reports is a feature that allows users to group report values into custom categories (buckets) without creating a formula field or modifying the data. Users can bucket text, numeric, or picklist values into named groups. For example, bucketing the Industry field to group 'Technology,' 'Software,' and 'Hardware' into a single bucket called 'Tech Sector' for simplified reporting.

Bulk API 2.0 is a simplified, REST-based version of Salesforce's Bulk API designed for loading, querying, and deleting large datasets (millions of records). Unlike the original Bulk API, version 2.0 automatically splits data into batches, manages retries for failed records, and provides a streamlined interface with fewer API calls needed to manage jobs. It supports CSV input/output and is the recommended approach for high-volume data operations.

Bulk Data Load Jobs is a Setup page that displays the status of data loading operations performed using the Bulk API. It shows job details including operation type (insert, update, delete), object name, number of records processed, number of failures, and completion status for each bulk job.

A Business Account in Salesforce is an Account record that represents a company or organization (as opposed to a Person Account, which represents an individual consumer). Business Accounts are the default Account type and serve as the central hub for tracking a company's Contacts, Opportunities, Cases, and other related records. They are used in B2B (business-to-business) scenarios.

Business Hours is a Setup page where administrators define the operating hours for the organization, including specific days and times for each day of the week. Business Hours are used by Case escalation rules, entitlement processes, and milestones to calculate response and resolution times based on when the support team is actually available.

A Calculated Insight in Salesforce Data Cloud is a computed metric or aggregation derived from unified customer profile data. Calculated Insights use SQL-like expressions to create new data points by performing calculations across Data Cloud data model objects, such as computing a customer's lifetime value, average order frequency, or engagement score. These insights can then be used for segmentation, activation, and AI-driven personalization.

A Calendar in Salesforce (Calendar in the API) is a standard object that represents a single calendar - typically a user's personal calendar, a Public Calendar visible to specific groups of users, a Resource Calendar for shared rooms or equipment, or a Holiday Calendar maintained by an admin. Each Calendar record holds a Name, a Type (User, Public, Resource, Holiday), a UserId or other owner reference, and visibility settings governing who can see and book against it. Calendars are containers for Calendar Events and Tasks; they appear as toggleable layers in the Salesforce calendar view, where users can overlay their own Calendar with their team members' Calendars, public Calendars (Office Holidays, Marketing Events), or resource Calendars (Conference Room A, Demo Lab) to coordinate scheduling. Salesforce Calendars integrate with external systems through Einstein Activity Capture and add-on Lightning Sync products that bidirectionally synchronize Events between Salesforce and Microsoft Outlook or Google Calendar.

Calendar Settings is a Setup page where administrators configure how calendars behave across the org. Options include enabling Home Page hover links for events, configuring calendar sharing defaults, controlling whether users can create events on other users' calendars, and setting the default calendar view.

A Call in Salesforce refers to a phone call activity logged as a Task record with the type set to 'Call.' Calls can be logged manually by users or automatically through CTI integrations. The logged call captures details such as the subject, comments, duration, related Contact or Lead, and associated records. Calls appear in the Activity Timeline and Activity History on related records.

A Call Center in Salesforce is a CTI (Computer-Telephony Integration) configuration that connects a third-party phone system to the Salesforce interface. It enables features such as click-to-dial, screen pops (showing caller information), call logging, and call controls (hold, transfer, conference) directly within the Salesforce console, allowing agents to manage phone interactions without leaving Salesforce.

A Callout in Apex is an HTTP or web service request made from Apex code to an external server or API. Apex supports both HTTP callouts (using HttpRequest/HttpResponse classes) and SOAP callouts (using WSDL2Apex-generated classes). Callouts are subject to governor limits (such as a 10-second timeout per callout and a maximum of 100 callouts per transaction) and require the external endpoint to be registered in Remote Site Settings or Named Credentials.

A Campaign in Salesforce is a marketing initiative such as an advertisement, email blast, webinar, conference, or direct mail effort. Campaigns track the cost, expected revenue, and effectiveness of marketing activities by associating Leads and Contacts as Campaign Members with statuses like Sent, Responded, or Attended.

A Campaign Hierarchy in Salesforce is a parent-child structure that organizes related Campaign records into a tree, allowing marketers to group individual campaigns under a broader initiative. Child campaigns roll up their statistics (such as total leads, responses, and costs) to the parent campaign, providing a consolidated view of the overall marketing program's performance.

A Campaign Member in Salesforce is a junction record that links a Lead or Contact to a Campaign, representing that individual's participation in the marketing initiative. Each Campaign Member record has a Status field (such as 'Sent,' 'Responded,' or 'Attended') that tracks the individual's level of engagement with the campaign.

Campaign ROI (Return On Investment) in Salesforce is a calculated field on the Campaign object that measures the financial return of a marketing campaign. It is calculated as: ((Total Value of Won Opportunities - Actual Cost) / Actual Cost) x 100. This metric helps marketers evaluate which campaigns are generating the best return relative to their investment.

Canvas App Previewer is a Setup tool that allows administrators and developers to preview Canvas apps directly within Salesforce. Canvas apps are web applications hosted outside of Salesforce that are displayed within the Salesforce UI using an iframe. The previewer lets users test how these external apps render before deploying them to production.

A Care Plan in Salesforce (primarily in Health Cloud) is a standard object that represents a structured plan of care for a patient or member. It includes goals, tasks, problems, and care team assignments that define the coordinated approach to managing a patient's health. Care Plans help healthcare organizations track treatment progress, coordinate across providers, and ensure patients receive consistent care.

A Care Program in Salesforce (primarily in Health Cloud) is a standard object that represents a structured health or wellness program designed to manage a group of patients or members with similar health needs. Care Programs define enrollment criteria, milestones, and associated care plans, enabling healthcare organizations to manage population health initiatives like chronic disease management or preventive care programs.

A Care Team in Salesforce (primarily in Health Cloud) is a group of individuals (such as doctors, nurses, social workers, and family members) who are collectively responsible for a patient's care. The Care Team is associated with an Account or Care Plan and tracks each member's role, contact information, and relationship to the patient, facilitating coordinated care delivery.

A Cart in Salesforce (WebCart in the API) is a standard Commerce Cloud object that represents an active or abandoned shopping cart for a buyer on a Salesforce Lightning B2B or B2B2C Commerce storefront. Each Cart record holds a Name, an AccountId (the buying organization for B2B, or the buyer Account for B2C), an OwnerId, a Status (Active, Checkout, Pending Order, Processing Order, Closed), BuyerGroupId for entitled price-list resolution, currency, and totals fields including SubtotalAmount, TotalTaxAmount, TotalShippingAmount, and GrandTotalAmount. Carts are the central transaction object in Commerce Cloud - they collect Cart Items as the buyer browses, evaluate pricing through Price Books and entitlements, hold promo and coupon adjustments, and ultimately produce an Order when the buyer checks out. Salesforce Commerce supports multiple concurrent Carts per buyer (B2B buyers managing parallel quote requests, for example) and persists abandoned Carts for marketing-driven re-engagement campaigns.

A Cart Item in Salesforce (CartItem in the API) is a standard Commerce Cloud object that represents a single line in a buyer's shopping Cart on a Lightning B2B or B2B2C Commerce storefront - one Product, a Quantity, and the resolved pricing for that line. Each Cart Item record holds a parent CartId, a Product2Id, the Quantity, the ListPrice (snapshot from the entitled Price Book), the SalesPrice (after promotion and entitlement adjustments), TotalListPrice, TotalAmount, AdjustmentAmount (cumulative discounts), and a Type field distinguishing Product Cart Items from Charge Cart Items (shipping, tax, fees layered onto the Cart). Cart Items are added when a buyer clicks Add to Cart, updated as they change quantities, and ultimately copied into the resulting Order as Order Products when the Cart is checked out. Like all Commerce pricing, Cart Item totals are recalculated server-side through the Pricing Procedure pipeline whenever the Cart contents, buyer entitlements, or active promotions change - making Cart Items the canonical record of what the buyer will pay if they check out right now.

Cascading Style Sheets (CSS) in the Salesforce context refers to the standard web technology used to style and format the visual presentation of Visualforce pages, Lightning components, and Experience Cloud sites. In Lightning Web Components, CSS is scoped to the component using Shadow DOM. Salesforce's Lightning Design System (SLDS) provides a comprehensive CSS framework with pre-built styles optimized for the Salesforce UI.

A Case in Salesforce represents a customer issue, question, or request for support. Cases track the entire lifecycle of a service interaction from creation through resolution, with fields for Status, Priority, Origin, and Subject. They can be created manually, via email-to-case, web-to-case, or by AI agents.

Case Feed in Salesforce is a chronological, activity-stream view on a Case record that displays all interactions and updates related to the case in a single timeline. It shows emails, Chatter posts, call logs, status changes, and other activities in reverse chronological order. Case Feed provides agents with a complete picture of the case history and enables them to take actions (like sending emails or posting updates) directly from the feed.

A Case (Checkout) in Salesforce Commerce refers to a support case that originates from or is related to a checkout transaction in Salesforce Commerce Cloud. It links the customer service issue to the specific order or checkout session, allowing service agents to view transaction details, payment information, and order status alongside the case for faster resolution.

A Category Group for Articles in Salesforce Knowledge is a Data Category Group used to classify and organize Knowledge articles. It provides a hierarchical structure of categories (like Product > Hardware > Laptops) that authors use to tag articles and that users use to browse and filter articles. Multiple category groups can be created to support different classification schemes.

A Category (Ideas) in Salesforce is a classification used to organize Ideas posted in an Ideas community. Categories allow users to browse ideas by topic (such as 'Product Features,' 'Usability,' or 'Integrations') and help administrators manage and prioritize submitted ideas. Categories are defined by administrators for each Ideas community.

A Category in Salesforce Knowledge and Answers refers to a node within a Data Category Group hierarchy. Categories classify and organize Knowledge articles and Answers questions into logical groupings. They support hierarchical structures (parent-child categories) and are used for both navigation (browsing content) and access control (restricting which categories different user groups can see).

A Category (Solutions) in Salesforce is a classification applied to Solution records to organize them by topic. Categories help support agents and customers browse and find relevant solutions more efficiently. Solution Categories can be organized hierarchically and are managed through the Solution Categories Setup page. Note: Solutions is a legacy feature that has largely been replaced by Salesforce Knowledge.

Certificate and Key Management is a Setup page where administrators create, manage, and store digital certificates and key pairs used for secure communications. These certificates are used for SSL/TLS encryption, single sign-on, mutual authentication with external systems, and signing SAML assertions.

A Challenge in Salesforce Trailhead is a hands-on assessment within a Trailhead module that requires the learner to complete a practical task in a Trailhead Playground or Developer org. Unlike quizzes that test knowledge with multiple-choice questions, challenges verify that the learner has actually performed the required configuration or development work by checking their org against specific criteria.

Change Data Capture (CDC) in Salesforce is a Streaming API feature that publishes real-time notifications when records in Salesforce are created, updated, deleted, or undeleted. External systems subscribe to change event channels to receive these notifications, enabling near-real-time data synchronization and event-driven architectures without polling the Salesforce API for changes.

A Change Set is a Salesforce deployment tool used to send customizations and configurations from one org to another, typically from a sandbox to production. Change Sets can include components like custom objects, fields, Apex classes, Flows, page layouts, and profiles. They require a deployment connection between the source and target orgs.

Channel Manager in Salesforce (particularly in Partner Relationship Management) refers to a user or role responsible for managing partner and channel sales relationships. In the context of Salesforce PRM, it includes tools and dashboards that help channel managers recruit partners, manage deal registration, track partner performance, and facilitate co-selling activities.

Chat (now called Messaging for In-App and Web, formerly Live Agent) in Salesforce is a real-time text-based communication channel that allows customers to chat with service agents through a website or mobile app widget. Chat conversations are routed to agents via Omni-Channel, and agents handle them within the Service Console, with access to full customer context and Knowledge articles.

Chat Console in Salesforce (related to the legacy Live Agent feature) is the agent-facing interface where service agents conduct real-time chat conversations with customers. It displays the active chat, customer details, a chat transcript, quick text options, and Knowledge article suggestions. In modern Salesforce, this functionality is embedded within the Service Console.

A Chat Window in Salesforce is the customer-facing widget that appears on a website or mobile app, enabling visitors to initiate a live chat conversation with a service agent. The chat window is configured by administrators with customizable branding, pre-chat forms, and offline messaging options. It connects to the Salesforce org via Embedded Service deployments.

A Chatlet in Salesforce is a compact, mini version of a chat interface component used within the Salesforce Console. Chatlets allow agents to manage aspects of a chat session (such as viewing transfer options, customer details, or canned responses) in small pop-up panels within the console without navigating away from their current workspace.

Chatter Bookmarks in Salesforce is a feature that allows users to save (bookmark) specific Chatter posts or comments for easy reference later. Bookmarked items are collected in a dedicated Bookmarks feed, enabling users to quickly return to important posts, discussions, or updates without scrolling through the full Chatter feed.

A Chatter Favorite in Salesforce is a saved search or topic stream in Chatter that a user has marked as a favorite. By favoriting a feed search or topic, users create quick-access shortcuts in their Chatter sidebar, allowing them to easily monitor specific discussions, keywords, or topics that are important to their work.

Chatter Feed is the central stream of posts, comments, updates, and activities displayed on the Chatter tab, on user profiles, and on individual record pages in Salesforce. The feed shows real-time updates including posts from followed users, record field changes, file shares, mentions, and group discussions, keeping users informed about activity relevant to them.

A Chatter Group is a collaborative space within Salesforce Chatter where a defined set of users can post, share files, and discuss topics together. Groups can be public (anyone can see and join), private (membership is by invitation or request), or unlisted (hidden from search). Groups are commonly used for project teams, departments, or cross-functional initiatives.

Chatter Mobile is the mobile component of Salesforce Chatter accessible through the Salesforce Mobile App. It allows users to view their Chatter feed, post updates, share files, comment, mention colleagues, and receive push notifications for Chatter activity on their mobile devices, enabling collaboration on the go.

Checkout in Salesforce Commerce refers to the process and functionality that allows customers to complete a purchase in a Salesforce Commerce Cloud storefront. It encompasses the cart review, shipping address entry, shipping method selection, payment processing, and order confirmation steps. Checkout can be customized to support various payment methods, tax calculations, and promotional discounts.

A Child Relationship in Salesforce describes the connection from a child object to a parent object in a master-detail or lookup relationship. The child object contains the relationship field that points to the parent. Child relationships are referenced in SOQL subqueries using the relationship name (e.g., querying Contacts as a child relationship of Account). The relationship name is used for building queries, related lists, and cross-object formulas.

A Claim in Salesforce (primarily in Financial Services Cloud and Insurance) is a standard or custom object representing a request from a policyholder for coverage or compensation based on the terms of an insurance policy. Claims track the details of the incident, the policy involved, the claimant, assessments, and the status of the resolution process.

Classic Email Templates is a Setup page for creating and managing email templates in the Salesforce Classic format, including text, HTML with letterhead, custom HTML, and Visualforce templates. While Lightning Email Templates are the newer standard, Classic templates remain available for workflows, approval processes, and legacy integrations.

Classic Letterheads is a Setup page for creating branded letterhead designs that serve as backgrounds for Classic HTML email templates. A letterhead defines the header image, footer content, background color, and border styling that gives emails a consistent, professional appearance aligned with the organization's brand.

A Client App in Salesforce refers to an external application that connects to and interacts with Salesforce through APIs using a Connected App configuration. The client app authenticates via OAuth 2.0 and then uses Salesforce APIs (REST, SOAP, Bulk, etc.) to read or modify data. Examples include mobile apps, desktop applications, and web applications that integrate with Salesforce.

The Clinical Data Model in Salesforce Health Cloud is a pre-built data model designed for healthcare organizations to manage clinical information. It includes standard objects and fields for clinical encounters, conditions, medications, allergies, immunizations, procedures, and observations, aligned with healthcare data standards like HL7 FHIR to enable interoperability with electronic health record (EHR) systems.

Clone in Salesforce is the action of creating a new record that duplicates the field values of an existing record. Users click the Clone button on a record to pre-populate a new record form with the original record's data, which they can then modify before saving. Clone functionality is available on most standard and custom objects and can be configured to include or exclude related records (Deep Clone).

Cloud Computing in the Salesforce context refers to the delivery model where software, platforms, and infrastructure are provided as a service over the internet rather than installed locally. Salesforce pioneered the SaaS (Software as a Service) cloud computing model, hosting all applications and data on its multi-tenant servers so customers access their CRM through a web browser without managing hardware or software installations.

Code Coverage in Salesforce refers to the percentage of Apex code lines that are executed by test methods. Salesforce requires a minimum of 75% overall code coverage across the org for deploying Apex to production, and each trigger must have at least 1% coverage. Code coverage is measured by running Apex test classes and is tracked on the Apex Classes and Apex Test Execution Setup pages.

A Collapsible Section in Salesforce is a section on a page layout that can be expanded or collapsed by the user to show or hide the fields within it. Administrators configure collapsible sections in the Page Layout editor, optionally setting them to be collapsed by default. This helps organize record pages by grouping related fields and reducing visual clutter.

A Combination Chart in Salesforce reports and dashboards is a chart type that displays two or more data series using different chart styles on the same visualization. For example, it can show bar columns for revenue alongside a line for the number of deals closed, using a secondary Y-axis. Combination charts help users compare metrics with different scales on a single component.

A Comment in Salesforce refers to a text note added to a record, such as a Case Comment on a Case record, a Feed Comment on a Chatter post, or a comment on an Idea or Knowledge article. Comments allow users to add context, updates, or additional information to records and collaborate with teammates or customers around specific issues.

A Comment in Chatter is a reply to a Chatter post in the feed. Users can comment on posts to continue a conversation, provide additional information, mention other users with @, attach files, and add links. Comments appear threaded beneath the original post and contribute to the collaborative discussion on records, groups, or user profiles.

Commerce Cloud is Salesforce's e-commerce platform that enables businesses to create seamless shopping experiences across web, mobile, social, and in-store channels. It comes in two flavors: B2C Commerce (formerly Demandware) for consumer-facing storefronts and B2B Commerce for business buyer portals with complex pricing and account hierarchies.

Commerce Cloud Einstein is the AI layer within Salesforce Commerce Cloud that provides personalized shopping experiences using machine learning. It powers features such as predictive product recommendations, personalized search results and sorting, commerce insights (dashboards showing product performance and shopping behavior), and open-time email content personalization, all based on shopper behavioral data.

A Commerce Cloud Storefront is a customer-facing e-commerce website or digital shopping experience built and hosted on Salesforce Commerce Cloud. Storefronts include the product catalog, search, category navigation, product detail pages, shopping cart, checkout, and account management. B2C storefronts serve individual consumers, while B2B storefronts serve business buyers with features like account-based pricing and bulk ordering.

Commit Amount in Salesforce Collaborative Forecasts is the forecast category and associated amount that represents revenue the sales team is confident will close. It includes Opportunities that the forecast owner has committed to delivering. The Commit Amount rolls up through the forecast hierarchy, giving management a reliable baseline for revenue projections.

A Community Application in Salesforce refers to a Salesforce app that is published and made available within an Experience Cloud site (community). It allows external users to interact with specific Salesforce data and functionality through a branded portal, such as a customer support portal with case management or a partner portal with deal registration.

A Community Expert in Salesforce is a recognized member of a Trailblazer Community or Experience Cloud site who demonstrates deep knowledge and actively helps others by answering questions, sharing best practices, and contributing valuable content. In Experience Cloud sites, administrators can designate certain members as experts, giving them a badge and elevated visibility in the community.

Company Information is a Setup page that stores the organization's fundamental details, including company name, address, default locale, default currency, and time zone. It also displays critical org information such as the Organization ID, edition type, API usage, data storage usage, and file storage usage.

A Competitor in Salesforce is a related list entry on an Opportunity record that identifies other companies competing for the same deal. Sales reps add competitors to Opportunities along with their strengths and weaknesses, helping the sales team develop competitive strategies. Competitor data can be reported on to analyze win/loss patterns against specific rivals.

Complaint Management in Salesforce (particularly in Financial Services Cloud and regulated industries) refers to the set of features and processes for tracking, managing, and resolving customer complaints in a compliant manner. It includes complaint intake, categorization, investigation, resolution tracking, regulatory reporting, and audit trails to meet industry compliance requirements.

Compliance BCC Email is a Setup feature that automatically sends a blind carbon copy of every outbound email from Salesforce to a specified compliance email address. This ensures that all customer communications are archived for regulatory compliance, legal discovery, or internal audit purposes.

Compliant Data Sharing is a Setup feature that provides enhanced data sharing controls for organizations in regulated industries. It enables granular, record-level data access rules that comply with regulatory requirements like HIPAA, FINRA, and GDPR, ensuring sensitive data is only accessible to authorized users.

The Component Reference (Visualforce) is the official documentation that lists all available Visualforce components, their attributes, and usage examples. Developers consult this reference to find the correct tags (like <apex:pageBlock>, <apex:inputField>, <apex:dataTable>) and their properties when building Visualforce pages. It is accessible through Salesforce Developer Documentation.

A Composite App in Salesforce refers to an application that combines native Salesforce functionality with external application components, mashups, or services. Composite apps leverage Salesforce data and UI while integrating external web applications, Canvas apps, or APIs to deliver a unified user experience that spans multiple systems within the Salesforce interface.

Computer-Telephony Integration (CTI) in Salesforce is the technology that connects telephone systems to the Salesforce platform, enabling agents to manage phone calls from within the Salesforce interface. CTI provides features such as click-to-dial, screen pops (automatic display of caller information), call logging, call transfer, and conference calling, all integrated into the Service Console or Sales Console using Open CTI or partner CTI adapters.

A Connected App is a framework that allows an external application to integrate with Salesforce using APIs, standard protocols like OAuth 2.0 and SAML, and other authentication mechanisms. Connected Apps define which API permissions are granted, enforce security policies, and control how external systems access Salesforce data.

Connected Apps OAuth Usage is a Setup page that displays usage statistics and details for Connected Apps using OAuth authentication in the org. It shows which connected apps are actively being used, the number of users, token counts, and last access dates, helping administrators monitor third-party application access.

A Connected User in Salesforce refers to a user whose Salesforce account is linked to an external system or identity provider through a Connected App, OAuth token, or SSO configuration. Connected users have an active authentication session that allows an external application to access Salesforce on their behalf. Administrators can view and manage connected user sessions and revoke access as needed.

Connection (for Salesforce to Salesforce) is a feature that enables two separate Salesforce organizations to share records with each other. Administrators establish a connection between orgs by sending and accepting connection invitations, then configure which objects and fields to publish (share) and subscribe to (receive). This allows partner companies or divisions with separate Salesforce orgs to collaborate on shared Leads, Opportunities, or Cases.

A Console Layout in Salesforce defines the arrangement and configuration of components displayed in the footer panel of a Salesforce Console (Service Console or Sales Console in Classic). It determines which interactive components (such as chat, softphone, history, or Knowledge sidebar) are available as mini-views in the console footer, giving agents quick access to tools without leaving their current record.

Console Settings is a Setup page where administrators configure behavior and appearance options for the Salesforce Console (both Service Console and Sales Console). Settings include keyboard shortcuts, tab limits, navigation behavior, and whether to show pinned lists or the footer component.

A Console Tab in Salesforce is a tab within the Service Console or Sales Console that represents an open record or workspace. Console tabs allow agents to work on multiple records simultaneously without navigating away. There are two types: Primary Tabs (main records like Cases or Accounts) and Subtabs (related records opened from a primary tab, displayed as nested tabs beneath it).

A Consult Call in Salesforce Service Cloud Voice is a feature that allows an agent to place a secondary call to another agent, supervisor, or external number to consult about an active customer call. During a consult call, the customer is placed on hold while the agent discusses the issue. The agent can then return to the customer, merge both calls into a conference, or transfer the customer.

A Contact in Salesforce represents an individual person associated with an Account. Contacts store personal details like name, title, phone, and email, and serve as the primary record for tracking communications and relationships with people at your customer or prospect organizations.

A Contact Role in Salesforce defines the part that a Contact plays in relation to a specific record, such as an Account, Opportunity, Case, or Contract. Contact Roles on Opportunities identify stakeholders like 'Decision Maker,' 'Evaluator,' or 'Economic Buyer.' Contact Roles on Accounts identify relationship types like 'Primary Contact' or 'Technical Contact.' They help teams understand who to engage in business processes.

Contact Roles on Opportunities is a Setup page where administrators enable and configure the ability to associate Contacts with Opportunity records and assign them specific roles such as Decision Maker, Evaluator, or Economic Buyer. This feature helps sales teams track the key stakeholders involved in each deal.

Content Delivery in Salesforce is a feature that allows users to share Salesforce CRM Content documents with external recipients by generating a trackable URL. The recipient can view or download the content via the link without needing a Salesforce login. Content deliveries track views, downloads, and last viewed date, providing visibility into how shared content is consumed.

A Content Document in Salesforce (ContentDocument in the API) is the standard parent object in the Salesforce Files framework that represents a single file as users see it - the persistent identifier for "this file" across all its uploaded versions. Each Content Document record holds metadata like Title, FileType (PDF, JPG, Office documents, etc.), FileExtension, ContentSize, ContentModifiedDate, OwnerId, the LatestPublishedVersionId pointing to the current Content Version, and SharingPrivacy controls. Content Document is the user-facing record of what most people simply call a "File" in Salesforce - its child Content Version records hold the actual binary content (one row per uploaded version), and its child Content Document Link records connect the file to the records it has been attached to. Content Document is the modern replacement for the legacy Attachment object, supporting multi-record sharing, version history, in-browser previews, library organization, and external sync through Salesforce Files Connect.

A Content Pack in Salesforce CRM Content is a collection of related documents bundled together for easy sharing. Content Packs allow users to assemble multiple files, documents, and presentations into a single package that can be delivered to prospects or clients via a content delivery link, providing a curated set of materials for a specific purpose like a sales pitch or onboarding kit.

A Content Version in Salesforce (ContentVersion in the API) is the standard child object in the Salesforce Files framework that holds the actual binary content for one specific version of a Content Document. Each Content Version record contains the file's binary data in the VersionData field (stored base64-encoded over the API), along with metadata like Title, FileType, FileExtension, ContentSize, VersionNumber, IsLatest flag, ReasonForChange (free-text explanation of what changed in this version), and a parent ContentDocumentId. When a file is first uploaded, Salesforce creates one Content Version record (the initial version, with VersionNumber = 1 and IsLatest = true) plus its parent Content Document. Subsequent file replacements insert new Content Version records under the same Content Document, each incrementing VersionNumber and flipping IsLatest on the prior version. Apex and API code that uploads files always inserts Content Version (not Content Document) - the platform automatically creates the parent Content Document and the initial Content Document Link to the inserting user.

A Contract in Salesforce is a standard object that represents a written agreement between a company and a customer. Contracts are linked to Accounts and track terms such as start date, end date, status (Draft, In Approval Process, Activated), payment terms, and special conditions. They provide a record of the formal business relationship and can trigger renewal workflows as expiration dates approach.

A Contract Line Item in Salesforce represents an individual product or service included in a Contract. Similar to Opportunity Line Items (which reference Products and Price Books), Contract Line Items detail the specific items covered by a contract, including quantity, unit price, and terms. They are commonly used in Service Cloud for entitlement management and in Revenue Cloud for subscription tracking.

A Contract (Checkout) in Salesforce Commerce refers to a contract or subscription agreement created as part of the checkout process in Salesforce Commerce Cloud. It captures the recurring billing terms, subscription period, and product details agreed upon during the purchase, linking the commercial transaction to ongoing contract management within Salesforce.

A Controller Extension in Visualforce is an Apex class that extends the functionality of a Standard Controller or Custom Controller. It allows developers to add custom logic, additional queries, and new actions to a Visualforce page while still leveraging the built-in capabilities of the standard controller (like record retrieval and navigation). Extensions are defined in the page's extensions attribute and take the standard controller as a constructor parameter.

A Controlling Field in Salesforce is a standard or custom field whose value determines the available options in a Dependent Field (picklist). When the controlling field's value changes, the dependent picklist dynamically filters to show only the valid subset of values. Controlling fields can be either checkbox or picklist field types. For example, a 'Country' picklist field can control a 'State' dependent picklist.

Conversation Designer in Salesforce is a tool for designing and building conversational AI experiences, particularly for Einstein Bots. It provides a visual interface where administrators and designers map out conversation flows, define intents and dialog paths, configure natural language understanding (NLU) models, and design the end-to-end customer interaction experience across messaging channels.

Conversation Transcript Export is a Setup feature that allows administrators to export chat and messaging conversation transcripts from Salesforce. This is used for compliance, quality assurance, and training purposes, providing a full record of customer-agent interactions.

Convert in Salesforce refers to the Lead Conversion process, which transforms a qualified Lead record into an Account, Contact, and optionally an Opportunity. During conversion, the Lead's field data is mapped to the corresponding fields on the new records. The original Lead record is marked as Converted and is no longer editable. Lead conversion is a key step in the sales process that moves prospects from the marketing pipeline to the sales pipeline.

A Cookie in Salesforce refers to a small piece of data stored in the user's web browser by Salesforce or by Salesforce-hosted sites (such as Experience Cloud sites or Salesforce Sites). Cookies are used for session management, user authentication, remembering user preferences, and tracking analytics. Salesforce uses both first-party and third-party cookies for functionality and performance monitoring.

CORS (Cross-Origin Resource Sharing) is a Setup page where administrators add trusted origin URLs that are allowed to make JavaScript requests to Salesforce APIs from web pages hosted on external domains. Without a CORS allowlist entry, browsers block cross-origin requests to Salesforce for security reasons.

A Coupon in Salesforce (Coupon in the API) is a standard object used in Loyalty Management and Salesforce Commerce that represents a single redeemable discount code issued to a buyer or loyalty member. Each Coupon record holds a unique CouponCode, a reference to its parent Promotion (which defines the discount mechanics - percentage off, fixed amount, free shipping, BOGO), an issued-to identifier (typically a Loyalty Member or Account), an EffectiveFromDate and EffectiveToDate that bound the validity window, a Status (Issued, Redeemed, Expired, Cancelled), and a UsageCount tracking redemption against the parent Promotion's max-use rules. Coupons differ from Promotions: a Promotion defines the rule (every customer who applies code SAVE10 gets 10% off), while a Coupon represents a single instance of that rule (member 12345 was issued code SAVE10-XYZ123 valid through April 30). This per-instance modeling enables precise tracking of who received which coupon, when it was used, and what its lifetime contribution to revenue and engagement was.

Coverage in Salesforce (particularly in Service Cloud) refers to the entitlement or service level coverage that a customer has for support. It determines whether a customer is eligible for service based on their entitlements, service contracts, and warranty terms. When a Case is created, Salesforce can check the customer's coverage to ensure they are entitled to support and to apply the correct service level milestones.

A Credit Memo in Salesforce (particularly in Salesforce Billing and Revenue Cloud) is a document that records a credit issued to a customer, reducing the amount they owe. Credit Memos are generated when invoiced charges are reversed, such as for refunds, billing errors, or contract modifications. They reference the original invoice and adjust the customer's account balance.

CRM Analytics (formerly Tableau CRM and Einstein Analytics) is Salesforce's native analytics platform that provides AI-powered dashboards, predictions, and data exploration directly within the Salesforce UI. It uses SAQL for querying datasets and offers features like Einstein Discovery for automated insight generation and predictive modeling.

CSV (Comma Separated Values) in Salesforce refers to the plain text file format used for importing and exporting data. CSV files use commas to separate field values and newlines to separate records. Salesforce tools like Data Loader, Data Import Wizard, Bulk API, and report exports all use CSV format. Data must conform to the correct field mappings and character encoding (typically UTF-8) for successful processing.

A CTI Adapter in Salesforce is a software component that serves as the bridge between a third-party telephony system and Salesforce's CTI framework. The adapter translates telephony events (like incoming calls, call transfers, and hang-ups) into Salesforce actions (like screen pops and call logging). CTI adapters are typically provided by telephony vendors and integrate with Salesforce using the Open CTI API.

A CTI Connector in Salesforce is a software integration that connects a specific phone system or telephony provider to the Salesforce platform. It enables features like click-to-dial, inbound screen pops, call recording, and call logging. Connectors are typically built by telephony partners using Open CTI and are installed as managed packages or configured through Setup.

A CTI System (Computer-Telephony Integration System) in Salesforce refers to the complete telephony infrastructure that integrates with Salesforce, including the PBX (Private Branch Exchange) or cloud phone system, the CTI adapter or connector, and the Salesforce Call Center configuration. Together, these components enable agents to manage phone calls directly within the Salesforce interface.

A Custom App in Salesforce is an app created by an administrator that bundles a set of tabs (for standard objects, custom objects, Visualforce pages, Lightning components, and other items) under a single label with a custom logo. Custom Apps are defined in the App Manager and appear in the App Launcher. In Classic, Custom Apps can be Classic apps (with a tab bar) or Console apps (with a multi-tab workspace).

A Custom Console Component in Salesforce is a custom Visualforce page, Lightning component, or Canvas app that administrators add to the sidebar, footer, or highlights panel of a Service Console or Sales Console. These components extend the console with custom functionality such as displaying external data, providing agent tools, or integrating third-party applications within the agent's workspace.

A Custom Controller in Visualforce is an Apex class written entirely from scratch that provides all the data and logic for a Visualforce page, without relying on a Standard Controller. Custom Controllers give developers complete control over page behavior, including custom queries, complex business logic, and custom navigation. The custom controller class is specified in the Visualforce page's controller attribute.

A Custom Field is a field created by an administrator on any standard or custom object to capture data specific to the organization's needs. Salesforce supports many custom field types including text, number, date, picklist, formula, lookup, and more. Custom field API names end with "__c".

Custom Help in Salesforce refers to administrator-defined help text that can be added to custom fields, custom objects, and Visualforce pages to provide context-specific guidance to users. For custom fields, it appears as a tooltip next to the field label. Administrators can also override the default help pages for objects with custom content that is specific to their organization's processes.

Custom Labels in Salesforce are custom text values that can be accessed from Apex code, Visualforce pages, Lightning components, and other platform features. They support translation into multiple languages, making them essential for building multilingual applications. Administrators create Custom Labels in Setup with a name, value, and optional translations, and developers reference them in code using System.Label.labelName.

Custom Links (also called Custom Buttons and Links) in Salesforce are administrator-defined URL links or JavaScript actions that appear on record detail pages, list views, or related lists. Custom Links can navigate to external websites, execute JavaScript (Classic only), open Visualforce pages, or construct URL-based integrations with external systems. They extend the actions available to users on Salesforce records.

A Custom Metadata Type in Salesforce is a framework for creating custom, deployable, and packageable application metadata. Unlike Custom Settings (which store data), Custom Metadata Type records are treated as metadata and can be deployed between environments using Change Sets, packages, and the Metadata API. They are ideal for storing application configuration, mapping tables, and business rules that need to move with the application.

A Custom Notification in Salesforce is an admin-defined notification message that can be sent to specific users through the Salesforce mobile app push channel, the desktop bell icon, or both - triggered programmatically from Flow, Process Builder, Apex, or the REST API. Custom Notifications are configured through the Custom Notification Type standard object (CustomNotificationType in the API), which holds the MasterLabel, CustomNotifTypeName, Description, and channel toggles (Desktop, Mobile). Once a Custom Notification Type is defined, automations reference it by Id when sending notifications, providing a Title, Body, optional Sender Id and TargetId (the record the notification is about), and a list of recipient User Ids. Custom Notifications complement standard Salesforce notifications (case assignments, approval requests, Chatter mentions) by letting admins build domain-specific alerts - "High-value Opportunity at risk", "VIP customer just submitted a Case", "SLA breach imminent" - without writing custom mobile push integration code.

Custom Notifications is a Setup page where administrators create notification types that can be sent to users through Flows, Apex, or REST API. Custom notifications appear in the Salesforce notification bell, as desktop push notifications, and in the Salesforce mobile app, providing a flexible way to alert users about important events.

A Custom Object is a user-defined database table created by administrators or developers to store information specific to their organization that is not covered by Salesforce's Standard Objects. Custom Objects can have custom fields, relationships, page layouts, and security settings just like standard objects, and their API names always end with "__c".

Custom Permissions is a Setup page where administrators create named permissions that can be assigned to users via Permission Sets or Profiles. Custom Permissions act as feature flags that developers and administrators can check in Apex code, validation rules, and Flows to control access to custom functionality without modifying profiles.

A Custom Report Type in Salesforce is an administrator-defined report template that specifies which objects and their relationships are available for reporting. It defines the primary object, related objects (up to four levels), and the fields from each object that report builders can use. Custom Report Types enable reporting on object combinations that are not covered by standard report types.

Custom Settings in Salesforce are a special type of custom object that allows administrators and developers to store reusable configuration data at the organization, profile, or user level. There are two types: List Custom Settings (store a dataset accessible across the org) and Hierarchy Custom Settings (store settings that can be overridden at the profile or user level). Custom Settings data is cached in the application cache, enabling fast access without SOQL queries.

A Custom View (more commonly called a List View) in Salesforce is a filtered, sorted display of records for a particular object. Users create custom views by defining filter criteria, selecting which columns to display, and choosing the visibility (private, shared with groups, or visible to all users). Custom views appear as selectable options in the list view dropdown on object tabs and record home pages.

Customer 360 is Salesforce's product-portfolio and integration vision: one unified customer profile spanning every Salesforce cloud (Sales, Service, Marketing, Commerce, Data Cloud, Agentforce) so every department sees the same data about each customer. The concept is delivered through shared data models (the Customer 360 Data Model), identity resolution in Data Cloud, and cross-cloud integration via Marketing Cloud Connect, Salesforce Connect, and the Einstein 1 Platform. "Customer 360" is both the marketing term Salesforce uses to describe its suite and the technical capability that unifies customer data across the products.

Customer Relationship Management (CRM) is a strategy and technology category for managing all of an organization's relationships and interactions with current and potential customers. In Salesforce's context, CRM refers to the core platform and its functionality for tracking accounts, contacts, opportunities, cases, and activities. Salesforce is the world's leading CRM platform, providing cloud-based tools for sales, service, marketing, and more.

Customer Satisfaction Score (CSAT) in Salesforce Service Cloud is a metric derived from post-interaction surveys that measures how satisfied customers are with the support they received. CSAT surveys can be sent automatically after case closure, and the results are tracked on Case records and displayed in Service Analytics dashboards. The score typically represents the percentage of customers who rated their experience as positive.

Customers (Chatter) in Salesforce refers to external users who are invited to participate in specific Chatter groups without having a full Salesforce license. Chatter Customer users can post, comment, and share files within the groups they are invited to, but they cannot see any Salesforce data or records outside their designated groups. This feature allows controlled collaboration with external stakeholders.

A Dashboard in Salesforce is a visual display of data from multiple reports presented as charts, gauges, tables, and metrics on a single page. Dashboards provide an at-a-glance view of key business data and can be filtered dynamically by the viewing user. Each dashboard component is backed by a source report.

Dashboard Builder in Salesforce is the drag-and-drop editor used to create and modify dashboards. It provides a canvas where users add, arrange, resize, and configure dashboard components (charts, gauges, tables, and metrics), each backed by a source report. Dashboard Builder allows users to set filters, choose chart types, configure component properties, and preview the dashboard before saving.

Dashboard Filters in Salesforce are interactive filter controls added to a dashboard that allow viewers to dynamically filter the data displayed across all dashboard components. Up to five filters can be added per dashboard, and each filter maps to fields in the underlying reports. Users click a filter and select values to instantly refine the dashboard view without editing the source reports.

A Dashboard Widget (also called a Dashboard Component) in Salesforce is an individual visual element within a dashboard that displays data from a specific source report. Widgets can be displayed as bar charts, pie charts, donut charts, line charts, funnel charts, scatter charts, gauges, metrics, or tables. Each widget is configured with a source report, chart type, and display properties.

Data Categories is a Setup area where administrators create hierarchical category groups used to classify Knowledge articles and Questions in Chatter Answers. Data categories enable users to filter and find relevant articles by topic, region, product line, or any other classification scheme defined by the organization.

A Data Category for Articles in Salesforce Knowledge is a specific category within a Data Category Group used to classify and organize Knowledge articles. Authors assign data categories to articles during creation or editing, and end users use these categories to browse or filter articles when searching the Knowledge base. Data categories also control article visibility based on role-based access rules.

Data Classification Download is a Setup feature that exports the data classification metadata for all fields in the org to a CSV file. This includes sensitivity levels, compliance categories, and data owner information assigned to each field, providing a comprehensive inventory for data governance and privacy audits.

Data Classification Settings is a Setup page where administrators enable and configure the data classification framework for the org. This framework allows organizations to tag fields with sensitivity levels (such as Public, Internal, Confidential, Restricted), compliance categories (GDPR, HIPAA, PCI), and data ownership information.

Data Classification Upload is a Setup feature that allows administrators to bulk-update data classification metadata by uploading a CSV file. This enables organizations to classify hundreds of fields at once rather than updating each field individually, streamlining the data governance process.

Data Cloud is Salesforce's hyperscale data platform that ingests, harmonizes, and unifies data from any source into a single customer profile. It connects data from CRM, websites, mobile apps, data warehouses, and third-party systems in near real-time, enabling segmentation, activation, and AI-driven insights across the entire Salesforce ecosystem.

Data Encryption in Salesforce refers to the various encryption mechanisms used to protect sensitive data. Salesforce provides Classic Encryption (a 128-bit AES encrypted custom field type for masking data) and Platform Encryption (part of Salesforce Shield, which encrypts data at rest with 256-bit AES encryption while preserving platform functionality like search, workflow, and validation rules). Data is also encrypted in transit using TLS.

Data Encryption Keys in Salesforce are the cryptographic keys used to encrypt and decrypt data protected by Platform Encryption (Salesforce Shield). Administrators manage these keys through the Key Management Setup page, where they can generate new keys, rotate (archive) existing keys, export keys for backup, and import keys. Each key has a status (Active, Archived, or Destroyed) and different key types exist for different data categories.

Data Export is a Setup feature that allows administrators to perform manual or scheduled exports of all data in the org. The export generates a set of CSV files containing records from all standard and custom objects, which can be downloaded as a ZIP file for backup, compliance, or migration purposes.

Data Import Wizard is a built-in Salesforce Setup tool that provides a guided, step-by-step interface for importing data from CSV files into standard objects like Accounts, Contacts, Leads, and Solutions, as well as custom objects. It includes duplicate checking, field mapping, and the ability to trigger workflow rules and processes during import.

Data Integration Metrics is a Setup page that displays performance and health metrics for data integration rules and processes running in the org. It shows success rates, error counts, processing times, and record volumes for integrations that enrich or synchronize Salesforce data with external sources.

Data Integration Rules is a Setup page where administrators enable and manage rules that automatically enrich Salesforce records with data from external services. Salesforce provides built-in integration rules for geocoding addresses and standardizing address formats using Data.com and other services.

Data Loader is a Salesforce client application used to bulk import, export, update, delete, and upsert data. It supports CSV files and can process up to five million records at a time. Data Loader is available as a desktop application and can be run from the command line for scheduled or automated data operations.

Data Manipulation Language (DML) in Salesforce Apex refers to the set of operations used to insert, update, upsert, delete, undelete, and merge records in the Salesforce database. DML operations can be performed using DML statements (like insert account;) or Database class methods (like Database.insert(account, false)). DML operations are subject to governor limits, including a maximum of 150 DML statements per transaction.

A Data Model Object (DMO) in Salesforce Data Cloud is a standardized data structure within the Data Cloud data model that represents a specific entity such as an Individual, Account, Sales Order, or Engagement Event. DMOs define the schema (fields and relationships) for ingested data and are part of the canonical data model that Data Cloud uses to harmonize data from multiple sources into a unified view.

Data Protection and Privacy is a Setup page that centralizes privacy-related settings and tools for the org. It provides access to data classification, consent management, individual rights portability, and other features that help organizations comply with privacy regulations like GDPR, CCPA, and HIPAA.

Data State in Salesforce refers to the condition or status classification assigned to data within a field as part of the Data Classification framework. Data states include values like 'Active,' 'Archived,' and 'Purged,' indicating the lifecycle stage of the data. This classification helps organizations manage data retention policies and compliance requirements by tracking how data should be handled at each stage.

A Data Stream in Salesforce Data Cloud is an ingestion pipeline that brings data from an external source into Data Cloud. Data Streams define the source system, the data schema (mapping source fields to Data Cloud fields), the refresh schedule (real-time, batch, or incremental), and the target Data Model Object. They are the primary mechanism for connecting external data sources like databases, cloud storage, APIs, and Salesforce orgs to Data Cloud.

Database in Salesforce refers to the underlying relational database that stores all of an organization's data. In Salesforce's multi-tenant architecture, each org's data is stored in a shared database infrastructure but logically isolated from other tenants. Salesforce objects (both standard and custom) correspond to database tables, fields correspond to columns, and records correspond to rows. Data is accessed via SOQL, SOSL, APIs, and the Salesforce user interface.

A Database Table in Salesforce's context refers to the underlying storage structure represented by a Salesforce object. Each standard object (like Account or Contact) and custom object corresponds to a table in Salesforce's relational database. Fields on the object are the table's columns, and individual records are the table's rows. While users interact with objects through the Salesforce UI, developers and architects reference the database table concept when discussing data architecture and SOQL queries.

A Dataflow Step is an individual transformation operation within a CRM Analytics dataflow that processes data from one or more source datasets. Each step performs a specific function such as filtering, joining, aggregating, or calculating values, and the output feeds into subsequent steps to build the final analytical dataset.

Dataloader.io is a cloud-based data loading tool accessible from Setup that enables administrators to import, export, update, and delete Salesforce records without installing desktop software. It provides a web interface for CSV-based data operations, scheduled jobs, and direct integrations with cloud storage services like Dropbox and Google Drive.

DataRaptor is an OmniStudio tool for reading, transforming, and writing Salesforce data in real time - a lightweight, configurable data integration layer that extracts from objects, applies transformations, and persists changes back without custom Apex. Starting with Summer '24, Salesforce is renaming DataRaptors to OmniStudio Data Mapper (Data Mapper Extract, Transform, Load, and Turbo Extract); the old and new names refer to the same capability.

Dataset Builder is a CRM Analytics tool that allows users to create datasets directly from Salesforce objects and other data sources through a visual interface. It enables non-technical business users to build analytics datasets by selecting objects, fields, and join relationships without writing code.

DataWeave Resources is a Setup page for managing DataWeave scripts, which are used for data transformation within Salesforce. DataWeave is a programming language for querying and transforming data available in Mule applications and Salesforce, allowing developers to convert data between formats like JSON, XML, and CSV.

A Date Literal is a keyword in SOQL that represents relative dates dynamically, such as TODAY, YESTERDAY, LAST_WEEK, THIS_QUARTER, LAST_FISCAL_YEAR, or NEXT_N_DAYS:n. Date Literals automatically adjust based on the current date, making queries adaptive without manual date recalculation.

Dated Exchange Rates are currency conversion rates in Salesforce that have effective date ranges, enabling accurate multi-currency reporting for historical transactions. Each exchange rate is associated with a specific date range, allowing organizations to report financials in different currencies using the correct rate that was in effect on the transaction date.

A Debug Log is a detailed record of code execution events in Salesforce, captured when debug logging is enabled for a user or transaction. It traces Apex execution, workflow actions, validation rules, system processes, and API calls, and is accessible through the Developer Console or Setup for troubleshooting performance and logic issues.

Decimal Places is a configuration property on Number and Currency fields that specifies how many digits are allowed after the decimal point (0-18). The setting determines both the precision of stored values and how numbers are displayed in the Salesforce interface and reports.

A Decision Table is a Business Rules Engine table that maps input conditions to output actions in a structured, spreadsheet-like format. Each row represents a rule that defines what should happen when certain conditions are met, allowing non-developers to configure complex conditional logic without code.

Deep Clone Product Settings is a Setup page where administrators configure the behavior of the deep clone feature for Products and related records. It controls which child records are included when a Product is cloned, such as price book entries, product features, and related configurations.

Delegated Administration allows non-admin users to perform a limited set of administrative functions for specific groups or organizational units without granting full system admin access. Delegated admins can manage users, reset passwords, and perform other tasks for their assigned group while respecting security and governance boundaries.

A Delegated Approver is a user who has been designated to approve or reject approval requests on behalf of another user who is away or unavailable. The delegated approver acts with the same authority as the original approver for a specified period during an absence.

Delegated Authentication is an SSO implementation method where Salesforce delegates login verification to an external web service rather than authenticating users directly. The external service validates credentials and returns a token to Salesforce, allowing integration with non-SAML identity providers.

Delegated Authentication Error History is a Setup page that logs errors from delegated authentication attempts, where Salesforce delegates the authentication process to an external web service. It helps administrators troubleshoot login failures by showing error messages, timestamps, and the usernames that experienced issues.

Delete Attachments Sent as Links is a Setup feature that controls whether file attachments sent as download links in Salesforce emails are automatically deleted after a specified period. This helps organizations manage storage usage and comply with data retention policies by removing temporary file links.

Deliverability is a Setup page that controls the org's email sending settings and access levels. Administrators can configure the access level for sending email (No Access, System Email Only, or All Email), which determines whether users, workflows, and Apex code can send outbound emails from the Salesforce org.

Demote in Salesforce Knowledge refers to reverting a published article back to draft status. This action removes the article from public visibility and allows authors to make revisions before republishing, useful for correcting errors or updating outdated information.

Density Settings is a Setup page where administrators control the default display density for Lightning Experience. Density settings determine the spacing and compactness of the user interface, offering options like "Comfy" (more spacing) and "Compact" (tighter spacing) to suit different user preferences and screen sizes.

A Dependency in Salesforce represents a relationship between metadata components where one component requires another to function properly. Understanding dependencies is critical during deployments and package creation to ensure all required components are included and deployed in the correct order.

A Dependent Field is a picklist whose available values dynamically change based on the value selected in a controlling field on the same record. Dependent fields enforce data consistency by limiting choices to relevant, valid options that correspond to the controlling field selection.

In Salesforce, Deploy refers to the process of moving metadata and code from one org to another - typically from a sandbox, scratch org, or Git-backed developer environment into a higher-environment sandbox or into production. Deployment channels include Change Sets (UI-based, for related sandboxes), Salesforce CLI (sf, the modern unified CLI that replaced sfdx in 2023), the Metadata API via custom tooling, third-party DevOps platforms (Copado, Gearset, Flosum), and - historically - the Ant Migration Tool, which Salesforce retired in Spring '24.

Deployment Manager is a Setup page in Salesforce Classic that displays and manages metadata deployments, showing deployment history, status, and detailed logs. It allows administrators to monitor in-progress deployments and review the outcomes of completed changes.

Deployment Settings is a Setup page where administrators configure which Salesforce orgs are authorized to send or receive change sets. It manages the deployment connections between production and sandbox environments, controlling the flow of metadata changes across the development lifecycle.

Deployment Status is a Setup page that displays the real-time status, progress, and historical records of metadata deployments in a Salesforce org. It shows which components are being deployed, any errors encountered, and final deployment outcomes.

A Deprecated Component is a Salesforce platform feature, API, or component that is no longer recommended for use and may be removed in a future release. Salesforce provides deprecation notices and recommends migration paths to newer, supported alternatives.

Design Center is a visual tool in MuleSoft Anypoint Platform for designing and documenting APIs using RAML (RESTful API Modeling Language) or OpenAPI Specification (OAS). It allows API-first development where contracts are designed before implementation, fostering better API governance.

The Detail section of a record page is the area displaying individual field values for a single record in a formatted layout. In Lightning Experience, the detail section can include multiple sections with visibility rules and dynamic forms for enhanced usability.

Detail View is the page layout in Salesforce that displays all field values, related lists, and activities for a single record. It is the primary interface for viewing and editing record data, customizable through page layouts and available in both Classic and Lightning Experience.

A Dev Hub is a Salesforce org that manages the creation and lifecycle of Scratch Orgs for Salesforce DX development. It serves as the central control point where developers authenticate, create ephemeral testing environments, and manage org metadata and source control.

Developer Console is an in-browser IDE integrated into Salesforce that enables developers to write and test Apex code, execute SOQL and SOSL queries, set breakpoints for debugging, view debug logs, and monitor system resources and performance. It is accessible via Setup or browser extension.

Developer Edition is a free Salesforce org edition designed for individual developers and small teams to build, test, and learn Salesforce without licensing costs. It includes all platform features but is limited to a small number of logins and is not intended for production use.

A Developer Pro Sandbox is a sandbox environment that copies only the organization's metadata (no production data) and provides 1 GB of test data storage, compared to 200 MB in a standard Developer Sandbox. It is useful for development and testing tasks that require more storage space but do not need production data. Developer Pro Sandboxes can be refreshed once per day.

A Developer Sandbox is a sandbox environment that copies only the metadata (configuration) from production with no production data, providing a clean slate for development and testing. It is the smallest and fastest-to-refresh sandbox type, ideal for isolated feature development.

Development as a Service (DaaS) is a MuleSoft Anypoint Platform concept of providing development tools, platforms, and infrastructure as cloud services. It enables organizations to deliver development capabilities to teams without managing underlying infrastructure.

A Development Environment in Salesforce is any org used for building and testing features before production deployment, including sandboxes, scratch orgs, or Developer Edition orgs. These isolated environments allow safe experimentation without affecting production users or data.

DevOps Center is a Salesforce Setup application that brings DevOps best practices to the Salesforce development lifecycle. It provides a point-and-click interface for source control integration, work item tracking, environment management, and change deployment, enabling teams to manage releases without deep knowledge of Git or command-line tools.

Dial-Tone Multi-Frequency (DTMF) is a telecommunications standard for touch-tone signals generated by telephone keypresses (0-9, *, #). DTMF is used in IVR (Interactive Voice Response) systems to enable callers to navigate menus and provide input without speaking.

Dialed Number Identification Service (DNIS) is a telephony feature that identifies which phone number a caller dialed to reach an organization. DNIS allows contact centers to route calls to appropriate queues, teams, or departments based on the number dialed.

A Digital Experience in Salesforce is a self-service portal or community site built with Experience Cloud that provides external users (customers, partners, employees) secure access to relevant information, support, and transactions. It can include knowledge bases, case creation, account portals, and more.

Digital Process Automation is Salesforce's comprehensive term for the suite of automation capabilities including Flow, Process Builder, Workflow Rules, and Approval Processes. It encompasses tools for automating business logic, approvals, and user interactions to reduce manual work.

Direct Inward Dial (DID) is a telephony feature that allows callers to reach a specific extension or department directly without passing through a switchboard or main reception. DIDs map phone numbers directly to individuals or teams in a contact center.

A Directory Number (DN) is a unique phone number or extension assigned to a telephone line, device, or user in a CTI (Computer Telephony Integration) system. DNs identify the physical or virtual location for incoming and outgoing calls in a telecommunications network.

Discovery Framework Sample Templates is a Setup area providing pre-built templates for the Salesforce Discovery Framework, which is used to create guided assessment forms and questionnaires. These templates help organizations quickly implement discovery processes for sales qualification, needs assessments, and customer onboarding.

Dispatcher Console is the Field Service Lightning interface that enables dispatchers to view, create, assign, and track work orders and field service resources. It provides real-time visibility into technician locations, workload, availability, and job status.

DKIM Keys is a Setup page where administrators create and manage DomainKeys Identified Mail (DKIM) signing keys. DKIM adds a digital signature to outbound emails from Salesforce, verifying to recipients' email servers that the messages genuinely originated from the organization's domain and have not been tampered with in transit.

A Document in Salesforce (Document in the API) is a legacy standard object that stores static files - typically logos, email letterhead images, brochures, templates, and other reference assets - inside Document Folders, accessible through the Documents tab in Salesforce Classic. Each Document record holds a Name, a Body (binary blob), a ContentType, a BodyLength, an Url field for external references, an IsPublic flag, an IsBodySearchable flag, a Keywords field for search, and a FolderId pointing to its parent folder. Documents predate both Attachments and Salesforce Files (ContentDocument) and were the original way to store reusable assets that aren't tied to a single record. Their primary remaining use cases in modern orgs are email template imagery, letterheads, and public-facing static assets that need stable URLs (the IsPublicly Accessible flag generates a permanent unauthenticated URL - useful for embedding logos in HTML emails sent to customers without Salesforce logins). For new file storage, Salesforce strongly recommends Files (ContentDocument) instead.

A Document Library is a folder in Salesforce's Documents tab or CRM Content section used for storing, organizing, and managing files such as templates, brochures, and reference documents. Documents can be shared internally or embedded in pages and records.

A Donation in Salesforce represents a single contribution from a donor to a nonprofit organization. In the Nonprofit Success Pack (NPSP), Donations are stored on the standard Opportunity object, with Type = "Donation" and configurable Stage values (Prospecting, Pledged, Posted, Paid, Closed Won) reflecting the donation lifecycle. In the modern Nonprofit Cloud, Donations are represented through the standard Gift Transaction object, separating them cleanly from the sales-pipeline Opportunity model. Each Donation captures the donor (linked through Account, Contact, or Account-Soft-Credit), the Amount, the Close Date (gift date), payment method, designation (which fund or program receives the gift), associated Campaign, and any matching gift, in-kind valuation, or attribution details. Donations are the operational unit of nonprofit fundraising - every dollar received maps to a Donation record, providing the queryable financial backbone for revenue reporting, donor stewardship, IRS Form 990 compliance, and grant-funder accountability.

A Draft Article is a Knowledge article in draft status that has not yet been published for end-user access. Authors can save, edit, and preview draft articles before submitting them for review and eventual publication.

A Draft Translation is a translated version of a Knowledge article that is in draft status and has not yet been published. Translators can edit and refine translations before approval and publication to ensure quality and accuracy.

Duplicate Error Logs is a Setup page that records instances where Duplicate Rules blocked or flagged record creation or updates. It provides details about the duplicate rule that fired, the matching records identified, and the action taken (block or alert), helping administrators monitor and fine-tune their duplicate management strategy.

Duplicate Management is the suite of Salesforce features designed to detect and manage duplicate records, including Matching Rules that identify duplicates, Duplicate Rules that define actions (block or alert), and Merge features. It helps maintain data quality by preventing or consolidating duplicate entries.

A Duplicate Rule is a configuration that defines what action to take when a duplicate record is detected based on a Matching Rule. It can block record creation/updates, allow with a warning, or alert specific users without preventing the action, providing flexible duplicate governance.

A DX Project (Salesforce DX Project) is a local directory structure recognized by Salesforce CLI ("sf", historically "sfdx" before the 2023 unification) as the container for Salesforce source code and configuration. A DX Project is defined by a sfdx-project.json manifest at its root that declares package directories, source API version, and default org; developers work with metadata as files inside the project, version-control them in Git, and deploy or retrieve via the CLI rather than the Salesforce UI.

A Dynamic Dashboard is a Salesforce dashboard configured to display data filtered according to the running user's security settings and field-level permissions. Each user sees only the data they have access to, eliminating the need for multiple dashboard versions for different user roles.

Dynamic Forms is a Lightning Experience feature that allows fields and form sections to be placed individually as components on record pages with visibility and read-only rules applied. Unlike traditional page layouts, Dynamic Forms enable conditional visibility at the component level for enhanced user experience.

Dynamic Visualforce Binding uses dynamic references such as {!$ObjectType.Account.fields[fieldName]} to build generic Visualforce pages that adapt to different objects without hardcoding field names. This technique enables developers to create reusable, flexible pages that work across multiple objects.

Education Cloud is Salesforce's product suite designed for educational institutions, including K-12 schools, colleges, and universities. It combines the Education Data Architecture (EDA) data model with tools for recruiting, admissions, student success, advancement, and alumni engagement, all built natively on the Salesforce platform.

Education Data Architecture (EDA) is an open-source data model and managed package developed by Salesforce for higher education institutions. It provides a pre-built schema with standard objects such as Program Enrollment, Course, and Faculty that aligns with academic and enrollment management needs.

Einstein is Salesforce's comprehensive artificial intelligence technology layer embedded across the entire platform. It encompasses a suite of AI capabilities - including machine learning, natural language processing, predictive analytics, and generative AI - that help users make smarter decisions, automate routine tasks, and uncover actionable insights from their data without requiring data science expertise.

Einstein Activity Capture is an AI-powered feature that automatically captures and syncs emails and calendar events from email clients (Outlook, Gmail) into Salesforce without manual logging. It enriches Salesforce records with relationship intelligence and activity history in real-time.

Einstein Article Recommendations is an AI feature that automatically suggests relevant Knowledge articles to support agents and customers based on case content, keywords, and historical patterns. It surfaces articles likely to resolve the case, improving resolution time and customer satisfaction.

Einstein Autofill Setup is a Setup page where administrators configure Einstein's ability to automatically fill in field values on records based on AI predictions and data from related records. It uses machine learning to suggest or auto-populate fields, reducing manual data entry and improving data quality.

Einstein Automate is Salesforce's comprehensive automation suite that integrates Flow, MuleSoft Composer for integration automation, and Einstein Bots for conversational AI. It provides a unified platform for automating business processes, integrations, and customer interactions.

AI-powered chatbot in Salesforce Service Cloud that handles routine customer inquiries through automated conversations, using NLP to understand customer intent and provide answers or route to agents.

Einstein Case Classification is a Service Cloud AI feature that automatically predicts and populates picklist fields on incoming Cases - Type, Reason, Priority, Sub-Type - based on patterns learned from your org's historical case data. Admins pick the fields to auto-classify, Salesforce trains a model on the historical Cases that have those fields already set, and once deployed the model predicts values on new Cases so routing and reporting downstream run against clean, consistent data.

An AI-powered feature in Service Cloud that automatically routes incoming cases to the right agent or queue based on case attributes, agent skills, and historical routing patterns.

Einstein Case Wrap-Up is a Service Cloud AI feature that suggests field values for agents to apply when closing a Case - Status, Resolution Code, Root Cause, and similar closure fields. It learns from historical closed Cases and the context of the current Case (description, email threads, chat transcript) to recommend the right closure values, reducing manual entry and improving data consistency for downstream reporting.

A Sales Cloud feature that uses AI to analyze recorded sales calls and video meetings, automatically surfacing mentions of competitors, products, pricing, and custom keywords to help managers coach reps.

An AI feature in Sales Cloud that analyzes pipeline deals and predicts which opportunities are likely to close, flags deals that are trending negatively, and surfaces the factors influencing those predictions.

An analytics tool within Tableau CRM (formerly Einstein Analytics) that uses machine learning to automatically find patterns in data, explain why metrics change, predict outcomes, and recommend actions.

A Marketing Cloud feature that uses AI to score contacts based on their likelihood to engage with emails (open, click) or make purchases, helping marketers target the right audience.

A set of Salesforce AI APIs (part of Einstein Platform Services) that provide natural language processing capabilities including sentiment analysis and intent classification for text data.

An AI feature in Sales Cloud that automatically scores leads based on their likelihood to convert, analyzing historical lead data and conversion patterns to help sales teams prioritize outreach.

A Salesforce AI tool that uses rules-based and predictive models to recommend offers and actions to users at the point of interaction, displayed through a Lightning component on record pages.

An AI feature in Sales Cloud that assigns a score (1-99) to each opportunity based on its likelihood to close, analyzing factors like activity history, stage duration, and related data.

Einstein Platform is a Setup area that provides access to the suite of Salesforce AI capabilities, including Einstein Prediction Builder, Einstein Discovery, Einstein Bots, and other AI-powered features. It serves as the central hub for configuring, managing, and monitoring all AI services available in the org.

An Einstein Prediction is an AI-generated forecast that uses machine learning models trained on your Salesforce data to predict future outcomes. Built through tools like Einstein Prediction Builder, predictions analyze historical patterns in your records to score the likelihood of specific events - such as whether a lead will convert, an opportunity will close, or a customer will churn.

Einstein Prediction Builder is a point-and-click Salesforce tool that lets admins create custom AI predictions on any standard or custom Salesforce object without writing code. An admin picks the field to predict (yes/no or numeric), selects the dataset and filters, chooses the fields to consider as model inputs, and Salesforce trains and deploys the model. Once live, predictions appear as a field value on records and can drive reports, Flows, and list views - useful for business questions like "will this Opportunity close?" or "will this Case escalate?"

Einstein Product Recommendations is a Salesforce Commerce Cloud AI feature that analyzes shopper behavior (page views, searches, purchases, cart activity) and automatically suggests relevant products on storefront pages - product detail pages, category pages, cart, and order confirmation. Recommendations drive cross-sell and upsell without merchandisers hand-curating every relationship, and the model retrains as shopper behavior shifts.

An AI feature that automatically surfaces relevant news, company data, and relationship information from external sources to help sales reps prepare for customer conversations and identify new opportunities.

Einstein Reply Recommendations is a Service Cloud AI feature that suggests pre-written reply text to agents in chat and messaging sessions based on similar past conversations that led to resolution. Admins train the feature on historical chat transcripts; at runtime the agent sees three suggested replies in the chat sidebar and can click to insert (and optionally edit). The feature complements, not replaces, agent judgment - agents still review before sending.

Einstein Sales is a Setup area for configuring AI-powered sales features including Einstein Lead Scoring, Einstein Opportunity Scoring, Einstein Activity Capture, and Einstein Deal Insights. These features use machine learning to analyze sales data and provide predictions and recommendations that help reps prioritize their pipeline.

An AI-enhanced search experience in Salesforce that delivers personalized results by learning from each user's search and click patterns, and surfaces results before the user finishes typing.

Einstein Search Dictionaries is a Salesforce configuration feature that lets admins define synonyms, abbreviations, and equivalent terms so the global search engine (Einstein Search) returns the same results regardless of the exact phrasing users type. For example, mapping "acct" to "Account" or "IBM" to "International Business Machines" means both queries find the same records. Dictionaries are managed per language and apply across the UI search bar, Lightning list-view search, and Experience Cloud search.

A Marketing Cloud feature that uses AI to determine the optimal time to send emails to each individual contact based on their historical engagement patterns, maximizing open rates.

Einstein Setup is a centralized Setup page that provides a guided configuration experience for enabling and managing all Einstein AI features in the org. It displays the status of each Einstein feature, provides setup assistants, and offers recommendations for which AI capabilities would benefit the org based on its data and usage patterns.

Salesforce's security architecture for generative AI that provides data masking, prompt defense, toxicity detection, zero data retention with LLM partners, and audit trails to ensure safe AI usage within CRM.

A set of Salesforce AI APIs (part of Einstein Platform Services) that provide image recognition capabilities including image classification and object detection for building visual AI into apps.

Email Address Internationalization is a Setup feature that enables support for internationalized email addresses containing non-ASCII characters (such as accented letters, Chinese characters, or Cyrillic script) in the local part or domain of an email address. This ensures Salesforce can send and receive emails using international domain names.

A workflow and process automation action in Salesforce that sends an email using a specified email template to designated recipients when triggered by a workflow rule, process, or flow.

A feature in Salesforce approval processes that allows approvers to approve or reject approval requests directly by replying to the email notification rather than logging into Salesforce.

Email Attachments is a Setup page where administrators configure how email attachments are handled in the org, including maximum attachment size limits, whether attachments are stored as Salesforce Files or classic Attachments, and security settings for inbound and outbound email attachments.

Email Delivery Settings is a Setup page that controls how Salesforce delivers outbound emails, including bounce management, email relay configuration, and compliance settings. Administrators can configure email relay to route outbound emails through their organization's email server for additional security scanning and archiving.

Email Footers is a Setup page where administrators create and manage standard footer text that is automatically appended to outbound emails. Email footers typically contain legal disclaimers, unsubscribe links, company contact information, and privacy notices required by email regulations like CAN-SPAM.

An Email Message in Salesforce is a standard object (EmailMessage in the API) that stores the full content and metadata of a single email sent or received within the platform. It captures the subject, plain-text body, HTML body, from and to addresses, CC and BCC recipients, message date, raw headers, attachments, and a status flag indicating whether the message is New, Read, Replied, Sent, Forwarded, or Draft. Email Messages are most commonly created automatically by Email-to-Case (which converts inbound emails into Cases and stores each message as a child record), the Send Email quick action on Cases or other records, and connected mail systems like Salesforce Inbox, Einstein Activity Capture, or third-party email integrations. Each Email Message has a ParentId that links it to a Case, Lead, Contact, Account, or custom object - making it the primary record type for the email conversation history visible in the Lightning Service Console.

An automated email message sent by Salesforce to notify users about system events, record changes, task assignments, approval requests, or other activities configured by administrators.

Email Services is a Setup page where administrators create Apex-based email services that process inbound emails sent to Salesforce-generated email addresses. Each email service is backed by an Apex class that parses the incoming email's subject, body, and attachments to create or update Salesforce records automatically.

A Marketing Cloud application for creating, personalizing, and sending email campaigns at scale, with tools for content creation, A/B testing, dynamic content, subscriber management, and deliverability optimization.

A preformatted email layout in Salesforce that can include merge fields, letterheads, and formatting to standardize outgoing communications sent through workflows, approval processes, or manual actions.

Email to Salesforce is a Setup feature that provides each user with a unique Salesforce email address. When users BCC this address on emails sent from any email client, the email is automatically logged as an activity on the matching Lead, Contact, or Opportunity record in Salesforce, ensuring email communications are captured in the CRM.

A feature that lets companies embed customer service components like chat windows, Knowledge articles, and case management directly into external websites or mobile apps using code snippets.

Embedded Service Deployments is a Setup page where administrators configure and manage chat widgets, messaging channels, and service components that can be embedded on external websites and mobile apps. These deployments bring Salesforce-powered customer service directly to the customer's digital experience.

Enablement Lite Settings is a Setup page for configuring the basic version of Salesforce Enablement, which provides tools for onboarding, training, and coaching sales teams. Administrators can enable features like in-app learning modules, coaching templates, and milestone tracking to help reps ramp up faster.

A Salesforce Shield feature (Platform Encryption) that encrypts data stored in the Salesforce database using AES-256 encryption, protecting sensitive fields, files, and attachments while at rest.

In Salesforce Shield Platform Encryption, a cryptographic key used to encrypt and decrypt protected data, managed through the key management system with options for Salesforce-managed or customer-supplied keys.

The system within Salesforce Shield Platform Encryption for generating, rotating, archiving, and destroying encryption keys, including options for customer-managed keys (Bring Your Own Key).

Encryption Settings is a Setup page where administrators configure Shield Platform Encryption to encrypt sensitive data at rest in the Salesforce database. Administrators can select which fields, files, and attachments to encrypt, manage encryption keys, and control encryption policies across the org.

An upgraded version of Einstein Bots in Salesforce that offers expanded capabilities including more complex dialog management, richer NLP understanding, and integration with Einstein AI features.

Enhanced Email is a Setup feature that stores emails as EmailMessage records related to Cases and other objects, rather than as Task records. This provides richer email functionality including threading, inline images, read receipts, and better integration with the Case Feed and Activity Timeline.

Enhanced Knowledge Settings is a Setup page where administrators configure advanced options for Salesforce Knowledge, including article versioning, approval workflows for article publication, translation settings, and the behavior of Knowledge search within the Service Console.

In Salesforce context, a large-scale application built on the Lightning Platform designed to support complex business processes across an entire organization, often involving multiple integrated objects and automation.

A Salesforce CRM edition designed for larger organizations that includes advanced customization, API access, workflow automation, and more storage than Professional Edition, serving as a mid-to-upper tier offering.

A WSDL (Web Services Description Language) file in Salesforce that is strongly typed and includes all standard and custom objects, fields, and types specific to your org, used for SOAP API integrations.

An Entitlement in Salesforce defines the level of support a customer is eligible to receive, including response times, service hours, and the number of support incidents covered. Entitlements are linked to Accounts, Assets, or Service Contracts and work with Milestones to ensure that service level agreements (SLAs) are met.

A contact record associated with an entitlement in Salesforce Service Cloud, specifying which customers are eligible to receive support under a particular service agreement or contract.

A Service Cloud feature that helps organizations define, enforce, and track customer support agreements (entitlements), including service levels, milestones, and entitlement processes for case management.

A timeline of milestones in Service Cloud that defines the steps (and time limits) your support team must complete to resolve a case or work order under a specific service agreement.

Entitlement Settings is a Setup page where administrators enable and configure the Entitlement Management feature for the org. Settings include enabling entitlements on Cases, choosing whether to track entitlements by Account or Contact, and configuring default entitlement process behavior.

An Entitlement Template is a predefined set of entitlements that can be quickly applied to products to standardize customer support terms. When a product with an entitlement template is added to an asset, the template automatically creates the associated entitlement records, defining support levels, response times, and service commitments without manual entry.

In Salesforce development, a generic term for a data object or record type in the system, such as a standard object (Account, Contact) or custom object, that stores data in the platform's database.

A visual diagram showing the relationships between Salesforce objects (entities), illustrating how standard and custom objects connect through lookup, master-detail, and junction relationships.

An Enumeration Field is a data type primarily used in Apex programming that represents a typed list of values where each value takes on exactly one of a finite set of identifiers. Enum fields are distinct from Picklist fields (which serve a similar purpose in the UI) and are defined in code to enforce strict type safety for a fixed set of constants.

A Salesforce tool that provides a central place to create, view, and manage multiple Salesforce orgs (sandboxes, scratch orgs, developer orgs) from a single login, simplifying multi-org administration.

A developer tool in Salesforce (typically the browser console or Apex debug log) used to view errors, debug information, and system messages when troubleshooting issues in custom code or configurations.

A Salesforce calendar object that represents a scheduled activity with a specific date, time, and duration - such as meetings, calls, or appointments - that can be associated with records like contacts and opportunities.

Event Manager is a Setup page for configuring and managing platform events, change data capture events, and other event-driven integrations in Salesforce. It provides a central view of event channels, subscriptions, and publishing configuration for the org's event-driven architecture.

Event Monitoring Settings is a Setup page where administrators configure Salesforce Shield Event Monitoring, which tracks user activity and system events in the org. Settings include enabling event log file generation, configuring real-time event streaming, and selecting which event types to monitor.

Event Relays is a Setup page where administrators configure the forwarding of Salesforce platform events and change data capture events to external event buses like Amazon EventBridge. Event relays enable real-time data streaming from Salesforce to external systems without building custom polling integrations.

A feature in Salesforce that allows users to create recurring events that repeat on a defined schedule (daily, weekly, monthly), generating a series of linked event records on the calendar.

In Salesforce Computer Telephony Integration (CTI), an event handler that receives and processes telephony events (like incoming calls, hold, transfer) from the phone system and triggers corresponding actions.

Event Studio is a Setup area that provides tools for managing platform events, including event definitions, publishing controls, and subscriber management. It gives administrators visibility into the event-driven messaging system used for real-time integrations and asynchronous processing within Salesforce.

In MuleSoft Anypoint Platform (part of Salesforce), a reusable asset published to Anypoint Exchange such as an API specification, connector, template, or integration pattern that can be shared across teams.

In MuleSoft's API-led connectivity approach (part of the Salesforce ecosystem), an API layer that exposes data tailored to specific user experiences or channels, sitting above process and system APIs.

A drag-and-drop tool in Salesforce for designing and customizing Experience Cloud sites (communities, portals, help centers) with configurable pages, components, themes, and navigation without code.

Experience Cloud (formerly Community Cloud) is a Salesforce product that lets organizations build branded digital experiences such as customer portals, partner portals, help centers, and forums. These sites give external users secure access to relevant Salesforce data and functionality without needing a full Salesforce license.

A branded digital experience (formerly called a Community) built on Salesforce Experience Cloud that provides customers, partners, or employees with a portal for self-service, collaboration, or data access.

Expire All Passwords is a Setup action that forces all users in the org to reset their passwords on their next login. This security measure is typically used after a suspected security breach, a major security policy change, or as part of a routine security audit to ensure all passwords meet current complexity requirements.

External Client App Manager is a Setup page for managing external client applications that connect to Salesforce using OAuth or other authentication methods. It provides controls for registering, configuring, and monitoring third-party client apps that access Salesforce data and APIs.

A Salesforce configuration that defines how to connect to an external system (like SAP, SharePoint, or a custom database) via Salesforce Connect or OData, enabling external objects to display data from outside Salesforce without copying it.

An External Lookup Relationship is a special relationship field type that links a standard, custom, or external object's child records to an External Object's parent records. Unlike a standard lookup, it uses the External ID field of the External Object (rather than the Salesforce record ID) to associate records. This relationship type is essential for connecting Salesforce data to data stored outside the org, accessed in real-time via Salesforce Connect (OData, cross-org adapters, or custom Apex adapters).

An External Object in Salesforce is similar to a custom object, but it maps to data stored outside the Salesforce org rather than inside it. External Objects do not store data in Salesforce; instead, they provide real-time access to external data through Salesforce Connect using OData 2.0, OData 4.0, cross-org, or custom Apex adapter connections. External Object API names end with '__x' and their records are retrieved on-demand from the external system when a user views or queries them. They support a subset of standard Salesforce features, including list views, detail pages, record feeds, and reporting.

A Salesforce feature that lets admins register third-party REST APIs (via OpenAPI specifications) and automatically generate Apex actions from them, making external API calls available in flows without code.

A Salesforce user who accesses the platform through an Experience Cloud site (portal or community), typically a customer, partner, or other non-employee with a limited license such as Customer Community or Partner Community.

In Salesforce, a Facet is a reusable UI building block that injects content into a named region of a parent component. Its most common form is the Visualforce tag <apex:facet>, which places markup inside slots like the header, footer, or caption of data components such as <apex:dataTable>, <apex:pageBlockTable>, or <apex:column>. The term also appears in Experience Cloud, Einstein Search, and Salesforce CMS, where a facet is a filter panel that lets users narrow a list or search result by category, record type, or custom field value.

A Feature License is a per-user flag that unlocks a specific Salesforce feature set (for example Marketing User, Knowledge User, Service Cloud User, Flow User, Mobile User) that is licensed and provisioned separately from the base edition. Admins grant a Feature License on the User record as a checkbox or via a Permission Set License assignment; a user needs both their base User License and the Feature License to access the gated capability.

Feed Attachment, Chatter is a Chatter capability that brings social collaboration into the Salesforce workflow. It allows teams to communicate, share files, and discuss records in context, reducing the need for external communication tools.

In Chatter, a Feed Filter is a built-in option for narrowing the feed to a subset of posts - common filters include All Updates, To Me (posts mentioning the user), Bookmarked, Company Highlights, and Most Recent. Feed Filters appear as selectable chips in the Chatter feed header and let users manage information overload without leaving their feed view.

A Feed Item in Salesforce (FeedItem in the API) is the standard object that stores a single post in any Chatter feed - a user's status update, a record-feed post, a question, an announcement, or a system-generated tracked-change entry. Each Feed Item record holds a Body (the text content), a Type (TextPost, ContentPost, LinkPost, QuestionPost, TrackedChange, etc.), a polymorphic ParentId pointing to whichever record's feed it appears on (a User, Account, Opportunity, Case, Group, or any other Chatter-enabled object), a CreatedById and CreatedDate, an IsRichText flag, and a NetworkScope field controlling community visibility. Feed Items are the central data structure of Chatter: comments live on FeedComment records linked to a Feed Item, reactions and likes live on FeedAttachment, FeedLike, or related junction objects, and Files attached to a post are linked through FeedAttachment. Feed Items also surface as the primary record type for Salesforce's Activity timeline, where every record's Chatter feed mixes user posts with auto-generated tracked-change entries (field updates that admins have enabled for Feed Tracking).

Feed Tracking is a Salesforce Setup feature that controls which field changes on an object create a tracked update entry in the Chatter feed. Admins enable Feed Tracking per object and select up to 20 fields whose changes should post to the feed - for example, enabling tracking on Account.Owner and Account.AnnualRevenue means every owner change or revenue edit appears automatically in the Account's feed and in the feed of anyone who follows that Account.

A Field is a data element on a Salesforce object that stores a specific piece of information about a record, analogous to a column in a database table. Each field has a defined data type (such as text, number, date, picklist, lookup, or formula), an API name for programmatic access, and a user-facing label. Fields can be standard (provided out of the box by Salesforce) or custom (created by administrators, identified by a __c suffix).

Field Accessibility is a Setup page that provides a comprehensive matrix view of field-level security across all profiles and permission sets. It shows whether each field on an object is visible, editable, or hidden for each profile, making it easy to audit and troubleshoot field access issues across the org.

A Field Dependency in Salesforce is a configuration that filters the available values in a dependent picklist based on the value selected in a controlling field. The controlling field can be a standard or custom picklist (or checkbox), and the dependent field is a custom picklist whose options change dynamically. For example, if the controlling field is 'Country' and the dependent field is 'State,' selecting 'United States' would display only US states in the dependent picklist. Field dependencies are configured in the object's field settings under Setup and enforce data consistency without requiring code.

A Salesforce feature that records and displays changes made to specified fields on a record, showing the old value, new value, who made the change, and when, stored in a related history list.

Field Service (formerly Field Service Lightning) is a Salesforce product that extends Service Cloud to manage mobile workforces who perform on-site work. It includes work order management, scheduling optimization, a dispatcher console, a mobile app for technicians, and inventory tracking, enabling organizations to coordinate field operations efficiently.

Field Service Mobile App Builder is a Setup tool for customizing the Salesforce Field Service mobile application used by field technicians. Administrators can configure the app's layout, add custom components, define offline data requirements, and control which features are available to mobile workers.

Field Service Mobile Settings is a Setup page where administrators configure global settings for the Field Service mobile application, including offline data caching, GPS tracking, push notification behavior, and geofencing parameters for automatic status updates when technicians arrive at or depart from service locations.

Field Service Settings is a Setup page where administrators enable and configure Salesforce Field Service features for the org. This includes enabling the Field Service managed package, configuring service territories, scheduling policies, work order settings, and optimization parameters for the dispatch engine.

A grouping of fields in Salesforce that can be referenced dynamically in Visualforce pages, Lightning components, and Apex code, allowing admins to change which fields appear without modifying code.

A Field Update is a workflow action (also available in approval processes) that automatically changes the value of a field on a record when the associated rule's criteria are met. It can set a specific value, use a formula to calculate the new value, or clear the field entirely, and it can optionally trigger re-evaluation of workflow rules after the update. With the retirement of Workflow Rules, equivalent functionality is now available through Record-Triggered Flows.

Field-Level Help is custom help text that administrators can add to any standard or custom field, displayed as a small help icon next to the field label on record detail and edit pages. When users hover over or click the icon, the help text appears, providing guidance on the field's purpose, expected format, or business rules. It supports up to 255 characters of plain text.

Field-Level Security (FLS) is a per-field access control in Salesforce. It determines, per profile or permission set, whether a user can read a specific field's value or edit it. FLS is independent of object permissions and page layouts - a user may have read/edit access to the Account object and still have a specific field like Account.AnnualRevenue hidden or read-only via FLS.

A File in Salesforce is the modern, user-facing name for content stored through the Salesforce Files framework - internally represented by the ContentDocument and ContentVersion objects. Each File is a ContentDocument record that points to one or more ContentVersion records (one per uploaded version), allowing version history, in-place updates, and previews. Files are linked to records through the ContentDocumentLink junction object, which means a single File can be shared with many records, many users, and many groups, each with its own access level (Viewer, Collaborator, or Owner). Files also support libraries (Workspace), folder hierarchies, follow notifications, sharing settings inherited from the parent record, in-browser previews for common formats (PDF, Office, images), external sync via Salesforce Files Connect (SharePoint, Box, Google Drive), and integration into Chatter posts, Email Messages, Cases, Knowledge Articles, and Experience Cloud sites. Files replaced the legacy Attachment object as the recommended way to store any file uploaded into Salesforce.

In Salesforce Files, a File Collaborator is a user who has been granted Collaborator-level access to a file. Collaborators can view, download, and edit the file (including uploading a new version), but cannot delete the file, manage its permissions, or change ownership - those capabilities are reserved for the File Owner. Collaborator is one of three file permission levels, alongside Viewer (read-only) and Owner (full control).

In Salesforce Files, the File Owner is the user who uploaded the file, or to whom ownership has been explicitly transferred. The Owner has full control: edit the file, upload new versions, delete it, share and unshare it, change collaborator roles, and transfer ownership to another user. Only one user can be the Owner at a time; others access the file as Collaborators (edit rights) or Viewers (read/download only).

File Upload and Download Security is a Setup page where administrators control which file types users can upload to Salesforce and how files are downloaded and rendered in the browser. It helps prevent malicious files from being uploaded and ensures secure handling of downloads.

File Viewer is a feature in Salesforce that enables users to preview files and attachments directly within the Salesforce interface without downloading them. It supports common file formats including PDFs, images, Microsoft Office documents, and other file types, rendering them inline on record pages, Chatter feeds, and content libraries.

A File (Private) is a Salesforce concept that combines platform functionality with Private-specific behavior. It is a building block used by developers and administrators to implement business logic and extend the platform.

A File (Privately Shared) is a Salesforce concept that combines platform functionality with Privately Shared-specific behavior. It is a building block used by developers and administrators to implement business logic and extend the platform.

A File (Your Company) is a Salesforce concept that combines platform functionality with Your Company-specific behavior. It is a building block used by developers and administrators to implement business logic and extend the platform.

A tab in Salesforce that provides a centralized view of all files a user has access to, including files they own, files shared with them, files in their libraries, and files attached to records they can view.

Filter Conditions (also called Filter Criteria) in Salesforce are logical expressions used to narrow down which records are displayed, processed, or included in a result set. They consist of three parts: a field name, an operator (such as equals, not equal to, contains, starts with, greater than, less than, or IN), and a value. Filter conditions are used throughout the platform, including in report filters, list views, workflow rules, Flow decision elements, validation rules, SOQL WHERE clauses, and process criteria. Multiple filter conditions can be combined using AND/OR logic.

Filter Email Tracking is a Setup feature that controls how Salesforce tracks email opens and clicks for outbound emails. Administrators can enable or disable tracking, configure which emails include tracking pixels, and filter out automated bot clicks to ensure accurate engagement metrics.

In Salesforce Approval Processes, Final Approval Actions are the actions that execute automatically when an approval process completes successfully - that is, when every required approver has approved the record. Admins configure these actions in Setup: field updates, email alerts, task creation, and outbound messages are the built-in types, and they fire exactly once when the record reaches the final approved state.

Final Rejection Actions are the set of automated actions that Salesforce executes when a record receives its final rejection in an Approval Process. These actions are configured within the Approval Process setup and can include field updates, email alerts, outbound messages, and tasks. They fire only when the record is definitively rejected at the last approval step, ensuring that all necessary follow-up steps (such as resetting a status field or notifying the submitter) happen automatically upon final rejection.

Financial Services Cloud is an industry-specific Salesforce product designed for banks, wealth management firms, insurance companies, and other financial institutions. It includes a financial account data model, client relationship management tools, action plans for compliance processes, and integration with financial planning systems.

Fiscal Year in Salesforce is a Setup configuration that defines the accounting periods used for forecasting, reporting, and quota management. Organizations can choose a Standard Fiscal Year (aligned to calendar months with a configurable start month) or a Custom Fiscal Year with non-standard quarter and period structures. This setting affects how forecast periods, report date filters, and fiscal-based groupings work across the org.

In Salesforce Chatter, an action that allows users to mark a post, comment, or file as inappropriate, notifying community moderators for review and potential content moderation action.

A Salesforce Industries (formerly Vlocity) component that creates dynamic, data-driven UI cards for displaying contextual information from multiple data sources on a single interface without code.

Flow is Salesforce's declarative automation tool that lets administrators and developers build complex business processes using a visual, drag-and-drop interface. Flows can collect user input via screens, create and update records, call Apex code, send emails, and make decisions based on data, all without writing code.

Flow Builder is an interactive Salesforce builder that lets users build, configure, and manage functionality through a structured interface. It reduces the need for manual coding or configuration by providing visual tools and step-by-step workflows.

Flow Creation with Einstein is a Setup feature that enables AI-assisted Flow building, where administrators can describe what they want a Flow to do in natural language and Einstein generates the Flow configuration automatically. This dramatically reduces the time and expertise needed to create complex business automations.

A Flow Interview is a single running instance of a Salesforce Flow. When a Flow is launched - by a user on a screen, a record-triggered Flow, a scheduled Flow, or an invocable call - Salesforce creates an Interview that holds the Flow's current variable state, position, and execution context. Users can pause a screen-based Flow mid-run, which saves the Interview so it can be resumed later; those paused Interviews are visible on the Paused Flow Interviews list and the user's home page.

A Salesforce feature that coordinates multiple flows and user interactions into a single multi-step, multi-user business process, managing steps, stages, and assignments across teams.

A Flow Trigger is the event configuration that determines when and why a flow executes. In Record-Triggered Flows, the trigger specifies the object being monitored and the DML event (record creation, update, or deletion) that causes the flow to run. The trigger also defines whether the flow runs before or after the record is saved, and can include entry conditions that further filter which records activate the flow. It is the initiating condition of the flow, not the actions the flow performs.

In Salesforce, a Folder is an organizational container for Reports, Dashboards, Email Templates, or Documents. Each folder has an access level (Private, Public Read Only, Public Read/Write) and an explicit list of users, roles, groups, or territories granted View, Edit, or Manage access. Folders are how admins and users partition shared content - a report in a folder inherits that folder's sharing, not the user's overall permissions.

Follow is a Chatter feature in Salesforce that allows users to subscribe to updates about records, people, or topics. When you follow an item, relevant changes such as field updates, posts, comments, and activities appear in your Chatter feed. Each user can follow up to 500 combined items (people, records, and topics) by default.

Forecast Amount is the aggregated monetary value displayed in a sales forecast, representing the total expected revenue from opportunities within a given forecast category and time period. It can reflect the raw opportunity amounts or adjusted figures modified by sales reps, managers, or territory owners. Forecast amounts roll up through the role hierarchy to provide visibility at each management level.

Forecast Category is a field on the Opportunity object that classifies deals by their likelihood of closing for forecasting purposes. The standard categories are Pipeline, Best Case, Most Likely (in some configurations), Commit, Omitted, and Closed. Each opportunity stage maps to a forecast category, and these categories determine how opportunity amounts are grouped and displayed in the forecasting module.

In Salesforce Forecasting, the total product quantity projected for a forecast period, available when quantity-based forecasting is enabled alongside or instead of revenue-based forecasting.

A Salesforce user included in the forecasting hierarchy who can submit forecasts, typically a sales rep or manager whose opportunities and adjustments contribute to the forecast rollup.

The Salesforce forecasting module that provides sales teams with projected revenue (or quantity) estimates by period, allowing reps to submit forecasts, managers to adjust rollups, and leaders to track commit vs. pipeline.

Forecasts Hierarchy is a Setup page where administrators define the organizational hierarchy used for sales forecasting. It determines how forecast data rolls up from individual reps through managers to executives, establishing the reporting chain that aggregates forecast amounts at each level.

Forecasts Settings is a Setup page where administrators configure the collaborative forecasting feature, including forecast types, forecast categories, date ranges, adjustment permissions, and which objects and fields drive the forecast calculations. It controls how sales teams predict and track revenue.

A Foreign Key in Salesforce is a field on one object that stores the Record ID of a related record on another object, establishing a relationship between the two objects. For example, the AccountId field on the Contact object is a foreign key that links each Contact to its parent Account. Foreign keys are fundamental to Salesforce's relational data model and are used in lookup relationships, master-detail relationships, and SOQL relationship queries to traverse between related records.

A Formula Field is a read-only field that automatically calculates its value based on a formula expression referencing other fields on the same record or related records. Formula Fields support text, number, date, and checkbox return types, and can use functions like IF, VLOOKUP, TODAY, and TEXT.

A Full Sandbox is a complete copy of a production Salesforce organization, including all metadata, standard and custom object records, attachments, and documents. It has a 29-day refresh interval and is ideal for comprehensive testing scenarios such as performance testing, load testing, and user acceptance testing. Full Sandboxes provide the most realistic testing environment since they mirror the entire production dataset.

Generate Orders is a CPQ (Configure, Price, Quote) and Billing feature that automatically creates Order records from contracted quotes. It converts accepted quotes into orders for fulfillment and billing, streamlining the quote-to-cash process. Visual Workflow templates for generating orders are also available on the AppExchange for customization.

A GET Request is an HTTP method used to retrieve data from a server or API endpoint without modifying it. In Salesforce, GET requests are used when calling the Salesforce REST API to read records, query data, or retrieve metadata. Developers also use GET requests in Apex HTTP callouts (via the HttpRequest class with setMethod('GET')) to fetch data from external services. It is one of the standard HTTP verbs alongside POST, PUT, PATCH, and DELETE.

Getter Methods in Apex are methods that return the value of a class property or variable. They use the get accessor keyword and are commonly used in Visualforce controllers to make data available to Visualforce pages for display. For example, a getter method like public String getName() { return 'Hello'; } allows a Visualforce page to reference {!name} and display the returned value. Getter methods work alongside setter methods to control read and write access to controller properties.

A Global Action (also called a Global Quick Action) in Salesforce is a quick action that is not tied to a specific object. Global actions are accessible from anywhere in Salesforce, including the global actions menu in the Lightning Experience header bar, Chatter publishers, and the Salesforce mobile app. They allow users to create records, log calls, send emails, or launch custom Lightning components and Flows without first navigating to a specific record page. Administrators define global actions in Setup under Global Actions and add them to the Global Publisher Layout.

Global Search is a search feature in Salesforce Lightning Experience and Classic that allows users to search across multiple objects and record types from a unified search box at the top of every page. Results are ranked by relevance and respect object-level permissions, sharing rules, and field-level security. Users can filter results by object type, date range, and other criteria to quickly find the records they need.

In Salesforce formulas, Visualforce, and Lightning components, a system-provided variable (prefixed with $) that gives access to contextual information like $User.Id, $Profile.Name, $Organization.Id, or $Label values.

In Salesforce context, Gmail Integration connects Gmail with Salesforce, allowing users to view Salesforce records, log emails to Salesforce, and create new records directly from the Gmail interface.

Gmail Integration and Sync is a Setup page where administrators configure the integration between Salesforce and Gmail. This includes enabling Lightning for Gmail (which adds a Salesforce sidebar in Gmail), configuring email and calendar synchronization, and managing settings for how emails and events flow between the two platforms.

Salesforce Government Cloud (also known as Government Cloud Plus) is a dedicated Salesforce instance that meets FedRAMP High, DoD IL2/IL4, and other government compliance requirements for U.S. federal, state, and local agencies.

Governor Limits are runtime limits enforced by the Salesforce platform that prevent any single transaction from monopolizing shared resources in the multitenant environment. They restrict the number of SOQL queries (100 per synchronous transaction), DML statements (150), callouts, heap size, CPU time, and other operations to ensure fair resource allocation across all tenants.

In Salesforce fiscal year settings, the standard calendar year (January 1 through December 31) option, as opposed to a custom fiscal year configuration with non-standard periods or start dates.

In Salesforce's AI context (Einstein), the technique of anchoring generative AI responses in your actual CRM data and trusted knowledge sources rather than relying solely on the language model's general training data.

A Salesforce collaboration feature that creates shared spaces in Chatter where members can post updates, share files, and collaborate on topics, available as public, private, or unlisted groups.

A Group Member in Salesforce (GroupMember in the API) is a standard junction object that records a single membership relationship between a Group and either a User or another Group. Each Group Member record holds a GroupId (the parent Group - Public Group, Queue, Chatter Group, or any other system-managed group), a UserOrGroupId (the polymorphic member reference, pointing to either a User or another Group), and standard system fields. Groups in Salesforce are nestable - a Public Group can contain other Public Groups as members, and Group Member captures each level of that nesting one row at a time. Group Member is the underlying data structure behind nearly every group-based Salesforce feature: Public Group sharing rules iterate over Group Members to determine record visibility; Queue assignment routes records to Group Members; Chatter Group membership controls who can post and read; folder-access lists evaluate against Group Members. Every "who is in this Group?" question in Salesforce ultimately resolves to a Group Member SOQL query.

A Salesforce task that is assigned to multiple users simultaneously, creating individual task instances for each assignee so that a team of people can each track their completion of the same activity.

A Salesforce user profile associated with unauthenticated visitors to Experience Cloud sites or Sites.com pages, with highly restricted permissions that control what data and features anonymous visitors can access.

Guest User Sharing Rule Access Report is a Setup feature that generates a security report showing which records are accessible to unauthenticated guest users through sharing rules on Experience Cloud sites. This report helps administrators identify and remediate potential overexposure of sensitive data to anonymous visitors.

Guided Slack Setup is a Setup wizard that walks administrators through the process of connecting their Salesforce org to a Slack workspace. The guided setup covers authorization, channel configuration, notification settings, and enabling Slack-first workflows that allow users to interact with Salesforce data from within Slack.

In Salesforce Einstein (formerly used in Community reputation scoring), a decay parameter that determines how quickly the influence of older activities diminishes over time when calculating engagement or reputation scores.

In Salesforce's AI context (Einstein), when a generative AI model produces a response that sounds plausible but is factually incorrect or fabricated, which the Einstein Trust Layer aims to mitigate through grounding and data validation.

In Salesforce Service Cloud and Einstein Bots, the transfer of a customer conversation from an automated bot or AI agent to a live human agent, typically triggered when the bot cannot resolve the customer's issue.

In Salesforce Shield Platform Encryption, a dedicated tamper-resistant hardware device used to securely generate, store, and manage encryption keys, providing an additional layer of key security for sensitive data.

Health Check is a Setup tool that evaluates the security configuration of the Salesforce org against Salesforce's recommended baseline standards. It assigns a score from 0 to 100 and identifies specific settings that are below recommendations, such as password policies, session settings, and login requirements.

Health Cloud is an industry-specific Salesforce product built for healthcare and life sciences organizations. It provides a patient-centric data model, care plan management, clinical timelines, and provider relationship tools. Health Cloud extends Service Cloud with healthcare-specific features for managing patients, members, and care coordination.

Health Cloud CRM Analytics Settings is a Setup page for configuring analytics dashboards and datasets specific to healthcare organizations using Health Cloud. It enables pre-built healthcare analytics templates for patient population health, care coordination metrics, and clinical outcome tracking.

Health Cloud Setup is a centralized Setup page that guides administrators through enabling and configuring Health Cloud features for healthcare and life sciences organizations. It includes configuration steps for the patient data model, care plan templates, clinical timelines, and provider relationship management.

In Salesforce Health Cloud, an object representing a patient's care plan that defines health goals, problems, tasks, and care team assignments, used to coordinate and track patient treatment across providers.

Heroku is a cloud application platform (PaaS) owned by Salesforce that lets developers build, deploy, and scale applications using popular languages like Node.js, Python, Ruby, Java, and Go. Heroku integrates with Salesforce through Heroku Connect, enabling bidirectional data sync between Heroku Postgres databases and Salesforce objects.

Hierarchy Custom Settings in Salesforce are a type of Custom Setting that uses a built-in hierarchy to personalize application behavior at three levels: organization-wide defaults, profile-level overrides, and individual user-level overrides. When code or a formula accesses a Hierarchy Custom Setting, Salesforce checks for a value at the current user level first, then the user's profile, and finally the org default, returning the most specific match. Hierarchy Custom Settings data is stored in the application cache, which means accessing it does not count against SOQL query limits. They are commonly used for feature flags, thresholds, and per-user configuration values.

A Salesforce license type for Experience Cloud sites that supports large numbers of external users (hundreds of thousands to millions) with limited object access, using a special sharing model based on foreign keys rather than roles.

A Lightning Experience component that appears at the top of a record page displaying key fields and quick actions for the record, giving users immediate visibility into the most important information.

Holidays is a Setup page where administrators define organization-wide or business-hours-specific holiday dates. When a holiday is associated with a Business Hours record, Salesforce excludes that day from entitlement process calculations, case escalation timers, and milestone countdowns, ensuring SLA calculations accurately reflect non-working days.

In Salesforce Environment Hub, the Home Organization is the primary production Salesforce org that a company designates as the central registry for every related Salesforce org - sandboxes, developer orgs, trial orgs, packaging orgs, and partner orgs it connects to the Hub. The Home Org manages user access to the Environment Hub page, issues single sign-on to the connected orgs, and serves as the control point for auditing the org estate. Every Environment Hub has exactly one Home Organization.

The default landing page tab in Salesforce that displays a personalized dashboard of tasks, calendar events, recent records, performance metrics, and assistant notifications for the logged-in user.

A Salesforce feature in Classic UI that displays a popup with key record details when a user hovers their mouse cursor over a record link, allowing quick previews without navigating away from the current page.

A developer tool (like Workbench or browser dev tools) used to inspect HTTP request and response traffic between a client and the Salesforce API, helpful for troubleshooting API integrations and SOAP/REST calls.

Hyperforce is Salesforce's architecture that enables Salesforce products to run on major public cloud infrastructure providers like AWS, Azure, and GCP. It allows organizations to store data in specific geographic regions to meet local data residency requirements while maintaining the same Salesforce functionality, security, and trust standards.

Hyperforce Assistant is a Setup tool that guides administrators through the process of migrating their Salesforce org to Hyperforce, Salesforce's public cloud infrastructure. The assistant provides assessment steps, compatibility checks, and migration planning resources to ensure a smooth transition to the new architecture.

Icons is a Setup feature for managing and customizing the icons used for custom objects, tabs, and applications in the Salesforce user interface. Administrators can choose from the Salesforce icon library or upload custom icons to help users visually distinguish different objects and apps.

In Salesforce, the unique 15-character (case-sensitive) or 18-character (case-insensitive) alphanumeric identifier automatically assigned to every record, used as the primary key for referencing records across the platform.

A Salesforce object (part of the Ideas feature) that represents a suggestion posted by a user in an Ideas community or zone, which other users can vote on and comment on to help organizations crowdsource innovation.

A Salesforce Ideas feature that allows moderators to create focused campaigns or topics inviting community members to submit ideas around a specific theme, helping guide ideation efforts toward business priorities.

Salesforce's public community forum (now called the Trailblazer Community Ideas) where customers submit and vote on product improvement ideas, which Salesforce's product teams review and may implement in future releases.

Identity Provider is a Setup page where administrators configure Salesforce to act as an identity provider (IdP) for single sign-on to other applications. When enabled, users can authenticate once in Salesforce and then access connected third-party applications without entering separate credentials.

Identity Provider Event Log is a Setup page that records all single sign-on events where Salesforce acts as the identity provider. It logs successful and failed authentication attempts, the target service provider, timestamps, and user details, providing an audit trail for SSO-related security monitoring.

In Salesforce Data Cloud (formerly CDP), the process of matching and merging customer data from multiple sources into a single unified customer profile by resolving duplicate records based on matching rules and identity keys.

Identity Verification is a Setup page where administrators configure the methods and policies used to verify user identities during login and high-assurance actions. Options include Salesforce Authenticator, TOTP apps, SMS verification, email verification, and physical security keys.

Identity Verification History is a Setup page that maintains a log of all identity verification attempts in the org, including the verification method used, the result (success or failure), the user involved, and the activity that triggered the verification. This helps administrators monitor MFA compliance and troubleshoot access issues.

Identity Verification Settings is a configuration area in Salesforce Setup where administrators manage the behavior and parameters of a particular platform feature. Adjusting these settings allows organizations to fine-tune how Salesforce operates without writing code.

In Salesforce Process Builder and workflow rules, an action that executes right away when the trigger criteria are met, as opposed to time-dependent actions that are scheduled for a future date.

Import Articles is a Setup feature for bulk-importing Knowledge articles into Salesforce from CSV files. It allows administrators to migrate existing knowledge content from external systems, including article titles, bodies, data categories, and metadata, into the Salesforce Knowledge base.

A built-in Salesforce tool for importing data from CSV files into standard objects (accounts, contacts, leads, solutions, custom objects), supporting up to 50,000 records at a time with duplicate checking.

A Salesforce feature that lets admins create prompts (floating, docked, or targeted) that appear within the Salesforce interface to guide users through processes, announce changes, or provide training without external tools.

In Salesforce Service Cloud and CTI integrations, a phone call received from a customer that is routed to a service agent, typically creating or matching a record and presenting screen pop information.

A change set received by a target Salesforce org from another org (typically from a sandbox to production), containing metadata components like custom objects, fields, and Apex classes ready to be deployed.

An Indirect Lookup Relationship is a relationship type used with Salesforce Connect that links a child external object to a parent standard or custom Salesforce object by matching values in a unique External ID field on the parent, rather than matching on Salesforce Record IDs. This is specifically designed for scenarios where external data does not contain Salesforce record IDs, enabling seamless integration of external data sources.

Industries Cloud Einstein is a Setup area for configuring AI-powered features specific to Salesforce industry solutions such as Health Cloud, Financial Services Cloud, and Manufacturing Cloud. It provides pre-built AI models optimized for industry-specific use cases like patient risk scoring, financial recommendation engines, and demand forecasting.

Influence, Chatter was the Chatter Influence metric - a score displayed on a user's profile that measured their engagement and contribution to Chatter (posts, comments, likes, endorsements, and shares) across the org. Chatter Influence surfaced top contributors and active participants as a community-health signal; Salesforce de-emphasized the feature over time as Chatter evolved, and modern orgs rely more on explicit signals (endorsements, best answers, Experience Cloud reputation points) than on a single overall Influence score.

The automated actions that execute in a Salesforce approval process when a record is first submitted for approval, such as field updates (like changing status to 'Submitted') or email notifications.

In Salesforce Shield Platform Encryption, a random value used with the encryption key during the AES encryption process to ensure that identical data produces different encrypted outputs, enhancing security.

Installed Packages is a Setup page that lists all managed and unmanaged packages installed in the org, along with their version numbers, publisher information, and license details. Administrators use this page to view package details, check for available upgrades, configure package licenses, and uninstall packages.

In Salesforce Field Service and Manufacturing Cloud, a record representing a specific product that has been delivered to and set up at a customer's location, used for tracking service history, warranties, and maintenance.

A specific Salesforce server (identified by names like NA1, EU5, CS42) that hosts a group of Salesforce orgs, determining the login URL and API endpoint for the organizations running on that server.

In Salesforce Financial Services Cloud and Industries, an object representing a customer's insurance policy including coverage details, premium amounts, policy terms, and associated claims.

In Salesforce context, a development tool like Salesforce Extensions for VS Code (formerly Force.com IDE) used to write, test, and deploy Apex code, Lightning components, and other metadata to Salesforce orgs.

Integration Definitions is a Setup page for managing reusable integration configurations that define how Salesforce connects to external systems. These definitions encapsulate connection details, authentication methods, and data mapping rules that can be referenced by multiple integration processes.

A Salesforce Industries (OmniStudio) declarative tool for building server-side integrations that execute multiple data operations (Salesforce queries, API callouts, data transformations) in a single invocable action without code.

In Salesforce development, the process of testing how custom code and configurations interact with external systems, APIs, and other Salesforce components to verify that data flows correctly across integration points.

A dedicated Salesforce user account created specifically for API integrations with external systems, typically assigned an Integration license and configured with the minimum permissions required for the integration's data access needs.

A Salesforce Scheduler feature that uses business rules and customer preferences to offer available time slots, enabling customers and agents to book, reschedule, and manage appointments intelligently.

Intelligent Apps is a Setup area for managing AI-enhanced applications available in the Salesforce ecosystem. It provides access to pre-built intelligent applications that combine CRM data with AI capabilities to deliver context-aware recommendations, predictions, and automated actions across business processes.

A Salesforce Industries feature that uses AI/OCR to extract structured data from scanned documents and forms (like insurance claims or loan applications), automatically mapping the extracted data to Salesforce fields.

Intelligent Sales Settings is a Setup page for configuring AI-driven sales productivity features, including Einstein Activity Capture, automated activity logging, and intelligent deal insights. These settings control how AI enhances the sales workflow by automatically capturing and analyzing sales activities.

An Intent in Salesforce Einstein Bots is a classification that represents the user's purpose or goal behind a message. When a customer sends a message to a bot (such as 'Where is my order?' or 'I need to reset my password'), the bot's Natural Language Understanding (NLU) model analyzes the text and matches it to a trained intent. Each intent is configured with a set of training utterances (example phrases) that teach the model to recognize variations of the same request. Once an intent is identified, the bot routes the conversation to the appropriate dialog to handle that specific topic.

In Salesforce Service Cloud, a utility bar component in the Lightning console that allows agents to quickly log notes, create tasks, and document customer interactions while on a call or chat without leaving the current record.

In Salesforce Service Cloud and telephony integrations, an automated phone system that uses voice menus and keypad input to route callers to the right agent or self-service option before connecting to a live agent.

In Salesforce CTI and Service Cloud Voice, a phone call placed between internal users (agents, supervisors, or other employees) within the organization, as opposed to calls involving external customers.

In Salesforce Flows, a flow interview is a running instance of a flow representing one execution path for a user or automated process. It can be active, paused while waiting for user input, or finished.

A Workforce Engagement feature in Salesforce Service Cloud that monitors real-time agent activity and service metrics throughout the day. It allows supervisors to adjust staffing and schedules in response to demand changes.

In Salesforce Billing or Revenue Cloud, a record representing a bill sent to a customer for products or services. It contains line items, amounts due, payment terms, and status tracking for accounts receivable.

In Salesforce multi-currency settings, the three-letter ISO 4217 currency code (like USD, EUR, GBP) used to identify currencies. It's applied to price books, opportunities, and other financial records in the org.

A Job in Salesforce Bulk API 2.0 is a container that represents a single bulk data operation such as insert, update, upsert, delete, or query. To process large datasets, a developer creates a job specifying the object and operation type, uploads CSV data to the job, and then closes it to signal that all data has been provided. The job then processes asynchronously in the background. Each job transitions through states: Open (accepting data), UploadComplete (data submitted, awaiting processing), InProgress (actively processing), JobComplete (finished successfully), Failed, or Aborted. Results, including successful and failed records, can be retrieved via the job's ID.

In Marketing Cloud Journey Builder, Journey Analytics is the dashboard that shows performance for a specific customer journey - entry volume, exits by decision split, message activity at each step, conversion against the journey's goals, and the contact-level path each subscriber took. Admins use it to evaluate whether a live journey is actually moving the right behavior; builders use it during design iteration to decide which branches to tune.

In Salesforce development, a lightweight data-interchange format widely used in REST API requests and responses. It's also used in Apex JSON class parsing, serialization, and custom metadata storage.

A Junction Object is a custom object with two Master-Detail Relationships that creates a many-to-many relationship between two other objects. It acts as a bridge table, allowing records from one object to be associated with multiple records from another object and vice versa.

In Salesforce Shield Platform Encryption, a cryptographic function that derives encryption keys from a master secret and org-specific data. This ensures each tenant's encryption keys are unique even on shared infrastructure.

Key Management is a Setup page where administrators manage encryption keys used by Shield Platform Encryption, including generating new tenant secrets, rotating keys, archiving old secrets, and configuring key material sources. Proper key management ensures that encrypted data remains secure and recoverable.

In Salesforce security, a set of public and private cryptographic keys used for SSL/TLS certificates, connected app authentication (JWT bearer flow), or API integrations requiring secure communication.

In Salesforce Shield Platform Encryption, the process of generating a new tenant secret to derive new encryption keys. Data is re-encrypted with the new keys while the old secret is archived for backward compatibility.

Knowledge Action is a Setup feature for configuring automatic Knowledge article suggestions and actions within the Service Console. It defines the rules for suggesting relevant articles when agents view Cases, and can automatically attach or insert article content into Case responses.

A Salesforce Service Cloud component (in Classic) that provided agents with a sidebar widget to search, attach, and share Knowledge articles directly from the case record while assisting customers.

A Knowledge Article in Salesforce is the parent record in the Lightning Knowledge data model that holds metadata and version history for a single piece of help content used by service agents and customers. Each Knowledge Article (KnowledgeArticle in the API) acts as a stable, permanent identifier, while the actual content - title, summary, body fields, attachments - lives on related Knowledge Article Version records (KnowledgeArticleVersion). This split lets a single article move through draft, published, and archived states without changing its URL or breaking inbound links from cases, communities, or external systems. Knowledge Articles can be authored in multiple languages (each translation is a separate version chain), categorized through Data Categories, restricted by visibility rules, and exposed across multiple channels: internal agent console, public help sites built with Experience Cloud, the Salesforce mobile app, and chat or bot deflection flows. Lightning Knowledge replaces the legacy Salesforce Classic Knowledge model, which used Article Types instead of Record Types and stored content in many parallel custom objects.

In Salesforce Knowledge, a specific version of an article that tracks its lifecycle states (Draft, Published, Archived). Multiple versions can exist so edits can be drafted without affecting the live published version.

The unified Knowledge interface in Salesforce Lightning Experience and Service Cloud console that lets agents search, view, create, and attach Knowledge articles. It provides a single integrated experience within the case workspace.

Knowledge Settings is a Setup page where administrators enable and configure Salesforce Knowledge for the org. Settings include enabling Lightning Knowledge, configuring article types, setting up languages for multi-language knowledge bases, and controlling how articles appear in search results and customer-facing channels.

A Service Cloud console component in Salesforce Classic that displays suggested Knowledge articles alongside a case record. It automatically surfaces relevant articles based on case fields to help agents find answers quickly.

Language Settings is a Setup page where administrators configure the languages available in the org, including the default language for new users and the set of end-user languages available for selection. Salesforce supports over 30 fully supported languages and additional platform-only languages.

A Large Language Model (LLM) is a deep-learning model trained on massive amounts of text that can understand and generate natural language at scale. In the Salesforce ecosystem, LLMs are the underlying engine powering features like Agentforce agents, Einstein Copilot, and Prompt Builder across Sales, Service, Marketing, and Commerce Cloud. Salesforce exposes LLMs through the Einstein Trust Layer (the privacy and safety architecture formerly marketed alongside the Einstein GPT brand), which supports Salesforce-hosted foundation models as well as bring-your-own-model integrations from providers like OpenAI, Azure OpenAI, Anthropic, Google Vertex AI, and Amazon Bedrock. The Trust Layer adds data masking, prompt grounding, toxicity detection, and audit logging around every LLM call.

In Salesforce, a page layout that defines the arrangement and organization of fields, related lists, buttons, and sections displayed to users when viewing or editing a record. It's configurable per object and profile.

A Lead in Salesforce represents a potential customer who has expressed interest in your product or service but has not yet been qualified. Leads are typically generated from web forms, trade shows, advertising, or purchased lists. Once qualified, a Lead is converted into an Account, Contact, and optionally an Opportunity.

A Lead Assignment Rule in Salesforce is an automated rule that determines which user or queue receives ownership of a new or updated Lead record based on specified criteria. Assignment rules evaluate lead attributes such as geography, industry, lead source, or company size and route each lead to the appropriate sales representative or team to ensure fast and accurate follow-up.

Lead Settings is a Setup page where administrators configure organization-wide behavior for the Lead object, including default lead owner, lead queue settings, lead conversion mapping, and whether to require validation rules during lead conversion.

In Salesforce field configuration, the maximum number of characters or digits allowed in a text or number field. It's set during field creation to control data storage and enforce input constraints.

A feature in Tableau CRM (formerly Einstein Analytics) that provides an interactive interface for visually exploring datasets by adding filters, groupings, and measures. It allows quick data analysis without building a full dashboard.

A Salesforce email template component that defines consistent branding elements (logo, colors, footer) applied across HTML email templates. It ensures outgoing emails maintain a uniform organizational appearance.

In Salesforce CRM Content (now Salesforce Files), a collection of documents organized into a shared repository with controlled access. Teams can manage, version, and share files with specific user groups.

A Library Permission is a named access level assigned to a user's membership in a Salesforce CRM Content library. It controls what that user can do inside that specific library - view content, add content, tag content, archive content, manage the library itself, or any combination. Admins create and name Library Permissions (the same Permission can be applied across multiple libraries), then assign users to libraries with a chosen Permission. A user can hold different Library Permissions across the libraries they are members of.

A free AppExchange app from Salesforce that ISV partners install to track and manage license information for their managed packages. It records installation data and license assignments across subscriber orgs.

The Salesforce org where an ISV partner installs the License Management Application (LMA) to centrally manage, track, and support all customer licenses for their AppExchange packages.

Lightning App Builder is a Setup tool that provides a drag-and-drop interface for creating and customizing Lightning record pages, app pages, and home pages. Administrators can add standard and custom Lightning components, configure their properties, and assign pages to specific apps, record types, and profiles without writing code.

Lightning Bolt Solutions is a Setup area for managing pre-built industry and use-case-specific solution templates for Experience Cloud sites. Each Bolt solution includes pages, components, themes, and flows that can be installed and customized to rapidly launch branded digital experiences like partner portals or customer communities.

Lightning Components is a Setup page that lists all Lightning components (both Aura and Lightning Web Components) available in the org, including those from installed packages. It provides developers with an inventory of reusable UI components that can be placed on Lightning pages, Experience Cloud sites, and flows.

Salesforce's open-source design framework (SLDS) that provides CSS styles, icons, design tokens, and component blueprints. It enables building enterprise applications with a consistent look and feel matching Lightning Experience.

Lightning Email Templates is a Setup page for creating and managing email templates using the Lightning template builder. These templates support rich text formatting, merge fields, drag-and-drop content blocks, and dynamic content, providing a modern alternative to Classic Email Templates.

Lightning Experience Insights is a Setup page that provides analytics about Lightning Experience adoption and usage in the org. It shows metrics like the number of active Lightning users, pages viewed, features used, and switching behavior between Lightning and Classic, helping administrators drive adoption.

Lightning Extension is a Setup feature for managing extensions that enhance Lightning Experience functionality. Extensions can add new capabilities to the Lightning platform, such as additional component types, custom actions, or integrations with third-party services, extending the standard Lightning framework.

A Salesforce integration that embeds a Salesforce panel directly within the Gmail interface, allowing users to view related Salesforce records, log emails, and create new records without leaving Gmail.

A Salesforce integration that embeds a Salesforce panel in Microsoft Outlook, allowing users to view related Salesforce records, log emails and events, and create new records from within Outlook.

The Lightning Experience version of Salesforce Knowledge that uses standard record types and page layouts instead of article types. It streamlines knowledge management with a more modern, flexible architecture.

Lightning Out 2.0 App Manager is a Setup page for managing Lightning Out applications, which allow Lightning components to be embedded in external web pages and applications outside of Salesforce. Administrators configure which Lightning apps are available for external hosting and manage their security settings.

The Lightning Platform (formerly Force.com) is the application development platform that powers all of Salesforce. It provides the infrastructure for building, deploying, and running custom applications with tools like the Lightning App Builder, Apex, Lightning Web Components, and a robust set of APIs. All Salesforce products are built on this platform.

The Salesforce setup area where admins control which apps (standard and custom) appear in the App Launcher for users. Admins manage app visibility based on profiles and mark apps as visible or hidden.

Refers to the suite of point-and-click tools in Salesforce (App Builder, Flow Builder, Schema Builder) that enable admins and developers to build custom applications on the Lightning Platform without extensive code.

A custom application built on the Salesforce Lightning Platform that uses Enterprise Edition features and capabilities. It typically involves complex business logic, multiple objects, and advanced automation.

A simpler custom application on the Salesforce Lightning Platform with fewer tabs and functionality. It's typically used for lightweight use cases that need limited custom objects and basic automation.

Salesforce Scheduler (formerly known as Lightning Scheduler) is a Salesforce feature that enables appointment scheduling within Salesforce, allowing customers and agents to book, modify, and manage appointments. It's based on resource availability, service territories, and business rules.

Lightning Types are JSON-based data types in Salesforce used to structure, validate, and display data for Agentforce agents. Each Lightning Type consists of a schema defining the data structure and validation rules, an optional editor for input UI, and an optional renderer for output UI. Both standard and custom Lightning Types can be managed from Setup by searching 'Lightning Types' in Quick Find.

Lightning Usage is a Setup page that provides detailed analytics about how users interact with Lightning Experience, including daily and monthly active users, page load times, most-visited pages, and browser usage statistics. This data helps administrators optimize the org and track Lightning adoption progress.

The Lightning Web Component (LWC) Framework is Salesforce's modern UI development framework built on web standards including HTML, JavaScript, and CSS. It leverages native browser capabilities and the Web Components standard to create fast, reusable components that run on the Lightning Platform with strong encapsulation and efficient rendering.

In Salesforce Chatter, an action that lets users indicate approval or acknowledgment of a feed post, comment, or file by clicking the Like button. It increments a counter and notifies the author.

List Custom Settings in Salesforce are a type of Custom Setting that stores a flat list of reusable data records, similar to a custom object but with the advantage of being cached in the application cache for fast access without consuming SOQL query limits. Unlike Hierarchy Custom Settings (which return different values based on user, profile, or org), List Custom Settings simply store a collection of records that can be accessed by name. They are commonly used for storing lookup data such as country codes, state abbreviations, default values, or application configuration parameters. List Custom Settings data can be accessed in Apex using the getAll(), getInstance(dataSetName), or getValues(dataSetName) methods.

In Salesforce CPQ and standard Price Books, the default price assigned to a product in the standard price book. It serves as the baseline from which custom price book entries and discounts are calculated.

A filtered, sortable view of records for a Salesforce object that displays selected fields in a table format. It's configured with filter criteria to show specific subsets of records like 'My Open Cases' or 'New This Week.'

In Salesforce internationalization, an alternate name for an account, contact, or lead stored in a local language or script. It's used in regions where records may need to display names in both standard and local formats.

In Salesforce DX, a Local Project is the project directory on a developer's machine that contains the sfdx-project.json configuration file, source-format metadata, and scripts for working with scratch orgs, sandboxes, and production orgs via Salesforce CLI (sf, the unified CLI that replaced the original sfdx in 2023). It is the unit of work for source-driven Salesforce development, version-controlled in Git like any other codebase.

A Salesforce user setting that determines the display format for dates, times, numbers, currency, and names based on geographic conventions (such as en_US for U.S. English or de_DE for German).

The currently authenticated Salesforce user whose session is active, referenced in formulas as $User. Their permissions, profile, and role determine their data access and available features.

Login Access Policies is a Setup page where administrators control whether users can grant Salesforce support or other administrators temporary login access to their accounts. It also controls the maximum duration of login access grants and whether the option appears in users' personal settings.

Login Flows is a Setup feature that allows administrators to associate Flows with the login process, executing custom business logic after a user authenticates but before they access Salesforce. Login Flows can collect additional information, enforce custom security checks, or route users to specific pages based on their profile or IP address.

Login History is a Setup page that displays a log of all login attempts for the org over the past six months, including successful and failed logins. It shows the username, login time, source IP address, login type (UI, API, OAuth), browser, and platform for each attempt.

A Salesforce field type that stores up to 131,072 characters of plain text, used for lengthy descriptions, notes, or other content. It's for text exceeding the 255-character limit of standard text fields.

A popup window in Salesforce that appears when a user clicks the lookup icon on a relationship field. It provides a search interface to find and select a related record by name or other criteria.

A Salesforce field type that creates a relationship between two objects by storing a reference to a record on another object. It's displayed as a clickable link that navigates to the related record.

A filter applied to a Salesforce lookup or master-detail relationship field that restricts which records are available for selection based on specified criteria. It prevents users from choosing invalid related records.

A Lookup Icon is the magnifying-glass icon Salesforce displays next to a lookup field on a record-edit form or inline-edit context. Clicking the icon opens the Lookup Dialog - a search overlay that lets the user browse, search, and select the related record the field should reference. Salesforce renders the icon automatically on any lookup field; admins do not configure it individually.

A Lookup Relationship in Salesforce creates a loose association between two objects, similar to a foreign key in a relational database. Unlike Master-Detail, a Lookup Relationship does not enforce cascading delete, does not support Roll-Up Summary Fields natively, and allows the lookup field to be optional (blank).

In Salesforce context, the approach of building applications and automations using declarative tools (like Flow Builder, App Builder, and validation rules) with minimal or no traditional programming. It makes development accessible to admins.

A Loyalty Member in Salesforce (LoyaltyProgramMember in the API) is the standard object that represents a single customer enrolled in a Salesforce Loyalty Management program. Each Loyalty Member record holds a parent LoyaltyProgramId, a related Account or Contact (depending on whether the program enrolls organizations or individuals), a unique MembershipNumber, an EnrollmentDate, a Status (Active, Cancelled, Suspended), the member's current Tier, current point balances per Loyalty Program Currency, lifetime accrual totals, and references to the most recent qualifying activity that affects tier status. Loyalty Members are the central operational record in any loyalty program - every transaction posted to the program (purchases, partner activity, promotional engagement) updates the member's balances and may trigger tier transitions, benefit grants, and outbound communications. The Loyalty Member's tier is driven by configurable qualification rules (lifetime points versus rolling-window activity) and is recomputed by standard Salesforce batch jobs that run on a configured schedule.

A Loyalty Program in Salesforce (LoyaltyProgram in the API) is the parent standard object in Salesforce Loyalty Management that defines a single rewards program - its name, description, member enrollment process, partner network, transaction-eligibility rules, and the currencies and tier structures that members earn against. Each Loyalty Program is the root of a richly connected data model: Loyalty Program Currency objects define what members earn (points, miles, credits, multiple parallel currencies for the same program), Loyalty Tier Group and Loyalty Tier define the achievement levels (Silver, Gold, Platinum), Loyalty Program Member captures each enrolled customer, Promotion and Benefit objects define what members earn and unlock, and Transaction Journal records the activity that drives accruals and redemptions. Salesforce Loyalty Management uses this model to power consumer airline-and-hotel-style programs, B2B partner programs, healthcare and financial-services rewards, and any other engagement framework where customers earn and redeem value over time.

LWC (Lightning Web Components) is Salesforce's modern web-component framework for building UI in Lightning Experience, Experience Cloud, and mobile apps. Built on standard Web Components specifications (custom elements, shadow DOM, templates, ES modules), LWC replaced the older Aura component model as Salesforce's recommended UI framework - it is lighter, performs better in modern browsers, and lets developers use standard HTML/CSS/JavaScript with Salesforce-specific conveniences like reactive property tracking, wire adapters for data access, and built-in FLS/CRUD enforcement.

Machine Learning (ML) is a branch of artificial intelligence in which algorithms learn patterns from data to make predictions, classifications, or decisions without being explicitly programmed for each scenario. In Salesforce, machine learning powers many Einstein features, including Einstein Lead Scoring (predicting which leads are most likely to convert), Einstein Opportunity Scoring (predicting deal close likelihood), Einstein Prediction Builder (custom predictions on any object), Einstein Discovery (automated pattern detection and recommendations), and Einstein Next Best Action (recommending optimal steps). Salesforce also supports custom ML models through Einstein Model Builder and external model integrations.

In Salesforce Service Cloud, a set of predefined instructions that agents can execute with one click to perform repetitive tasks on a record. Examples include sending an email, updating fields, or posting to Chatter.

A Salesforce feature (primarily in Classic) that generates personalized documents by combining a Word template with Salesforce record data. It's used for creating form letters, envelopes, or labels for contacts and leads.

Mail Merge Templates is a Setup page for managing Word document templates used for mail merge operations in Salesforce. These templates contain merge fields that are replaced with Salesforce data when generating personalized documents such as letters, contracts, and proposals.

In Salesforce Field Service, a record that defines a recurring preventive maintenance schedule for an asset or location. It automatically generates work orders at specified intervals to ensure ongoing service coverage.

One of Salesforce's three annual platform updates (Spring, Summer, Winter) that introduces new features, enhancements, and changes to all customer orgs. It's preceded by preview sandboxes and release notes.

Manage Connected Apps is a Setup page that lists all Connected Apps that have been installed or created in the org, including OAuth settings, session policies, IP restrictions, and user provisioning configurations. Administrators use this page to control which users can access each connected app and under what conditions.

Manage Slack Connection is a Setup page for configuring and maintaining the connection between a Salesforce org and a Slack workspace. It provides controls for authentication, channel mapping, permission settings, and monitoring the health of the integration.

Manage Subscription is a Setup page where administrators view and manage the org's Salesforce subscription details, including license counts, edition information, add-on products, and contract renewal dates. It provides visibility into the organization's Salesforce investment and helps with license planning.

A Managed Package is a collection of Salesforce components (objects, classes, flows, pages, etc.) that is developed and distributed by a third-party ISV or internal team through AppExchange or directly. Managed Packages have their own namespace, support versioning and upgrades, and protect the developer's intellectual property by obfuscating Apex code.

A Salesforce package that depends on and extends the functionality of another managed package. It adds custom objects, code, or configurations that build upon the base package's features.

In Salesforce DX, the package.xml file that lists which metadata components to retrieve from or deploy to a Salesforce org, specifying component types and their members for migration operations.

A Salesforce sharing mechanism that allows record owners (and users with appropriate permissions) to grant access to specific records to other users, roles, or groups beyond what org-wide defaults and sharing rules provide.

A Salesforce industry solution that connects sales and operations teams by providing shared visibility into sales agreements, account-based forecasts, and production plans to align demand planning with CRM data.

A Many-to-Many Relationship in Salesforce allows records from one object to be associated with multiple records from another object and vice versa. It is implemented through a junction object, which is a custom object with two master-detail relationship fields pointing to two different parent objects. The junction object acts as a bridge table and can also store additional relationship-specific data, such as roles or dates.

Maps and Location Settings is a Setup page where administrators enable and configure map and geolocation features in Salesforce, including the display of interactive maps on address fields, geocoding of addresses, and location-based services for mobile users.

Marketing Automation is the practice - and set of tools - that uses software to execute, coordinate, and measure repeatable marketing tasks at scale: email campaigns, drip sequences, lead nurturing, scoring, audience segmentation, and cross-channel orchestration. In the Salesforce ecosystem, Marketing Automation is delivered primarily by Marketing Cloud Account Engagement (formerly Pardot) for B2B and Marketing Cloud Engagement plus Journey Builder for B2C and enterprise lifecycle marketing.

The current name for Pardot, Salesforce's B2B marketing automation platform that provides lead generation, nurture campaigns, scoring, grading, email marketing, and ROI reporting integrated with Sales Cloud.

Marketing Cloud Intelligence (formerly Datorama) is Salesforce's marketing analytics and reporting platform. It unifies marketing data from hundreds of sources and channels into a single dashboard, enabling cross-channel performance analysis, AI-powered insights, automated reporting, and ROI measurement. It connects to marketing platforms via API integrations (API Connect, TotalConnect, and LiteConnect) and helps marketers visualize campaign performance and optimize spend across all channels.

Marketing Cloud Personalization (formerly Interaction Studio) is Salesforce's real-time personalization and interaction management solution. It tracks customer behavior across web, email, mobile, and in-store channels in real time, using machine learning to deliver individualized content, product recommendations, and offers at the moment of interaction. It combines behavioral analytics with data from existing sources to build comprehensive customer profiles and enable personalized experiences throughout the customer journey.

Marketing User is a user-level permission (checkbox on the User record) that grants the ability to create, edit, and delete Campaign records and manage Campaign Members in Salesforce. It is distinct from marketing product licenses and operates independently of profiles and permission sets, serving as a simple toggle to enable campaign management for individual users.

A Salesforce feature that allows users to perform bulk operations on multiple records at once from a list view, such as mass email, mass transfer, mass update, or mass delete, saving time on repetitive tasks.

Mass Delete Records is a Setup tool that allows administrators to delete large numbers of records from standard objects like Leads, Accounts, Contacts, Cases, and Activities based on filter criteria. It provides a safe way to bulk-remove records without using Data Loader or writing Apex code.

Mass Transfer Approval Requests is a Setup tool that allows administrators to reassign pending approval requests from one user to another in bulk. This is useful when an approver is on leave, has left the company, or when approval responsibilities need to be redistributed.

Mass Transfer Records is a Setup tool that allows administrators to change the ownership of multiple records at once for objects like Accounts, Leads, Cases, and custom objects. It supports filter-based selection and can optionally transfer related records like open Opportunities and Cases along with the parent record.

Mass Update Addresses is a Setup tool that allows administrators to update address fields on multiple records simultaneously. It is particularly useful when a company changes its address format, corrects data quality issues, or needs to standardize addresses across a large number of records.

In Salesforce Shield Platform Encryption, the primary Hardware Security Module that stores the master wrapping key used to protect all derived tenant secrets and encryption keys across the platform.

In Salesforce, the complete list of all possible values defined for a picklist field, from which record type-specific subsets can be selected to control which values appear for different record types.

In Salesforce Shield Platform Encryption, a Salesforce-managed cryptographic key stored in Hardware Security Modules (HSMs) that, combined with the tenant secret, derives the data encryption keys for an org.

In Salesforce Shield Platform Encryption, a key stored in HSMs that encrypts (wraps) the tenant secrets, providing an additional layer of protection so tenant secrets are never stored in plain text.

A Master-Detail Relationship in Salesforce creates a tightly coupled parent-child link between two objects. The detail (child) record inherits the sharing and security settings of the master (parent), the lookup field is always required, and deleting the master record cascades to delete all related detail records. This relationship type enables Roll-Up Summary Fields on the master object.

Matching Rules is a Setup page where administrators create rules that define the criteria used to identify duplicate records. Matching rules specify which fields to compare and what matching algorithms to use (exact match, fuzzy match, etc.). They work in conjunction with Duplicate Rules to detect and prevent duplicates.

A Salesforce report format that groups data by both rows and columns with summary fields at each intersection, useful for comparing totals across two dimensions like product revenue by region and quarter.

In Salesforce, a Meeting Request is a calendar event or task that represents an invitation to meet with a contact, lead, or other party. Meeting requests can be created from records (contacts, opportunities, cases) and typically sync with external calendars (Outlook, Google Calendar) through Einstein Activity Capture, so the meeting appears in both Salesforce and the user's primary calendar.

In Salesforce Campaigns, the status assigned to each campaign member (like Sent, Responded, Attended) that tracks their level of engagement and response, with one status optionally marked as 'Responded' for ROI tracking.

A placeholder in Salesforce (written as {!FieldName} or {{{FieldName}}}) used in email templates, formulas, Visualforce pages, and documents that gets replaced with the actual field value from a record at runtime.

In Salesforce Lightning Message Service, a metadata component that defines a communication channel for publishing and subscribing to messages between Lightning web components, Aura components, and Visualforce pages on the same page.

In Chatter, a Message (specifically, a Chatter Message) is a private, one-to-one or one-to-few direct message between users. Unlike a Chatter post (which appears on a public feed) a Message is scoped to its recipients and not shared to a group or record feed. Chatter Messages were retired in many orgs over time in favor of Slack (now Salesforce's primary enterprise messaging product) and Experience Cloud notifications for external conversations.

In Salesforce Service Cloud, a feature that enables agents to communicate with customers through messaging channels like SMS, WhatsApp, Facebook Messenger, and Apple Messages for Business from the Service Console.

Messaging Components is a Setup page for managing the components used in Salesforce Messaging channels, including chat widgets, pre-chat forms, and post-chat surveys. Administrators configure these components to customize the customer's messaging experience across web, mobile, and social channels.

A Salesforce Service Cloud feature that embeds a persistent messaging widget directly within a company's mobile app, allowing customers to start and continue asynchronous conversations with support agents.

A Salesforce Service Cloud feature that adds a persistent messaging widget to a company's website, enabling customers to start asynchronous conversations with agents that persist across browser sessions.

Messaging Settings is a Setup page where administrators configure global settings for Salesforce Messaging channels, including chat timeout durations, auto-greeting messages, file transfer permissions, and session handling behavior across all messaging deployments in the org.

Metadata in Salesforce refers to the data that describes your org's configuration, customizations, and structure. It includes definitions of objects, fields, page layouts, validation rules, Apex classes, Flows, and every other component that makes up your Salesforce environment. Metadata is what gets deployed between orgs and is the foundation of Salesforce DX source-driven development.

An individual piece of Salesforce configuration or customization (like a custom field, Apex class, page layout, or workflow rule) that can be deployed between orgs using change sets, metadata API, or Salesforce DX.

A Salesforce developer resource that documents which metadata types and their properties are accessible through the Metadata API, helping developers understand what can be programmatically retrieved and deployed.

A category of Salesforce metadata (like CustomObject, ApexClass, Layout, Flow) that classifies configuration components, used in package.xml manifest files and Metadata API operations to specify what to deploy or retrieve.

A WSDL file downloaded from a Salesforce org that describes the Metadata API web service operations (deploy, retrieve, list, describe), used to generate client code for tools that manage org metadata programmatically.

A Salesforce development approach that uses declarative configurations (metadata) like custom objects, fields, page layouts, and flows rather than code to build applications, promoting point-and-click development over programming.

Migrate to Flow is a Setup tool that helps administrators convert legacy Process Builder processes and Workflow Rules to Flows. Salesforce is retiring Process Builder and Workflow Rules in favor of Flow as the unified automation tool, and this migration assistant automates much of the conversion process.

In Salesforce context, the process of moving data, metadata, or configurations between Salesforce orgs (such as sandbox to production) or from external systems into Salesforce using tools like Data Loader, change sets, or the Metadata API.

In Salesforce Service Cloud entitlement management, a required step in a support process (like First Response or Resolution) with a defined time limit that tracks whether service-level commitments are being met.

Automated actions in Salesforce entitlement processes that trigger at specific points relative to a milestone's target time, including warning actions (approaching deadline), violation actions (past deadline), and success actions (completed on time).

A reusable definition in Salesforce Service Cloud that names and describes a type of service milestone (like First Response, Case Resolution, or Follow-Up) that can be used across multiple entitlement processes.

Mini Page Layout controls the arrangement and visibility of elements on a Salesforce page. Administrators configure it to determine which fields, buttons, related lists, and sections appear for users, optimizing the interface for specific roles or processes.

A compact, abbreviated view of a record in Salesforce that shows key fields in a condensed format, typically appearing in hover details, related list previews, or console sidebar components.

Mobile Builder for the Seller-Focused Experience is a Setup tool for customizing the Salesforce mobile experience specifically designed for sales representatives. It allows administrators to configure the mobile app layout, quick actions, dashboards, and features optimized for selling on the go.

In Salesforce mobile administration, the settings and customizations that control how the Salesforce mobile app behaves for specific user groups, including navigation menu items, compact layouts, and enabled actions.

A Marketing Cloud application for creating and managing mobile marketing campaigns across SMS, MMS, push notifications, and group messaging channels, with tools for audience targeting and message personalization.

In Salesforce Einstein or Data Cloud, a tool for creating and managing machine learning models that can analyze data patterns and make predictions, configurable through a visual interface without deep data science expertise.

In Salesforce Trailhead, a learning unit that contains a group of related instructional units covering a specific topic, combining reading material, interactive challenges, and quizzes to teach Salesforce concepts.

Monitor Workflow Services is a Setup page that provides visibility into the execution status of workflow rules, including pending time-based workflow actions and outbound messages awaiting delivery. Administrators use this page to troubleshoot delayed or stuck workflow actions.

An integration application built using MuleSoft's Anypoint Studio (part of the Salesforce ecosystem) that connects APIs and systems, implementing data flows and business logic using Mule runtime connectors and components.

MuleSoft is an integration and API management platform owned by Salesforce. Its core product, Anypoint Platform, allows organizations to connect applications, data sources, and devices using a library of pre-built connectors and an API-led connectivity approach. MuleSoft enables Salesforce to communicate with ERP, HR, and other enterprise systems.

Salesforce's integration and API management platform that provides tools for designing, building, deploying, and managing APIs and integrations across cloud and on-premises systems, enabling connected enterprise architecture.

MuleSoft Direct is a Setup feature that provides pre-built, no-code integrations between Salesforce and popular enterprise applications. It allows administrators to connect Salesforce to systems like SAP, Workday, and NetSuite using guided setup wizards without needing MuleSoft Anypoint Platform expertise.

The practice of connecting Salesforce with external systems using MuleSoft's Anypoint Platform, typically through pre-built connectors, API-led connectivity patterns, and Composer for low-code integration scenarios.

MuleSoft Observability is a Setup feature for monitoring the health, performance, and usage of MuleSoft integrations connected to Salesforce. It provides dashboards with metrics on API call volumes, error rates, latency, and throughput, helping administrators identify and resolve integration issues proactively.

A Salesforce calendar event that includes multiple invitees, creating a parent event for the organizer and individual child event records for each attendee, allowing separate acceptance tracking per person.

A Salesforce field type that allows users to select multiple values from a predefined list (separated by semicolons when stored), useful for tagging records with several applicable categories or attributes.

The Salesforce platform architecture where multiple customer organizations share the same physical infrastructure, application code, and database, while keeping each org's data securely isolated and separately configurable.

In Salesforce development, the architectural pattern where the Model (Apex classes/sObjects) manages data, the View (Visualforce/LWC) handles the UI, and the Controller (Apex) manages business logic and user interactions.

My Domain is a Setup page where administrators configure a custom subdomain for the org's Salesforce URL (e.g., mycompany.my.salesforce.com instead of a generic instance URL). My Domain is required for many Salesforce features including Lightning components, single sign-on, and Experience Cloud sites.

My Settings in Salesforce Lightning Experience is a personal configuration page where individual users manage their own account preferences and display options. Accessed by clicking the user avatar in the upper-right corner and selecting 'Settings,' it allows users to configure their personal information (name, email, language, locale, time zone), security settings (change password, view login history, manage advanced user details), display and layout preferences, email notification settings, and calendar options. My Settings is distinct from the admin Setup menu and does not require administrator privileges.

A Named Credential in Salesforce securely stores the URL and authentication settings for an external service endpoint. By referencing a Named Credential in Apex callouts or External Services, developers avoid hardcoding URLs and credentials in code, improving security and making it easy to update endpoints without code changes.

Named Query API is a Setup feature for creating and managing pre-defined, named SOQL queries that can be executed via API. These named queries provide a governed, reusable way for external systems to access Salesforce data using parameterized queries with controlled access.

In Salesforce, a unique prefix assigned to a managed package or Developer Edition org that prevents naming conflicts by qualifying all custom components (like classes, objects, and fields) with the namespace prefix.

The specific alphanumeric identifier (1-15 characters) registered for a Salesforce managed package that prepends to all its components (e.g., myapp__CustomObject__c), ensuring uniqueness across the AppExchange ecosystem.

A Salesforce application built entirely on the Lightning Platform using native tools (Apex, LWC, Flows, custom objects) rather than external technologies, benefiting from automatic upgrades, built-in security, and multi-tenancy.

A tab in Salesforce that links to a URL, Visualforce page, Lightning component, or Canvas app rather than a standard or custom object, providing users with navigation access to custom or external resources.

In Salesforce Surveys and Service Cloud, a customer loyalty metric measured by asking how likely customers are to recommend your company (0-10 scale), categorizing respondents as Promoters, Passives, or Detractors.

Net Zero Cloud (formerly called Salesforce Sustainability Cloud) is a Salesforce product that helps organizations track, analyze, and report their carbon emissions and environmental data to support ESG goals and climate commitments. It provides tools for carbon accounting, supplier emissions tracking, waste and water management, and regulatory reporting.

Network Access is a Setup page where administrators define trusted IP ranges that bypass identity verification challenges. When users log in from a trusted IP range, they are not prompted for additional verification steps like email codes or Salesforce Authenticator, simplifying the login experience from known corporate networks.

In Salesforce CPQ, a quote record created for a new sales opportunity (as opposed to a renewal or amendment quote), containing product line items, pricing, and terms for a potential new customer deal.

A Salesforce feature (part of Einstein Next Best Action) that uses strategies combining business rules and predictive models to recommend specific actions or offers to users at the point of customer interaction.

A declarative strategy built in Strategy Builder that defines the logic for Einstein Next Best Action recommendations, combining data filters, recommendation sources, AI models, and business rules to determine which offers or actions to suggest.

In Salesforce Experience Cloud and Chatter, a display name that users can set as an alternative to their full name, allowing them to participate in communities with a chosen alias for privacy or preference.

In Salesforce Einstein, a natural language processing model trained to understand and classify text data, used in features like Einstein Intent (classifying customer messages) and Einstein Sentiment (analyzing text sentiment).

Nonprofit Cloud is Salesforce's product suite tailored for nonprofit organizations. It provides tools for fundraising, donor management, program delivery, grant management, and outcome tracking. The platform includes the Nonprofit Success Pack (NPSP) data model and integrations with payment processors and marketing tools.

A Note in Salesforce is the legacy standard object (Note in the API) that stores short, plain-text annotations attached to a parent record. Each Note has a Title, a Body field (up to 32 KB of plain text), a polymorphic ParentId pointing to almost any standard or custom record, an OwnerId, and an IsPrivate flag that hides the note from anyone except its owner. Notes were the original way users captured ad-hoc context on Accounts, Contacts, Opportunities, Cases, and other records before Salesforce introduced Lightning Notes (the ContentNote object) with rich-text formatting, file attachments, and modern collaboration features. The classic Note object remains in every org for backward compatibility and is still surfaced through the Notes & Attachments related list, but Salesforce recommends using Lightning Notes for all new notes - they support inline formatting, images, multi-record sharing, and survive Lightning Experience migrations cleanly.

The enhanced notes feature in Salesforce (Lightning Experience) that provides a rich-text editor for creating notes associated with records, supporting formatting, lists, and images, replacing the legacy Notes & Attachments related list.

In Salesforce, an open authorization protocol used by connected apps to grant third-party applications secure, token-based access to Salesforce data without exposing user credentials, supporting flows like Web Server, JWT Bearer, and Device.

OAuth and OpenID Connect Settings is a Setup page where administrators configure global OAuth 2.0 and OpenID Connect settings for the org. This includes enabling or disabling OAuth features, configuring token policies, managing allowed OAuth flows, and setting up OpenID Connect discovery endpoints.

OAuth Custom Scopes is a Setup page for creating and managing custom OAuth scopes that define granular access permissions for Connected Apps. Custom scopes allow administrators to control precisely what data and operations each external application can access beyond the default OAuth scopes provided by Salesforce.

An Object in Salesforce is a database table that stores a specific type of data. Each object is made up of fields (columns) and records (rows). Salesforce comes with Standard Objects like Account, Contact, and Opportunity, and administrators can create Custom Objects to store data unique to their business.

A setup tool in Salesforce that provides a central interface for viewing and customizing all standard and custom objects, including their fields, relationships, page layouts, validation rules, and other object-specific settings.

Custom help text configured at the object level in Salesforce that appears on the object's overview or support page, providing users with a description of the object's purpose and how it should be used.

A Salesforce security setting (also called CRUD permissions) that controls whether users can create, read, update, or delete records of a specific object based on their profile or permission set.

A Salesforce quick action tied to a specific object that appears on that object's record pages, enabling users to perform contextual actions like creating related records, updating fields, or logging activities directly from the record.

In Salesforce Connect, an external system that exposes data through OData protocol endpoints, allowing Salesforce to consume and display that external data as external objects without storing it locally.

Omni-Channel is a Salesforce routing engine that intelligently distributes work items such as Cases, Leads, Chats, and custom records to the most appropriate available agent in real time. It considers agent capacity, skills, and availability to balance workloads and ensure fast response times across all service channels.

A Salesforce feature that uses Flow Builder to define routing logic for Omni-Channel, allowing admins to build custom routing rules that determine how work items are assigned to agents based on complex conditions.

Omni-Channel Home is a Setup page that serves as the central management console for Omni-Channel routing configuration. It provides an overview of routing configurations, queue assignments, presence statuses, and real-time supervisor dashboards for monitoring agent workload and service levels.

A Service Cloud feature that automatically routes incoming work items (cases, chats, leads, custom objects) to the most appropriate available agent based on agent capacity, skills, and routing configuration.

Omni-Channel Settings is a Setup page where administrators enable and configure Omni-Channel, Salesforce's intelligent routing engine. Settings include enabling Omni-Channel, configuring routing logic (queue-based or skill-based), setting capacity models, and defining presence statuses that agents can select.

A Salesforce Industries (OmniStudio) component that creates guided, step-by-step user interfaces for complex business processes, combining data collection, integration procedures, and conditional logic in a single interactive flow.

A Salesforce Industries suite of declarative tools (formerly Vlocity) including OmniScripts, FlexCards, Integration Procedures, and DataRaptors for building industry-specific guided experiences and integrations without code.

In Salesforce Industries, a document generated on demand from templates using data from Salesforce records, typically used for contracts, proposals, quotes, or policy documents that need to be created dynamically.

A One-to-Many Relationship in Salesforce means a single parent record can be associated with multiple child records. This is the most common relationship type and is created using either a Master-Detail field (tightly coupled, where child records inherit sharing/security and are deleted if the parent is deleted) or a Lookup field (loosely coupled, where child records can exist independently of the parent).

A JavaScript API in Salesforce that lets developers build custom softphone integrations for the Service Cloud console without requiring a browser plugin, enabling click-to-dial, screen pops, and call controls in Lightning Experience.

In Salesforce reports, formulas, SOQL queries, and validation rules, a symbol or keyword (like equals, not equal to, contains, greater than) that defines how field values are compared or evaluated in logical expressions.

An Opportunity in Salesforce represents a potential revenue-generating deal or sale. It tracks the progress of a deal through customizable sales stages, from initial prospecting to closed-won or closed-lost, and stores key details like expected revenue, close date, and probability of winning.

An Opportunity Contact Role in Salesforce (OpportunityContactRole in the API) is a standard junction object that links a Contact to an Opportunity, capturing each person's role in the deal - Decision Maker, Economic Buyer, Influencer, Champion, Evaluator, or any custom value the org defines. Each Opportunity Contact Role record holds a ContactId, an OpportunityId, a Role picklist, and an IsPrimary flag (only one Contact per Opportunity can be primary). Contacts attached through Opportunity Contact Roles do not have to belong to the Opportunity's Account - this allows complex selling situations where partners, influencers, advisors, or third-party evaluators participate in a deal without being employees of the buying organization. Opportunity Contact Roles drive several core sales features: campaign-influence reporting (which Contacts at which Opportunities came from which Campaigns), deal-team visibility, win/loss analysis by buyer persona, and account-based marketing attribution. They are required prerequisites for many advanced Sales Cloud features including Salesforce Inbox auto-association and Pardot/Account Engagement-driven attribution.

An Opportunity Line Item in Salesforce (OpportunityLineItem in the API) is a standard child object that represents a single Product included on an Opportunity, capturing the Quantity, UnitPrice, ListPrice, Discount, and TotalPrice for that line. Each Opportunity Line Item links to a parent Opportunity through OpportunityId and to a Product through PricebookEntryId - meaning an Opportunity Line Item always sits on top of a specific Price Book Entry and inherits its currency, list price, and product reference. The sum of all Opportunity Line Items' TotalPrice values populates the Amount field on the parent Opportunity (when "Use Product-Based Pricing" is enabled), which then drives forecasts, pipeline reports, and territory roll-ups. Opportunity Line Items snapshot pricing at insert time - subsequent changes to the underlying Price Book Entry do not propagate, so historical pipeline values remain stable as price lists evolve.

Opportunity Settings is a Setup page where administrators configure organization-wide behavior for the Opportunity object, including whether to prompt users to add products when creating Opportunities, whether to enable Opportunity Teams, and whether to track changes to Opportunity fields for forecasting.

A group of Salesforce users assigned to work together on a specific opportunity, with each member having a defined team role and configurable access level (read-only or read/write) to the opportunity record.

An Opportunity Team Member in Salesforce (OpportunityTeamMember in the API) is a standard junction object that adds a User to an Opportunity Team and grants that user configurable access to the parent Opportunity record. Each Opportunity Team Member record holds an OpportunityId, a UserId, a TeamMemberRole picklist (Account Manager, Pre-Sales Consultant, Sales Manager, Sales Rep, etc.), and an OpportunityAccessLevel field set to Read or Edit. Opportunity Team Members are the deal-level equivalent of Account Team Members - they let multiple users collaborate on a specific deal with shared visibility and edit access, without affecting access to other deals on the same Account. This matters most in orgs where Opportunity organization-wide defaults are Private or Public Read Only, requiring an explicit grant for non-owner users to participate in deal work. Default Opportunity Teams (configured per User in Personal Settings) auto-populate Opportunity Team Members on every new Opportunity the user creates, so a sales rep's standard supporting cast (SE, SDR, manager) follows them across every deal automatically.

Opt Out of Customer Data Access is a Setup feature that controls whether Salesforce support engineers can access the org's data when troubleshooting support cases. Organizations with strict data privacy requirements can opt out to ensure that Salesforce personnel cannot view any customer records during support interactions.

A Salesforce object that represents a confirmed purchase or request from a customer, containing order products (line items), status tracking, and associations to accounts and contracts for fulfillment management.

An Order Product in Salesforce (OrderItem in the API) is a standard child object that represents a single line item on an Order - one Product, one quantity, one price. Each Order Product has a parent Order through the OrderId field, a reference to the Product through PricebookEntryId, and a copy of pricing details at the moment the line was created: Quantity, UnitPrice, ListPrice (snapshot from the Price Book Entry), TotalPrice (calculated), and ServiceDate. Order Products are typically created in one of three ways: automatically when a closed-won Opportunity is converted to an Order (using Salesforce's built-in "Create Order from Opportunity" action), manually added by a sales-ops user as part of order entry, or programmatically through Apex or an integration. Like Quote Line Items and Opportunity Line Items, Order Products snapshot pricing at insert time - subsequent changes to the underlying Price Book Entry do not propagate.

Order Settings is a Setup page where administrators configure organization-wide behavior for the Order object, including enabling orders, setting default order status values, configuring reduction orders, and controlling whether negative quantities are allowed on order products.

An Org (short for organization) is a single instance of the Salesforce platform that includes all of an organization's data, configurations, customizations, and users. Each org has a unique identifier and operates as an isolated tenant in Salesforce's multitenant architecture. Companies typically have one production org and multiple sandbox orgs.

An Org Limit in Salesforce is an organization-level resource allocation that defines the maximum resources available to the entire org, such as API request limits, storage limits, or data limits. Org Limits are tracked via the Limits API and are enforced to ensure platform stability in the multi-tenant environment. They are distinct from Governor Limits, which are per-transaction runtime constraints on Apex code execution.

The baseline sharing setting for each object in Salesforce that determines the default level of access all users have to each other's records (Private, Public Read Only, Public Read/Write, or Controlled by Parent).

In Salesforce Web-to-Lead, leads generated when prospects find your company through a search engine and submit a web form, tracked as a lead source to measure search engine marketing effectiveness.

A Salesforce org (organization) represents a single customer's instance of Salesforce, containing all their data, configurations, customizations, and users, uniquely identified by an Organization ID.

An email address configured at the organization level in Salesforce that serves as a verified sending address for outgoing emails, workflow alerts, and automated notifications from the org.

The sharing model settings in Salesforce Setup that define the baseline record access for each object across the org, determining whether records are Private, Public Read Only, Public Read/Write, or Controlled by Parent by default.

In Salesforce Service Cloud and CTI integrations, a phone call initiated by an agent to a customer, which can be placed via click-to-dial functionality from contact or case records within the Service Console.

A change set created in a Salesforce org (typically a sandbox) to send metadata components to another connected org (typically production), containing customizations like fields, objects, and classes for deployment.

A workflow action in Salesforce that sends a SOAP message to an external web service endpoint when triggered, containing specified field values from the record, enabling real-time integration with external systems.

Outlook Integration and Sync is a Setup page where administrators configure the integration between Salesforce and Microsoft Outlook. This includes enabling Lightning for Outlook (the Salesforce sidebar in Outlook), configuring email and calendar sync settings, and managing how contacts, events, and emails flow between the two platforms.

In the Salesforce console (Classic), a detail view that opens as a floating panel on top of the current page, allowing agents to view or edit record details without navigating away from their current work context.

The Salesforce user assigned as the owner of a specific record, who has full access to that record and whose ownership determines the record's position in the role hierarchy for sharing and reporting purposes.

In Salesforce Forecasting, the forecast amount that includes only the opportunities owned directly by a specific user, excluding any rollup amounts from subordinates in the forecast hierarchy.

In Salesforce Forecasting, the forecast quantity that includes only the opportunities owned directly by a specific user, excluding any rollup quantities from subordinates in the forecast hierarchy.

Platform as a Service - in Salesforce context, the Lightning Platform (formerly Force.com) which provides a cloud-based development environment where customers build custom applications without managing underlying infrastructure.

In Salesforce, a container for distributing custom applications, components, and configurations through the AppExchange or between orgs, available as managed packages (with IP protection) or unmanaged packages (open source).

A relationship between Salesforce packages where one package requires another package to be installed first, typically when a package extension references components from a base managed package.

The process of installing a Salesforce package (from AppExchange or a URL) into an org, which deploys the package's metadata components and makes its functionality available to users based on configured permissions.

In Salesforce DX and second-generation packaging (2GP), the tooling and commands used to create, version, and manage packages, including the sf package commands for building and distributing applications.

The process of publishing a Salesforce managed package to the AppExchange, making it available for other organizations to discover, install, and use, including security review and listing management.

Package Usage is a Setup page that displays license usage and allocation information for all installed managed packages in the org. It shows how many licenses are available, how many are assigned, and which users have been granted access to each package.

A specific numbered release of a Salesforce managed package that can be installed in subscriber orgs, with each version potentially adding features, fixes, or changes while maintaining backward compatibility with previous versions.

A Page Layout in Salesforce controls the arrangement of fields, buttons, related lists, and custom links on a record detail page. Administrators use the drag-and-drop layout editor to organize which elements appear, in what order, and whether fields are required, read-only, or hidden for users assigned to specific profiles.

In Salesforce account hierarchy, the account record that sits above a child account in a parent-child relationship, used to model corporate structures where subsidiaries or divisions roll up to a parent company.

In Salesforce Knowledge or Ideas, a category that contains subcategories in a hierarchical data category structure, used to organize and control visibility of articles or ideas by topic.

A Salesforce sandbox type that copies all metadata and configurations from production plus a sample of production data (defined by a sandbox template), used for testing with realistic data without copying the full dataset.

In Salesforce Classic console, a section of the page that updates independently without requiring a full page refresh, improving performance and user experience when navigating between records in the console.

In Salesforce, a company or individual with whom you have a business relationship through the Partner Relationship Management (PRM) features, typically a reseller, distributor, or channel partner tracked via partner accounts.

Salesforce accounts enabled for partner relationship management that allow external partner users to access your org through an Experience Cloud partner portal, with shared deal registration, lead distribution, and co-selling features.

Partner Experience is a Setup area for configuring Experience Cloud partner portals, which give external partners secure access to Salesforce data for deal registration, lead management, and collaboration. It includes settings for partner user profiles, sharing rules, and the partner community layout.

A legacy Salesforce portal (now replaced by Experience Cloud partner sites) that gave external partner users access to Salesforce data, deal registration, lead management, and collaborative selling tools.

The role assigned to a partner account's relationship with the account owner's organization in Salesforce, describing the business relationship (like Reseller, Distributor, or Integrator) for tracking purposes.

A Salesforce user associated with a partner account who accesses the org through an Experience Cloud partner site, typically with a Partner Community license providing access to leads, opportunities, and collaborative features.

A WSDL file in Salesforce designed for use by AppExchange partners and ISVs, providing a simplified interface for making SOAP API calls that is suitable for building client applications distributed across multiple orgs.

Password Policies is a Setup page where administrators define the password requirements for users in the org. Settings include minimum password length, complexity requirements (uppercase, lowercase, numbers, special characters), password expiration intervals, password history enforcement, and maximum login attempts before lockout.

In Salesforce second-generation managed packaging, a patch version that delivers bug fixes to a specific major.minor version of a package without introducing new features, allowing subscribers to receive targeted fixes.

In Salesforce packaging, a special Developer Edition org created from a managed package's major release to develop patch versions (bug fixes) that can be pushed to subscribers without requiring a full upgrade.

A Salesforce managed package release that contains only bug fixes for a specific major.minor version, distributed to subscriber orgs to resolve issues without introducing new features or requiring manual upgrades.

Path Settings is a Setup page where administrators enable and configure Path, a visual component that displays the stages of a process (like Opportunity stages or Case status values) as a guided, interactive progress bar on record pages. Admins can add coaching guidance and key fields to each step.

In Salesforce Health Cloud, a visual timeline component that displays a patient's medical history, appointments, care plan activities, and clinical events in chronological order on a single longitudinal view.

Paused And Failed Flow Interviews is a Setup page that displays all Flow interviews that are currently paused (waiting for user input or a scheduled resume) or have failed due to errors. Administrators can view error details, resume paused interviews, or delete stuck interviews to free up system resources.

In Salesforce Billing or Payments, a record representing a financial transaction where a customer remits funds against an invoice or balance, tracking payment amount, method, date, and allocation to invoices.

In Salesforce Scheduler, a configuration option that prioritizes appointment bookings during peak business hours first, helping organizations maximize appointment density during their busiest time periods.

In Salesforce Data Cloud (formerly CDP) or Marketing Cloud, a unified profile representing an individual contact or customer, consolidating identity data from multiple sources into a single actionable record.

In Salesforce Forecasting, a quota metric expressed as a percentage of a target rather than a fixed number, used when measuring sales performance against goals on a proportional basis.

In Salesforce, a specific access right granted to a user through profiles or permission sets that controls what actions they can perform, such as API Enabled, View All Data, Modify All Data, or Manage Users.

A Permission Set is a collection of settings and permissions that grant users access to specific tools, objects, fields, and features without changing their Profile. Permission Sets are additive, meaning they extend what a user can do on top of their base Profile permissions. They are a best practice for managing access in Salesforce.

A Permission Set Assignment in Salesforce (PermissionSetAssignment in the API) is a standard junction object that records a single grant of a Permission Set or Permission Set Group to a specific User. Each Permission Set Assignment record holds an AssigneeId (the User receiving the permissions), a PermissionSetId (the Permission Set being granted) or a PermissionSetGroupId, an optional ExpirationDate that automatically removes the assignment when reached, and standard system fields. Permission Set Assignments are the operational mechanism for the additive-permissions model that Salesforce recommends over Profile-based permissions: every User gets a baseline Profile (assigned permanently), and incremental access is layered on through Permission Set Assignments that can be added, removed, or expired without modifying the underlying Profile. This pattern dramatically simplifies permission management - instead of maintaining hundreds of variant Profiles, admins maintain a smaller set of base Profiles plus a library of focused Permission Sets that are mixed and matched per User.

A Permission Set Group bundles multiple Permission Sets together into a single assignable unit, simplifying access management for users who need a combination of permissions. Administrators can also add Muting Permission Sets within a group to suppress specific permissions, providing fine-grained control over the aggregate set of access.

A Permission Set License (PSL) in Salesforce is a supplemental license that grants a user access to features, objects, or permissions not included in their base User License. Unlike a User License (which every user must have), Permission Set Licenses are optional and are assigned only when users need access to specific gated functionality. For example, the 'CRM Analytics Plus Permission Set License' enables Einstein Analytics features, and the 'Identity Connect Permission Set License' enables identity management capabilities. Administrators assign PSLs to users from Setup, and once assigned, the related permissions can be granted through Permission Sets.

A Salesforce feature that combines an Account and Contact record into a single record for representing individual customers (B2C) rather than businesses, storing both company-level and personal information on one object.

In Salesforce user settings, a category of user profile data (like name, email, phone, address) that users may be able to edit themselves and that is subject to data protection and privacy configurations.

Personal Settings in Salesforce Classic is the user-facing configuration area where individual users manage their own preferences without needing administrator access. Accessed via the user's name menu in Salesforce Classic, it provides options for updating personal information (name, email, address), changing language, locale, and time zone settings, configuring email and calendar preferences, managing login history and security tokens, setting up email signatures, and adjusting display options. Personal Settings is the Classic equivalent of My Settings in Lightning Experience.

In Salesforce search, the ability to search for an exact multi-word phrase by enclosing it in quotation marks, ensuring results contain those words in that specific order rather than as separate terms.

A Salesforce field type that presents users with a predefined dropdown list of values to select from, ensuring data consistency and enabling reporting by constraining input to a controlled set of options.

Picklist Settings is a Setup page where administrators configure global behavior for picklist fields across the org, including whether to sort picklist values alphabetically or in a custom order, and whether to restrict picklist field values to only those defined by the administrator.

Picklist Value Sets is a Setup page for creating and managing global picklist value sets that can be shared across multiple picklist fields on different objects. When a value is added to or removed from a global value set, the change is automatically reflected on all fields using that set.

The individual options defined within a Salesforce picklist field, which can be managed as a global picklist value set (shared across fields) or as field-specific values, with options for active/inactive status and record type filtering.

A Salesforce list view feature that allows users to pin frequently used list views to the top of the list view selector for quick access, keeping preferred views readily available without scrolling.

In Salesforce Sales Cloud, the collection of all open opportunities in various stages of the sales process, representing the total potential revenue being actively pursued by the sales team.

Platform as a Service - the Salesforce Lightning Platform (formerly Force.com) delivery model that provides a complete cloud development and deployment environment, allowing customers to build applications without managing servers or infrastructure.

A Salesforce caching layer (part of Platform Cache) that stores frequently accessed data in memory using org cache (shared across users) or session cache (per user), reducing SOQL queries and improving application performance.

Platform Edition (also known as Lightning Platform Starter or Lightning Platform Plus) is a Salesforce edition that provides access to the core Salesforce platform for building and running custom applications without the standard CRM functionality. It excludes standard CRM objects like Opportunities, Forecasts, Quotes, and Campaigns, but includes custom objects, Tabs, Apex, Visualforce, Lightning components, Flows, APIs, and the AppExchange. Platform Edition comes in two tiers: Starter (with basic limits) and Plus (with higher limits and additional features like custom report types). It is designed for organizations that need a custom application platform rather than out-of-the-box CRM.

A Platform Event is a Salesforce messaging mechanism that enables event-driven architecture by allowing systems to publish and subscribe to real-time event messages. Platform Events decouple producers and consumers, enabling communication between Salesforce components, external systems, and asynchronous processes using a publish-subscribe model.

The Salesforce event streaming infrastructure that delivers platform events and Change Data Capture events to subscribers in near real-time, using a publish-subscribe model based on CometD/gRPC protocols.

In Salesforce Maps and Location services, a geographic coordinate or location data point represented on a map, used for geolocation features, territory mapping, and field service optimization.

In Salesforce Ideas communities, a list view that surfaces the ideas with the most votes or engagement from community members, helping organizations identify the most requested features or improvements.

In Salesforce Chatter Answers or Experience Cloud Q&A, a list view that displays the questions receiving the most views, replies, or engagement, helping surface commonly asked topics in the community.

Portal Health Check is a Setup tool that evaluates the security configuration of Experience Cloud sites (formerly Community portals) against Salesforce's recommended security standards. It identifies vulnerabilities such as excessive guest user permissions, insecure sharing rules, and missing authentication requirements.

In Salesforce Chatter, a message shared to a user's feed, a group feed, or a record feed that can contain text, mentions, hashtags, files, links, or polls for social collaboration within the org.

In Salesforce Chatter, the action of sharing another user's post to your own feed or a group feed, increasing its visibility and distribution to a wider audience within the organization.

Post Templates is a Setup page where administrators create predefined Chatter post templates that standardize how users share updates. Templates can include pre-formatted text, merge fields, and structured layouts that ensure consistent communication across the organization.

In Salesforce Visualforce, an HTTP POST request sent back to the server when a user interacts with a form element on a Visualforce page, triggering server-side controller actions and potentially re-rendering page components.

Predefined Case Teams is a Setup page where administrators create reusable teams of users that can be quickly assigned to Cases. Each team member has a defined role (such as Technical Lead or Escalation Manager) and access level, making it easy to assemble the right group of people for specific types of Cases.

A Prediction in Salesforce Einstein is a scored output generated by a machine learning model that estimates the likelihood of a future outcome. Einstein Prediction Builder allows administrators to create custom predictions on any standard or custom object by selecting a target field (what they want to predict), defining the dataset (record filters and example fields), and building a model. The resulting prediction appears as a score (0-100%) or a predicted value directly on the record. Salesforce also provides built-in predictions including Einstein Lead Scoring, Einstein Opportunity Scoring, and Einstein Case Classification, each trained on the org's historical data.

In Salesforce Einstein, a machine learning model trained on historical data to predict future outcomes (like lead conversion probability or opportunity close likelihood), deployable through Prediction Builder or Einstein Discovery.

A Service Cloud feature powered by Einstein AI that uses machine learning to route cases and other work items to the agent who is most likely to resolve them successfully, based on historical resolution patterns.

In CRM Analytics (formerly Tableau CRM, originally Einstein Analytics), a Preparation Recipe is a data preparation step that transforms, cleans, and combines datasets before analysis. Built in a visual recipe editor, it lets analysts define filters, joins, formulas, and aggregations without writing code - shaping raw source data into the dataset that powers dashboards and lenses.

In Salesforce Omni-Channel, a status set by agents to indicate their current availability (like Available, Busy, or On Break), which determines whether new work items can be routed to them.

A Salesforce object that contains a list of products and their prices, with a standard price book holding default prices and custom price books containing special pricing for different markets, customer segments, or promotions.

A Price Book Entry in Salesforce (PricebookEntry in the API) is a standard junction object that connects a Product (Product2) to a Price Book (Pricebook2) and stores the price for that Product within that Price Book. Each Price Book Entry holds a UnitPrice, a CurrencyIsoCode (in multi-currency orgs), an IsActive flag, a UseStandardPrice flag, and a ProductCode field denormalized from the parent Product. Every Product must have a corresponding Price Book Entry in the Standard Price Book before it can be added to any custom Price Book or used on an Opportunity, Quote, or Order. Custom Price Books can hold different prices for the same Product - for example, a "Government" Price Book offering a 20% discount on every item - by creating their own Price Book Entries. Price Book Entries are the reference rows that Opportunity Line Items, Quote Line Items, and Order Products copy from when they are created.

In Salesforce, a Primary Contact is the one Contact designated as the main point of communication for a parent record - typically an Account's primary business contact, or the lead decision-maker on an Opportunity (via the Opportunity Contact Role with Primary = true). Only one Primary Contact exists per parent. It drives default addressees on merge templates, campaign influence attribution, and many report and automation filters that key off "primary contact's" fields.

In Salesforce database architecture, the unique Record ID (15 or 18 character) that serves as the primary key for every record in every object, ensuring each record can be uniquely identified and referenced.

In Salesforce Partner Relationship Management, the primary partner account associated with an opportunity, typically the main channel partner responsible for the deal in partner-driven sales scenarios.

In the Salesforce Classic console, the main browser-like tab that represents a primary record (like a case or account), which can have multiple subtabs showing related records, allowing agents to work across related data.

A Salesforce feature that renders a simplified, print-friendly version of a record or report page, stripping out navigation elements and interactive components so the content can be cleanly printed.

Privacy Center is a Setup tool that helps organizations manage data privacy compliance by providing capabilities for executing data subject access requests (right to access), data deletion requests (right to be forgotten), data portability, and consent preference management in accordance with privacy regulations.

In Salesforce CTI and Service Cloud Voice, a private telephone system used by an organization to manage internal and external calls, which integrates with Salesforce through CTI adapters to enable screen pops and call logging.

Private Connect is a Setup feature that enables private, secure network connections between Salesforce and Amazon Web Services (AWS) without routing traffic over the public internet. It uses AWS PrivateLink technology for private peering, reducing latency, improving security, and helping organizations comply with strict network isolation requirements.

In Salesforce Chatter, a file or post sharing setting where the content is shared only with specific, invited individuals rather than being visible to the entire organization or a public group.

In Salesforce opportunity management, a percentage field on the opportunity record indicating the likelihood of closing the deal, typically auto-populated based on the opportunity stage but editable by the sales rep.

In MuleSoft's API-led connectivity approach (part of the Salesforce ecosystem), a middle-tier API that orchestrates data between system APIs and experience APIs, handling business logic, data transformation, and process coordination.

Process Automation Settings is a Setup page where administrators configure global settings for all process automation tools in the org. Options include setting the default workflow user, enabling email notifications for workflow errors, and configuring how formula fields are evaluated in automation contexts.

In Salesforce approval processes, a record that represents a single running instance of an approval process for a specific record, tracking the current status, submitted date, and the history of approval steps.

In Salesforce approval processes, a record representing a specific step (node) within a process instance, tracking which approver was assigned, the approval or rejection decision, and any comments provided at that step.

A Salesforce Setup tool that displays a visual diagram of an approval process, showing all steps, decision branches, approval/rejection actions, and routing logic in a flowchart format for easy understanding and troubleshooting.

A Salesforce object that represents an item or service your company sells, stored in the product catalog with details like name, description, product code, and family, linked to price books for pricing.

A categorization field on the Salesforce Product object that groups products into logical families or categories (like Hardware, Software, Services), used for reporting, forecasting, and organizing the product catalog.

Product Settings is a Setup page where administrators configure organization-wide behavior for the Product object and Price Books. Settings include enabling or disabling quantity and revenue schedules, configuring how products relate to Opportunities, and setting defaults for price book behavior.

In Salesforce B2B Commerce or Commerce Cloud, a product record configured for display in the storefront checkout process, representing an item available for purchase by customers through the online store.

A Salesforce customer's live production org where real business data is stored and end users work, as opposed to sandbox or development orgs used for testing and development purposes.

Professional Edition is a Salesforce CRM edition designed for small to mid-sized businesses that need full CRM functionality. It includes core features such as account and contact management, lead management, opportunity tracking, campaigns, products and price books, forecasting, and customizable reports and dashboards. Professional Edition supports Visualforce pages but does not include Apex code or full API access without add-on licenses.

A Salesforce configuration that defines a user's permissions, page layout assignments, field-level security, and app visibility, serving as the baseline set of access controls assigned to each user in the org.

The Chatter-specific aspects of a Salesforce user's profile page, including their photo, bio, contact information, feed posts, followers, following list, and groups, visible to other users in the organization.

A Salesforce.org (now Salesforce for Nonprofits) app that helps nonprofit organizations track programs, services, and client outcomes, managing program cohorts, service deliveries, and impact measurement.

In Salesforce DX, a Project is a local directory containing a sfdx-project.json configuration file, source-format metadata, and Git history that developers use with Salesforce CLI (sf, the unified CLI that replaced the original sfdx in 2023) to build and deploy customizations. The Project is the unit of work for source-driven Salesforce development and is typically synonymous with DX Project or Local Project.

In Salesforce DX, the Project Manifest is the sfdx-project.json file at the root of a DX Project. It declares which directories contain package source, the source API version used for metadata format conversions, the default Dev Hub alias, and - for Second-Generation Packaging (2GP) - package aliases, dependencies, and versioning. Salesforce CLI (sf, the unified CLI that replaced the original sfdx in 2023) reads sfdx-project.json on every command to understand the project layout.

In Salesforce Ideas, the action of moving an idea from one zone or status to a more visible or advanced state, or in packaging, promoting a beta package version to a released (production-ready) state.

A Salesforce tool that lets admins and developers create reusable prompt templates for generative AI, combining grounding data from CRM records with instructions to generate consistent, context-aware AI outputs across sales, service, and marketing.

In Salesforce implementation and development, a Prototype is an early, disposable build of a feature, screen, flow, or integration - used to validate the design with users before committing to a production-quality implementation. Salesforce teams often prototype in a scratch org or developer sandbox, use Lightning App Builder and Flow for low-code prototypes, and treat the prototype as throwaway or scaffolding rather than the final artifact.

Note: 'Prototype object' is not a recognized standard Salesforce term or feature. In general software development, a prototype refers to a preliminary version of a product or feature built to test concepts before full development. In the Salesforce context, if used informally, it may refer to a draft custom object created during the design phase of an application, but it has no official platform definition or specific behavior.

In Salesforce Health Cloud, the healthcare organization or facility that delivers care to patients, represented as an account record with provider-specific attributes like NPI, specialty, and network affiliation.

A Salesforce calendar visible to all users (or specific groups) in the organization, used for sharing company-wide events, team schedules, and resource availability beyond individual user calendars.

A Salesforce group consisting of individual users, roles, roles and subordinates, or other groups, used in sharing rules, folder access, email distribution, and queue membership to manage collective access and notifications.

Public Health Analytics Settings is a Setup page for configuring pre-built analytics dashboards designed for public health organizations. These dashboards provide visualizations for disease surveillance, vaccination tracking, community health metrics, and emergency response coordination.

In Salesforce Knowledge, an article version that has been published and is live and available to users through the channels it was configured for (internal app, customer portal, or public knowledge base).

In Salesforce Knowledge, a translated version of a knowledge article that has been published and made available to users in the target language, part of the multi-language knowledge base feature.

In Salesforce Chatter, the user who creates and shares a feed post, or in Experience Cloud, a content publisher who creates and distributes articles, posts, or other content to the community.

In Salesforce Knowledge, the workflow of creating, editing, reviewing, translating, publishing, and archiving knowledge articles through their lifecycle stages, managed by article actions and approval processes.

Purchase Rules is a declarative rule within the Salesforce platform that applies business logic to records based on field values and conditions. When criteria are satisfied, the rule performs its configured actions automatically, ensuring consistent enforcement of business policies.

In the Salesforce Mobile App, push notifications sent to a user's mobile device alerting them about Salesforce events like approval requests, task assignments, Chatter mentions, or custom notifications defined by admins.

In the Salesforce Classic console, push notifications that update the console in real-time when records the agent is viewing are modified by other users or system processes, keeping the agent's view current without manual refresh.

In Salesforce managed packaging, the process where an ISV automatically pushes a new package version to all subscriber orgs without requiring individual customers to manually initiate the upgrade.

A Salesforce Forecasting option that forecasts based on product quantities rather than (or in addition to) revenue amounts, useful for organizations that track sales performance by unit volume.

In Salesforce Products and Pricing, a schedule defined on a product that specifies how the product quantity will be delivered over time in installments, breaking a single order into multiple delivery dates.

In Salesforce Forecasting, the raw forecast quantity total from opportunities before any manager or owner adjustments have been applied, representing the unadjusted bottom-up quantity forecast.

In Salesforce Forecasting, the forecast quantity for a user's team that excludes adjustments made by their manager in the forecast hierarchy, showing the quantity total before management overrides.

In Salesforce Forecasting, the forecast quantity that excludes the owner's own judgment adjustments, showing only the raw rollup of opportunity quantities before the forecast owner made manual changes.

In Salesforce Apex SOQL, a cursor returned by Database.getQueryLocator() that enables processing of up to 50 million records in batch Apex jobs, compared to the standard 50,000-record SOQL limit.

In Salesforce URLs and web-to-lead/case forms, a parameter passed in the URL query string (after the ? character) that can prepopulate field values on records or control page behavior when the URL is loaded.

In Salesforce, a Question refers to a post type in Chatter Questions or Experience Cloud Q&A where a user asks for help or information from the community. Unlike a standard Chatter post, a Question supports answer-thread semantics - one or more Answers below, a Best Answer selection, and notification/follow subscriptions on the thread itself. Questions are a first-class Chatter object and can be routed into Cases if they need service-agent attention.

In Salesforce Chatter Answers, a question posted privately that is visible only to support agents and the question author, not to the broader community, used for sensitive or account-specific inquiries.

In Salesforce, a holding area for records (like cases, leads, or custom objects) that are awaiting assignment to a user, where any queue member can claim ownership, used to distribute work among teams.

A Queue Member in Salesforce is a User who has been added to a Queue, granting them the right to claim ownership of records assigned to that Queue. Under the hood, Queue membership is stored as Group Member records (with the parent Group having Type = "Queue"), since Queues in Salesforce are a specialized type of Group. Each Queue Member has visibility into all records currently owned by the Queue, can change their ownership to themselves (claiming a record) or assign them to other team members, and is included in any Queue-targeted notifications, email alerts, or routing rules. Queue Members are the operational core of any work-distribution model in Salesforce - Service Cloud queues for Cases, Sales Cloud queues for Leads, and custom-object queues for any team-shared workload. Adding or removing Queue Members directly affects who can act on the queued work, making roster management one of the most frequent admin tasks in service-heavy and high-volume sales orgs.

In Salesforce CRM Call Center (Classic CTI), a queue that holds incoming calls waiting to be routed to available agents, managing call distribution based on configured routing rules and agent availability.

A Salesforce action (global or object-specific) that provides users with a shortcut to perform common tasks like creating records, logging calls, sending emails, or updating fields, accessible from action bars and record pages.

A Salesforce productivity feature that stores predefined text snippets agents can insert into emails, chats, and other text fields with a few clicks, supporting merge fields to auto-populate record data into the text.

Quick Text Settings is a Setup page where administrators enable and configure Quick Text, which provides pre-written text snippets that users can insert into emails, chats, and other text fields. Quick Text reduces typing time and ensures consistent messaging across the support and sales teams.

Quip is a Salesforce collaboration and productivity platform (acquired in 2016) that combines documents, spreadsheets, chat, and task management in a single workspace, integrated with Salesforce records for contextual document collaboration. Salesforce has announced the end of life for Quip, with all subscriptions unable to be renewed after March 1, 2027. After subscription expiration, instances go through a 90-day read-only phase, a 90-day blocked login phase, and then data deletion. Salesforce recommends migrating to Slack and Agentforce.

In Salesforce Sales Cloud, a revenue or quantity target assigned to a sales rep or team for a specific time period, used in forecasting to measure performance against goals and track attainment percentages.

A Salesforce object that represents a formal pricing proposal for products or services, generated from an opportunity with line items, pricing, terms, and the ability to produce PDF quote documents for customers.

A line item on a Salesforce Quote record that specifies a particular product, its quantity, unit price, and any discounts, representing one product entry in the overall pricing proposal.

In Salesforce B2B Commerce, the quote or pricing summary presented to a buyer during the checkout process, reflecting the products in their cart with negotiated or list pricing applied.

Quotes Settings is a Setup page where administrators enable and configure the Quotes feature, which allows sales reps to create detailed price quotes from Opportunity records. Settings include enabling quotes, configuring quote templates, and setting up quote-to-order conversion rules.

A Salesforce field or record access level that allows users to view data but not modify, create, or delete it, enforced through profiles, permission sets, field-level security, or sharing settings.

In Salesforce Service Cloud Voice, a feature that converts live phone conversations to text in real-time during customer calls, providing agents with a running transcript and enabling AI-powered suggestions.

Real-Time Translations is a Setup feature that enables automatic translation of Knowledge articles and other content in real time using AI-powered translation services. It allows organizations to make their content instantly available in multiple languages without waiting for manual translation cycles.

In Salesforce approval processes, the automated actions that execute when an approval request is recalled (withdrawn) by the submitter, such as field updates to revert the status or email notifications.

In Salesforce, a related list or section on a record page that displays the most recent activities (tasks and events) associated with that record, giving users a quick view of latest interactions.

A feature in Salesforce that tracks and displays the records a user has most recently viewed or edited, accessible from the navigation bar or search results for quick return access to frequently used records.

In CRM Analytics (formerly Tableau CRM, originally Einstein Analytics), a Recipe is a set of data transformation steps that prepares and combines datasets for analysis. Joins, filters, computed columns, and aggregations are defined in a visual editor, each step connected to the next to form a declarative data-prep pipeline - the output is a dataset that dashboards and lenses read from.

In Salesforce Einstein Next Best Action, a record that represents a specific offer or action to suggest to a user, containing a name, description, acceptance label, and rejection label displayed through the recommendation component.

In Salesforce Einstein Next Best Action, a strategy built in Strategy Builder that defines the decision logic for which recommendations to surface, combining data sources, filters, AI models, and business rules.

A Record in Salesforce is a single row of data stored in an object. Each record has a unique 15- or 18-character Salesforce ID and contains field values defined by the object's schema. Records are the fundamental units of data in Salesforce and can be created, read, updated, and deleted through the UI, APIs, or automation.

The main body section of a Salesforce record page that displays all the field values, related lists, and components configured in the page layout, representing the detailed view of a single record.

The unique 15-character (case-sensitive) or 18-character (case-insensitive) alphanumeric identifier assigned to every record in Salesforce, used in URLs, API calls, formulas, and relationships to reference specific records.

In Salesforce approval processes and Apex, the mechanism that locks a record to prevent edits while it is pending approval or being processed, ensuring data integrity during the approval workflow.

The primary identifying field on a Salesforce record (like Account Name, Case Number, or a custom auto-number field) that serves as the human-readable label for the record in lists, lookups, and search results.

Record Page Settings is a Setup page where administrators configure default behaviors for Lightning record pages, including whether to use the standard record page or a custom Lightning page, how related lists are displayed, and whether to enable dynamic forms and dynamic related lists.

A Record Type in Salesforce allows administrators to offer different business processes, picklist values, and page layouts for the same object based on user profile or context. Record Types are commonly used when a single object serves multiple purposes, ensuring that each group of users sees only the fields and values relevant to them.

In Salesforce automation (flows, process builder, workflow rules), an action that modifies field values on the triggering record or a related record, applying specified changes when criteria are met.

The Salesforce security layer that controls access to individual records (as opposed to object-level or field-level security), enforced through org-wide defaults, role hierarchy, sharing rules, manual sharing, and Apex managed sharing.

A Recurring Donation in Salesforce represents a donor's ongoing commitment to give a specified amount on a regular schedule - monthly, quarterly, or annually - to a nonprofit organization. In the Nonprofit Success Pack (NPSP), a Recurring Donation is stored on the npe03__Recurring_Donation__c custom object; in the modern Nonprofit Cloud, it is the standard RecurringDonation object. Each Recurring Donation record holds a parent Contact or Account (the donor), an Amount per installment, an Installment Period, a Date Established, a Status (Active, Lapsed, Closed), an optional End Date, a Payment Method, and configurable behaviors for how individual installment Opportunities (or Gift Transactions in Nonprofit Cloud) are generated. The recurring-donations engine automatically creates the next installment's transaction record at the appropriate cadence, posts it through payment processing, and updates the parent Recurring Donation's status if installments lapse or fail. Recurring Donations are foundational to nonprofit revenue strategy because sustaining donors typically have 5-10x the lifetime value of one-time donors and provide predictable monthly cash flow.

A Salesforce calendar event configured to repeat on a schedule (daily, weekly, monthly, or custom), creating a series of linked event records that share common details but have individual dates.

A Salesforce feature that temporarily stores deleted records for 15 days by default, allowing users and admins to restore accidentally deleted records before they are permanently purged. In Salesforce Classic, the Extended Recycle Bin Retention feature can extend this period to 30 days. The Recycle Bin can hold records up to 25 times the organization's data storage limit in megabytes.

A Salesforce Industries (Financial Services, Health Cloud) feature for tracking and managing referrals between parties, such as patient referrals between healthcare providers or client referrals between financial advisors.

A Refund in Salesforce (Refund in the API) is a standard object in Salesforce Order Management and Salesforce Billing that represents money returned to a customer after an Order has been fulfilled or partially fulfilled. Each Refund record holds a parent Account, a related PaymentId or PaymentGroupId tracing back to the original tender, an Amount, a Status (Draft, Pending, Processed, Cancelled, Failed), a CurrencyIsoCode, an EffectiveDate, a Type (Cash, Credit, Adjustment), a GatewayRefNumber for the payment processor's confirmation, and an optional reference to the originating Return Order or Credit Memo. Refunds close the financial loop on returns, cancellations, billing disputes, or goodwill credits - every dollar moving from the merchant back to the customer is captured as a Refund record, providing a queryable financial audit trail and a basis for reconciliation against the upstream payment gateway. Refunds integrate with Salesforce Billing's revenue recognition rules to ensure that recognized revenue is appropriately reversed when a refund is processed.

In Salesforce development, the practice of re-running tests after making changes to existing code or configurations to verify that updates have not broken previously working functionality.

A section on a Salesforce record page that displays records from a related object linked through a lookup or master-detail relationship, such as Contacts on an Account or Cases on a Contact.

In Salesforce Classic, the clickable links that appear at the top of a related list allowing quick access to actions like New, View All, and other operations without scrolling down to the full related list.

A single record displayed as a row within a Salesforce related list, representing one related record (like one contact or one case) associated with the parent record being viewed.

A Salesforce object that is connected to another object through a lookup or master-detail relationship field, allowing records on one object to reference and link to records on the other.

In Salesforce, a connection between two objects established through relationship fields (lookup, master-detail, or hierarchical), enabling records on one object to reference records on another for data modeling.

In Salesforce Financial Services Cloud, a grouping mechanism that associates multiple accounts and contacts into a household or business group, providing a unified view of related financial relationships.

In Salesforce Financial Services Cloud, an individual account or contact record that belongs to a relationship group (household), with attributes defining their role and relationship within the group.

In Salesforce SOQL, a query that traverses relationships between objects to retrieve fields from related records, using dot notation for parent-to-child (subquery) or child-to-parent relationships in a single query.

In Salesforce development lifecycle, the practice of planning, coordinating, and executing the deployment of changes across environments (sandboxes to production), using tools like change sets, DevOps Center, or Salesforce DX.

In Salesforce release management, a Release Train is a scheduled cadence of deployments that bundles multiple changes from multiple teams into a coordinated release to production. Each Release Train has fixed dates - code-freeze, UAT window, release day - and predictable sandbox refresh points leading up to them. The goal is to eliminate ad-hoc "one-off" production deploys, align testing and go-live across teams, and give stakeholders a consistent "when will my change ship?" answer.

Release Updates is a Setup page that lists upcoming and recently enforced Salesforce platform changes that may affect the org. Each update includes a description, impact assessment, enforcement date, and the option to test the update before it is automatically enforced, giving administrators time to prepare.

Remote Access is a Setup page for managing legacy Connected App configurations that allow external applications to authenticate and access Salesforce data. While newer Connected Apps are managed through the App Manager, Remote Access provides backward compatibility for older OAuth integrations.

A legacy term for a Salesforce Connected App, which is an application that uses OAuth to integrate with Salesforce, allowing external apps to authenticate users and access Salesforce data securely.

Remote Site Settings is a Setup page where administrators register external URLs that Salesforce Apex code is allowed to call. Before Apex can make an HTTP callout to an external endpoint, the endpoint's domain must be added as a Remote Site. This allowlist prevents unauthorized outbound connections from the platform.

Rename Tabs and Labels is a Setup page where administrators change the display names of standard objects and tabs to match their organization's terminology. This allows companies to customize Salesforce vocabulary without creating custom objects, making the platform feel natural to users.

In Salesforce CPQ and Subscription Management, the process of extending or renewing an existing contract or subscription, generating a renewal opportunity and quote with the existing product terms carried forward.

In Salesforce Chatter Answers, Experience Cloud Q&A, or case comments, a response posted to a question or discussion by a user or support agent, contributing to the conversation thread.

A Report in Salesforce is a configurable view of data that displays records meeting specified filter criteria in rows and columns. Reports can be tabular, summary, matrix, or joined, and support groupings, formulas, charts, and conditional highlighting. They are the foundation of Salesforce analytics and can be scheduled, exported, and embedded in dashboards.

The Salesforce report creation and editing tool that provides a drag-and-drop interface for selecting report type, adding fields (columns), defining filters, choosing groupings, and configuring summary formulas.

A Salesforce configuration that defines which objects and their relationships are available as data sources for a report, determining which fields can be included and how records from related objects are joined.

A Salesforce feature (also called Analytic Snapshot) that captures report results on a scheduled basis and stores them as records in a custom object, creating historical data snapshots for trend analysis over time.

The Salesforce user whose permissions and data access determine which records are included when a Reporting Snapshot runs, similar to how a dashboard running user controls the data scope.

The specific Salesforce report whose results are captured each time a Reporting Snapshot executes, with the report's columns mapped to fields on the target custom object where snapshot records are stored.

A Reporting Snapshot Target Object is the specific custom object that an administrator designates to store the data captured by a Reporting Snapshot (also called Analytic Snapshot). When a Reporting Snapshot runs on its defined schedule, it takes a point-in-time snapshot of a source report's data and maps each report column to a corresponding field on the target custom object, creating one new record per report row. Over time, the target object accumulates historical records, enabling trend analysis and historical comparisons through reports and dashboards built on the target object's data.

In Salesforce Scheduler, an appointment request created when a customer or agent selects a desired time slot, which may require confirmation or assignment before becoming a confirmed appointment record.

In Salesforce Field Service, a calendar associated with a service resource that displays their availability, scheduled appointments, work orders, and absences, used by the scheduling optimizer to assign work.

In Salesforce development, the architectural style used by the Salesforce REST API that enables CRUD operations on Salesforce data using standard HTTP methods (GET, POST, PATCH, DELETE) with JSON or XML payloads.

Salesforce REST API is a RESTful web service interface that provides access to Salesforce org data and functionality using standard HTTP methods (GET, POST, PATCH, DELETE) and resource-based URIs. It primarily uses JSON as the data format (XML is also supported) and is accessed at endpoints like /services/data/vXX.0/sobjects/Account/. REST API is the most widely used Salesforce API for web applications, mobile apps, and lightweight integrations. It supports CRUD operations, SOQL and SOSL queries, metadata retrieval, file uploads, Composite requests (batching multiple API calls), and SObject Tree for creating related records in a single request.

In Salesforce Einstein and Data Cloud, a technique where the AI retrieves relevant data from your CRM, knowledge base, or Data Cloud before generating a response, grounding the output in your actual business data.

A Salesforce object (part of Order Management) that represents a customer's request to return purchased products, containing details about which items are being returned, the reason, and the expected refund or exchange.

A line item on a Salesforce Return Order that specifies a particular product being returned, its quantity, condition, return reason, and any associated refund amount or exchange details.

In MuleSoft's API-led connectivity approach (part of the Salesforce ecosystem), a system API or process API designed to be reused across multiple integration projects, reducing duplication and promoting consistent data access.

A Salesforce Forecasting option that tracks projected revenue from opportunities, rolling up amounts based on forecast categories and the role hierarchy to give managers and leaders visibility into expected sales revenue.

Revenue Intelligence is a Sales Cloud product that gives sales leaders AI-powered insight into pipeline health, deal trends, and forecast accuracy. Built on CRM Analytics (the platform formerly known as Tableau CRM and originally Einstein Analytics), it analyzes opportunity, activity, and outcome data to surface patterns a human reviewer would struggle to spot - stalling deals, at-risk pipeline, historical forecast bias, and rep-level performance signals - directly inside the Sales Cloud experience.

In Salesforce Products and Pricing, a schedule defined on a product that specifies how revenue will be recognized over time in installments, splitting total revenue across multiple periods for recognition.

A Salesforce record in the role hierarchy that defines a user's position within the organization's data access structure, determining which records they can see based on the 'roll-up' visibility model.

The Salesforce security structure that defines a hierarchy of roles, where users in higher roles automatically gain read access (or read/write, if configured) to records owned by users in roles below them.

A Roll-Up Summary Field is a special field on a master object in a Master-Detail relationship that calculates an aggregate value (COUNT, SUM, MIN, or MAX) from the related detail records. It automatically recalculates whenever detail records are created, updated, or deleted.

In Salesforce Omni-Channel, a configuration that defines how work items are distributed to agents, specifying routing model (most available or least active), priority, capacity weight, and overflow behavior.

In Salesforce Omni-Channel, the underlying system that evaluates routing configurations, agent availability, capacity, and skills to determine which agent should receive each incoming work item.

In Salesforce Omni-Channel, a logical checkpoint in the routing process where work items enter the routing system, typically associated with a queue from which items are distributed to agents.

In Salesforce dashboards and reporting snapshots, the user whose data access permissions determine what records are included in the results, allowing a dashboard to show data from a single perspective regardless of who views it.

In MuleSoft Anypoint Platform (part of the Salesforce ecosystem), the cloud-based management console for deploying, monitoring, and managing Mule applications across CloudHub, Runtime Fabric, and on-premises environments.

Software as a Service - the delivery model Salesforce pioneered where CRM software is hosted in the cloud and accessed via web browser, with no local installation required, automatic updates, and subscription-based pricing.

Sales Cloud is Salesforce's flagship CRM product designed for sales teams. It provides tools for managing Leads, Accounts, Contacts, Opportunities, and the full sales pipeline. Sales Cloud includes features like lead scoring, forecasting, email integration, territory management, and CPQ to help sales organizations close deals faster.

Sales Cloud Everywhere is a Setup feature that extends Sales Cloud functionality beyond the Salesforce interface, allowing sales reps to access CRM data, log activities, and manage their pipeline from any web page they visit, including prospect websites, LinkedIn, and Gmail, through a browser extension.

A Sales Cloud feature set (formerly High Velocity Sales) that provides sales cadences, work queues, Einstein activity capture, and automated outreach sequences to help inside sales reps manage their prospecting pipeline efficiently.

In Salesforce price books, the specific price assigned to a product within a custom price book, which may differ from the list price in the standard price book to reflect discounts, region-specific, or customer-specific pricing.

Salesforce is a cloud-based customer relationship management (CRM) platform that enables companies to manage relationships with customers and prospects across sales, service, marketing, commerce, and other business functions. Founded in 1999, it pioneered the Software-as-a-Service (SaaS) model with a multi-tenant architecture, and has since expanded into a comprehensive ecosystem of cloud products, development tools, and an extensive partner marketplace (AppExchange).

A professional certification offered by Salesforce that validates an individual's skills in configuring and managing a Salesforce org, covering topics like security, data management, automation, analytics, and user setup.

The Salesforce Agentforce Specialist Certification is an intermediate-level Salesforce credential for professionals who build and configure generative-AI features on the Einstein 1 Platform. The exam covers Agentforce agent design, Prompt Builder templates grounded in CRM data, Einstein Trust Layer configuration, Data Cloud readiness for AI, and responsible-AI practices. It is aimed at admins and consultants who deliver AI solutions - not model engineers. Salesforce rebranded this credential from "AI Specialist" to "Agentforce Specialist" in 2026 (article 005298924).

A Salesforce certification that validates foundational knowledge of AI concepts and how they apply within the Salesforce ecosystem, including Einstein features, data quality for AI, and ethical AI considerations.

Salesforce Anti-Money Laundering (AML) is a compliance solution for financial services organizations that enables identity verification, sanctions screening, and adverse media checks for applicants and customers directly within Salesforce. It integrates with third-party AML compliance platforms to help organizations detect, prevent, and report money laundering activities in accordance with regulatory requirements.

Salesforce Anywhere is a real-time collaboration capability that keeps customer data, conversations, and planning accessible within Salesforce records where work originates. Enhanced with Quip document and spreadsheet collaboration, it combines live CRM data with built-in documents, chat, alerts, and customizable business process templates to help teams collaborate and make decisions faster.

The version number of the Salesforce API that a piece of metadata, Apex code, or integration is configured to use, determining which platform features and behaviors are available (e.g., API version 59.0).

The Salesforce Architect Certification track is Salesforce's top-tier credential family for architects who design and lead enterprise Salesforce implementations. It culminates in the Certified Technical Architect (CTA), earned via a review board defense rather than a written exam. The path builds through Application Architect and System Architect - each requiring five domain architect certifications (e.g., Data Architect, Sharing and Visibility Architect, Integration Architect, Identity and Access Management Architect, Development Lifecycle and Deployment Architect) - before candidates can register for the CTA board.

A Salesforce Certificate and Key Pair is a cryptographic credential managed in Salesforce Setup under Certificate and Key Management, used to authenticate API integrations, sign SAML assertions for single sign-on, and establish secure TLS/SSL connections with external systems. Salesforce generates the certificate and private key pair, and administrators can export the certificate to share with external service providers.

Salesforce Certifications are globally recognized professional credentials offered by Salesforce that validate expertise in specific Salesforce domains such as Administration, Development, Architecture, Marketing Cloud, and AI. Professionals earn certifications by passing proctored exams, and they span multiple levels from Associate and Administrator to Architect credentials, providing a structured career advancement path.

Salesforce's e-commerce platform for building and managing online storefronts, supporting both B2B and B2C commerce with product catalogs, shopping carts, checkout, order management, and AI-powered personalization.

The B2B edition of Salesforce Commerce Cloud designed for business buyers, featuring account-based purchasing, negotiated pricing, bulk ordering, reordering, and integration with Sales and Service Cloud.

The B2C edition of Salesforce Commerce Cloud (formerly Demandware) designed for consumer-facing retail, providing storefront templates, merchandising tools, AI-powered product recommendations, and multi-site management.

Salesforce Connect enables users to access and interact with data stored in external systems in real time directly within Salesforce, without copying or duplicating the data. It works by defining external data sources and creating external objects that map to external tables, supporting connections via the OData protocol, cross-org adapters, and custom Apex adapters.

A Salesforce user interface designed for high-volume, fast-paced work environments (like support centers), featuring a tab-based workspace, split views, utility bar, and keyboard shortcuts for efficient multi-record navigation.

The Salesforce Console Integration Toolkit is a browser-based JavaScript API that provides programmatic access to the Salesforce Service Cloud Console in Salesforce Classic, enabling developers to manipulate tabs, control console UI behavior, and execute asynchronous calls. It is used through custom buttons, Visualforce pages, and JavaScript code to extend and customize the console experience for service agents.

A category of Salesforce professional certifications for consultants specializing in specific clouds (Sales Cloud, Service Cloud, Marketing Cloud, etc.), validating expertise in designing and implementing Salesforce solutions for customers.

Salesforce CPQ (Configure, Price, Quote) is a sales tool that automates the creation of accurate quotes for complex products and services. It enables sales teams to configure product bundles based on customer requirements, apply custom pricing rules and volume discounts, and generate professional branded quote documents - all directly within the Salesforce platform on the Opportunity and Quote objects.

Salesforce CRM Call Center is a feature that integrates Salesforce with Computer Telephony Integration (CTI) systems, enabling agents to make and receive calls via a softphone embedded in Salesforce while accessing real-time customer data. It uses call center definition files (XML) to configure connections with various CTI vendors and supports automatic call logging, screen pops, and click-to-dial functionality.

Salesforce CRM Content is an enterprise content management feature that helps organizations organize, share, and manage business documents and files through searchable content libraries. It supports all file types and enables powerful searches across document content, metadata, titles, descriptions, tags, and author names, providing a more structured alternative to attaching files directly to individual records.

Salesforce Developers (developer.salesforce.com) is the official developer community and portal that provides comprehensive documentation, APIs, tools, sample code, and forums for building applications and integrations on the Salesforce platform. It serves as the central hub for developer resources including Apex, Lightning Web Components, REST/SOAP APIs, and Salesforce CLI documentation.

Salesforce DX (Developer Experience) is a set of tools, practices, and infrastructure designed to modernize Salesforce development. It includes the Salesforce CLI, scratch orgs, source-driven development, version control integration, and continuous integration/continuous deployment (CI/CD) capabilities that bring Salesforce development in line with modern software engineering practices.

Salesforce Extensions for Visual Studio Code is an open-source extension pack that provides a full-featured development environment for building on the Salesforce platform within VS Code. It includes tools for Apex development with IntelliSense, Lightning Web Component authoring, SOQL query building, debugging with replay, and integration with Salesforce CLI for deploying to orgs, scratch orgs, and sandboxes.

Salesforce Feedback Management is a solution for collecting, analyzing, and acting on customer feedback across multiple channels, extending the native Salesforce Surveys feature with advanced capabilities. It enables teams to gather CSAT and NPS survey data, map responses directly to Salesforce records, trigger automated follow-up actions, and create personalized customer experiences based on feedback insights.

Salesforce Flow Orchestration enables administrators to create multi-user, multi-step automated processes that can pause and wait for approvals, external data, or assigned work before continuing. It organizes flows into sequential or parallel steps grouped by stages, providing visibility into long-running business processes. As of February 2026, Flow Orchestration became a standard Flow type available without requiring an add-on license.

Salesforce for Nonprofits (formerly known as the Nonprofit Success Pack/NPSP, now Nonprofit Cloud) is a suite of purpose-built applications designed for nonprofit organizations to manage fundraising, donor relationships, program delivery, grantmaking, and volunteer coordination. It provides nonprofit-specific data models for constituent tracking, donation management, outcome measurement, and case management.

Salesforce Foundations is a Setup feature that provides existing Salesforce customers with access to a curated set of capabilities from Sales, Service, Marketing, Commerce, and Data Cloud at no additional cost. It extends the core platform with cross-cloud features to help organizations unify their customer experience.

Salesforce Go is a feature discovery and implementation platform designed for Salesforce administrators to streamline setup and drive user adoption. It groups features into curated sets tied to specific business objectives, helping admins address underused licenses and underexplored capabilities. Salesforce Go is accessible from Setup and guides admins through enabling and configuring features step by step.

An enhanced version of Salesforce Government Cloud that meets FedRAMP High authorization, DoD IL4, and ITAR compliance requirements, hosted in dedicated infrastructure for U.S. government agencies with the strictest security needs.

Salesforce Inbox was an email productivity add-on for Sales Cloud that integrated with Gmail and Outlook to help sales reps automatically log emails, track email opens and link clicks, schedule meetings, and create Salesforce records directly from their inbox. It has been retired, with its core capabilities now incorporated into Sales Cloud's standard email integration features and Einstein Activity Capture.

Salesforce Knowledge is a knowledge management system that allows organizations to create, manage, and share articles with agents and customers. Articles can be categorized, versioned, and published to internal agent views, customer portals, or public websites. Knowledge deflects cases by enabling self-service and speeds up agent resolution times.

Salesforce Maps is a location intelligence add-on that brings geographic visualization and territory management directly into Salesforce. It helps sales and field service teams visualize customer data on interactive maps, design optimized routes, plan territories based on geography and revenue potential, and perform proximity searches to identify nearby accounts or leads.

Salesforce Maps Layers are visual overlays within Salesforce Maps that display collections of Salesforce records (such as accounts, leads, or opportunities) as color-coded location pins on an interactive map. They enable users to visualize geographic patterns in their CRM data, plan routes, and derive location-based insights for territory management and field operations.

Salesforce Marketing Cloud is Salesforce's enterprise digital-marketing platform, bundling tools for email, mobile, advertising, web personalization, and journey orchestration. Core studios include Email Studio, Mobile Studio, Advertising Studio, Web Studio, and Journey Builder, supplemented by Contact Builder, Automation Studio, and Einstein AI features. (Social Studio was part of Marketing Cloud but was retired in November 2024; there is no direct Salesforce replacement - customers typically migrate to partner tools such as Sprinklr or Hootsuite for social marketing.)

Salesforce Mobile App is a Setup area where administrators configure the Salesforce mobile application for iOS and Android. Settings include which navigation items appear in the mobile app, mobile-specific page layouts, push notification configuration, offline access, and branding customization.

Salesforce Order Management is a platform that manages the complete order lifecycle from capture through fulfillment, returns, and refunds, built on an event-driven architecture. It connects commerce, service, and logistics systems with pre-built integrations to Commerce Cloud and native support for Sales and Service Clouds, providing a unified view of order status across all channels.

A Salesforce certification (Platform Developer I and II) that validates a developer's ability to build custom applications on the Lightning Platform using Apex, Visualforce, Lightning components, and SOQL.

A Salesforce Record ID is a system-generated unique identifier assigned to every record in a Salesforce org. It is available in both a 15-character case-sensitive format and an 18-character case-insensitive format (which includes a 3-character checksum suffix). Record IDs are immutable and serve as the primary key for accessing, querying, and relating records throughout the platform.

Salesforce's CRM solution for sales teams that provides lead and opportunity management, forecasting, territory management, sales engagement, CPQ, and AI-powered insights to manage the full sales lifecycle.

Salesforce's customer service platform that provides case management, knowledge base, omni-channel routing, service console, entitlements, Field Service, and AI-powered tools to deliver efficient customer support.

Salesforce Service Oriented Architecture (SOA) is an architectural approach that enables developers to build loosely coupled, discrete services on the Salesforce platform using Apex for integration with external web services, internal systems, and composite services. It supports building scalable on-demand applications through API-driven integrations and service-based design patterns.

Salesforce Shield is a set of four security add-on products that provide enhanced protection for sensitive data in Salesforce. It includes Platform Encryption (encrypts data at rest), Event Monitoring (tracks user activity and API calls), Field Audit Trail (retains field history data for up to 10 years), and Data Detect (identifies and classifies sensitive data patterns across your org). These components can be purchased together or individually.

Salesforce Surveys is a native feature that enables organizations to create, distribute, and analyze surveys to gather customer and employee feedback directly within Salesforce. Survey responses are automatically linked to customer records, eliminating manual data entry and enabling automated follow-up actions based on feedback scores like CSAT and NPS.

Salesforce Voice, also known as Service Cloud Voice, is a native telephony solution that integrates phone calls directly into the Salesforce agent workspace alongside chat, email, and messaging channels. It provides AI-powered real-time call transcription, supervisor monitoring, and unified omnichannel visibility, enabling agents to handle calls without leaving the Service Console.

A Sandbox is a copy of your Salesforce production environment used for development, testing, and training. Sandboxes come in four types: Developer, Developer Pro, Partial Copy, and Full. They allow teams to build and test changes in isolation before deploying to production, protecting live data and users from unfinished or buggy configurations.

Sandbox Templates define which object data is copied from production when creating or refreshing a Partial Copy Sandbox. Administrators select up to 10,000 records per object and choose specific objects to include, allowing teams to create focused test datasets that are smaller than a full copy but still representative of real data patterns.

A standard button in Salesforce record creation forms that saves the current record and immediately opens a new blank record of the same type, streamlining bulk data entry workflows.

A Salesforce feature available in reports, dashboards, list views, and other components that creates a copy of the current item with a new name, preserving the original while allowing modifications to the duplicate.

In Salesforce automation, the ability to set a flow, report, dashboard refresh, or batch Apex job to run automatically at specified intervals (hourly, daily, weekly, monthly) using the Salesforce scheduler.

A Scheduled Action in Salesforce is a time-based automated action that executes at a specified interval before or after a trigger event, such as a record creation date or a field value change. Used within Flow Builder and previously in Process Builder and Workflow Rules, scheduled actions enable administrators to automate follow-ups, reminders, escalations, and other time-sensitive business processes without writing code.

Scheduled Jobs is a Setup page that displays all jobs scheduled to run at specific times, including scheduled Apex classes, scheduled Flows, scheduled reports, scheduled dashboards, and scheduled analytics. Administrators can view the schedule, next execution time, and status of each job.

In Salesforce Field Service, a configuration that defines rules for the scheduling optimizer, specifying priorities like minimizing travel time, respecting skill requirements, and balancing workload when assigning work orders to service resources.

Schema Builder is a Setup tool that provides a visual, drag-and-drop interface for viewing and modifying the data model of a Salesforce org. It displays objects, fields, and relationships as an interactive diagram, allowing administrators to create new objects and fields and define relationships without navigating between multiple Setup pages.

Schema Settings is a Setup page where administrators configure global settings related to the org's data schema, including whether to enable external sharing model features, configure object-level settings, and manage schema-related performance optimizations.

A Scratch Org is a temporary, fully configurable Salesforce environment that developers create from a Dev Hub using Salesforce DX. Scratch Orgs are designed for development and testing, can be spun up in seconds with a specific configuration defined in a JSON file, and are automatically deleted after a maximum of 30 days.

In Salesforce CTI and Service Cloud Voice, the automatic display of a record or page on an agent's screen when an incoming call is received, showing caller information from matching Salesforce records for faster service.

The Salesforce search functionality (powered by the search engine) that lets users find records across objects using keywords, with features like instant results, search filters, searchable fields, and SOSL-based full-text search.

A Salesforce search feature that visually highlights the matching search terms within the returned results, making it easier for users to identify why each record appeared and quickly scan for relevant matches.

A Salesforce configuration that controls which fields appear in search results for each object, defining the columns displayed when records appear in lookup dialogs, search results, and phone lookup results.

The text string entered by a user into Salesforce search, which the search engine tokenizes and matches against indexed fields across objects to return relevant records in the search results.

In Salesforce Marketing Cloud and Data Cloud, a defined group of contacts or individuals filtered by specific attributes, behaviors, or criteria, used for targeted messaging campaigns and personalized engagement.

In Salesforce SOQL, a query pattern that uses a subquery in the WHERE clause to filter parent records based on criteria in a child object, such as selecting accounts where related opportunities meet certain conditions.

Send through External Email Services is a Setup feature that allows organizations to route outbound emails from Salesforce through an external email service like Amazon SES or SendGrid instead of Salesforce's built-in email servers. This provides greater control over email deliverability, tracking, and compliance.

In Salesforce Field Service, an object that defines a type of work your company provides (like installation, repair, or maintenance), linked to service territories, skills, and work types for scheduling purposes.

A Salesforce Field Service object that represents a scheduled appointment for field work at a specific location and time, linked to a work order, service resource, and service territory for dispatch and tracking.

In Salesforce Omni-Channel, a configuration that defines a category of work (like Cases, Chats, or Leads) that can be routed to agents, specifying the Salesforce object and capacity model for that work type.

Service Cloud is Salesforce's customer service platform that helps organizations deliver support across every channel, including phone, email, chat, social media, and self-service portals. It includes Case Management, Knowledge Base, Omni-Channel routing, Entitlements, and AI-powered features to help agents resolve issues quickly and efficiently.

Service Cloud Reports is a Setup area providing pre-built report templates and dashboards for monitoring customer service metrics. These reports cover Case volume, resolution times, agent performance, SLA compliance, customer satisfaction scores, and other key service KPIs.

A Service Cloud feature that integrates telephony directly into Salesforce, providing agents with a built-in softphone, real-time transcription, AI-powered recommendations, and call recording within the Service Console.

The Service Console in Salesforce is a specialized, tab-based workspace designed for customer support agents. It provides a unified interface where agents can view and manage multiple customer records, cases, and interactions simultaneously without navigating between separate pages, improving response times and overall agent productivity.

A Salesforce Service Cloud object that represents a formal support agreement between your organization and a customer, defining the terms, coverage, and entitlements for service over a specified period.

In Salesforce Field Service, the automated scheduling engine that optimizes the assignment of work orders to service resources based on skills, location, travel time, priority, and scheduling policies to maximize efficiency.

A Salesforce Field Service object that represents an individual worker (technician, agent, or contractor) who can be assigned to service appointments, with attributes including skills, location, capacity, and availability.

Service Setup Assistant is a guided Setup wizard that walks administrators through the essential steps of configuring Service Cloud for their organization. It provides a checklist-based approach to enabling features like Case Management, the Service Console, Knowledge, Omni-Channel routing, and customer self-service portals.

A Salesforce Field Service object that defines a geographic region where services are delivered, containing service resources, operating hours, and work rules that govern how work is scheduled and dispatched in that area.

In Salesforce API and authentication, a unique token (string) returned after successful login that identifies an authenticated user session, required in the header of subsequent API calls to authorize requests.

Session Management is a Setup page where administrators view and manage all active user sessions in the org. It provides details on each session including the user, login time, IP address, session type, and the ability to revoke individual sessions for security purposes.

Session Settings is a Setup page where administrators configure global session behavior for the org, including session timeout duration, whether to lock sessions to the originating IP address, clickjack protection, CSRF protection, and whether to force re-login after a session expires.

A Salesforce security setting that defines how long a user session can remain inactive before automatically expiring, requiring the user to log in again, configurable in Session Settings for the org and individual profiles.

Set Up CRM Analytics for Manufacturing is a Setup wizard that deploys pre-built CRM Analytics dashboards and datasets tailored for manufacturing organizations. These analytics cover demand forecasting, account-based revenue tracking, and sales agreement monitoring specific to the Manufacturing Cloud data model.

In Salesforce Apex and Visualforce development, methods in a controller class that receive values from user input on a Visualforce page, following the naming convention set[PropertyName]() for data binding.

Settings in Salesforce Setup refers to the broad collection of configuration pages organized under the Setup menu where administrators control how the platform and its features behave for the entire org. These are grouped into categories such as Company Settings (company info, fiscal year, business hours), Security Settings (password policies, session settings, field-level security), User Management Settings, Feature Settings (Sales, Service, Marketing feature controls), Platform Settings (custom code, API, environments), and many more. Each individual settings page controls specific aspects of the platform's behavior.

The Salesforce administration area (accessed via the gear icon) where admins configure org settings, manage users, customize objects and fields, build automation, set security policies, and control platform features.

Setup Home is the landing page of the Salesforce Setup menu that provides a centralized overview of the org's health, recent setup changes, and recommended actions. It includes links to the most commonly used setup pages, the setup search bar, and widgets showing adoption metrics, feature recommendations, and release updates.

Setup with Agentforce (Beta) is an AI-assisted Setup experience that uses Agentforce to help administrators configure Salesforce using natural language instructions. Admins can describe what they want to accomplish, and the AI agent guides them through or performs the configuration steps automatically.

In Salesforce sharing architecture, an internal group automatically created and maintained by the system to facilitate sharing rules, portal/community access, and territory-based sharing behind the scenes.

A Salesforce feature that allows a single event or task to be related to multiple contacts simultaneously (up to 50), creating a shared activity record rather than requiring separate activities for each contact.

The Salesforce data access framework that determines which users can see and edit which records, encompassing org-wide defaults, role hierarchy, sharing rules, manual sharing, teams, and territory-based sharing.

In Salesforce sharing, a system-managed group used behind the scenes to implement sharing rules and territory assignments, automatically maintained by the platform when sharing configurations change.

The overall Salesforce sharing architecture for an org that includes org-wide defaults, role hierarchy, sharing rules, manual sharing, Apex sharing, and teams, collectively defining record-level access for all users.

A Sharing Rule in Salesforce grants additional record access to specific groups of users beyond what is defined by the org-wide default sharing settings and the role hierarchy. Sharing Rules can be criteria-based (sharing records that match specific field values) or owner-based (sharing records owned by certain users or roles).

Sharing Settings is a Setup page where administrators define the organization-wide default (OWD) access levels for each object and create sharing rules to extend access beyond the defaults. OWD settings control the baseline visibility (Private, Public Read Only, Public Read/Write) for records across the org.

In Chatter, Sharing (as an action on a feed post) lets a user re-surface an existing post to another audience - a Chatter group, a record's feed, or their own profile feed - so people outside the original post's scope see it. Unlike a Comment (which stays on the original post) or a Like (which is a reaction), Sharing propagates the post to a new feed context while preserving a reference back to the original.

A Workforce Engagement feature in Salesforce Service Cloud that allows supervisors to create, assign, and manage agent work shifts, ensuring adequate staffing coverage across time zones and service channels.

In Salesforce Workforce Engagement (Shift Management), a reusable template that defines a recurring pattern of shifts over a set period, automating the creation of consistent agent schedules week over week.

Shift Scheduling is a Setup feature for configuring shift-based work scheduling in Salesforce, primarily used in Workforce Engagement Management. It allows administrators to define shift patterns, scheduling rules, and agent preferences to create optimized work schedules for service center teams.

A Shift Template in Salesforce Workforce Engagement (and Field Service) is a reusable definition of shift details - start/end times, meal breaks, job profile, territory, skills needed - that admins apply when generating recurring shifts. Rather than recreating the same shift structure every week, the template captures the shape once and the scheduling engine stamps actual Shift records from it as needed. Templates pair with Shift Patterns (which define the recurrence cadence) to drive automated scheduling.

A toggle option in Salesforce report views that shows or hides the individual record rows behind summary or matrix report groupings, letting users switch between seeing aggregated totals and detailed record data.

In Salesforce Classic, the left panel of the interface that displays recent items, shortcut links, messages, custom components, and quick-create options, providing navigation and contextual information alongside the main content area.

Single Sign-On (SSO) Settings is a Setup page in Salesforce where administrators enable and configure federated authentication, allowing users to log in through an external Identity Provider (IdP) rather than entering Salesforce credentials directly. The page provides options to enable SAML-based SSO, specify the IdP's entity ID and login/logout URLs, upload the IdP's signing certificate, configure the SAML assertion attributes, and set the identity type and location. Salesforce supports SAML 2.0 for SSO and can act as both a Service Provider (SP) and an Identity Provider. SSO Settings works alongside Auth. Providers for OAuth-based social sign-on and OpenID Connect integrations.

A Salesforce web content management system (now part of Experience Cloud) that provided a drag-and-drop website builder for creating branded, dynamic web pages hosted on the Salesforce platform without code.

Salesforce Sites (Force.com Sites) is a feature that allows you to create public-facing web pages hosted on the Salesforce platform, accessible without login, that can display Salesforce data through Visualforce pages.

Sites and Domains is a Setup page for managing all custom domains and site configurations for the org, including Experience Cloud site URLs, Salesforce Sites, and custom domain mappings. Administrators can configure branded URLs, SSL certificates, and DNS settings for all web properties.

A Skeleton Template in Salesforce is a minimal HTML/Visualforce template structure that provides the basic page framework (such as HTML doctype, head, and body tags) without predefined content or styling. It is used as a starting point when developers want full control over the page layout and markup rather than using a standard Salesforce template with built-in headers and sidebars.

A Skill in Salesforce is a standard object that represents a specific competency, certification, or capability that can be assigned to a Service Resource (a field-service technician) or used as a routing criterion for Omni-Channel work distribution. Each Skill record holds a MasterLabel, an optional DeveloperName, and a Description; the actual mapping of skills to resources lives on the ServiceResourceSkill junction object, which captures effective start and end dates and a SkillLevel rating. Skills are the foundation of skills-based work assignment in two distinct Salesforce features: Field Service uses Skills to ensure service appointments are dispatched only to technicians qualified to perform the work (HVAC certification, language fluency, security clearance), and Omni-Channel uses Skills (modeled in a related but separate framework) to route Cases, Leads, or Chats to agents whose skill profiles best match the work requirements. The same vocabulary of skills can drive both systems, giving service organizations a unified competency model across digital channels and on-site work.

Slack is a messaging and collaboration platform owned by Salesforce that organizes team communication into channels, direct messages, and huddles. Integrated with Salesforce, Slack allows users to receive CRM notifications, search Salesforce records, and take actions on records directly from their messaging workspace.

Slack Apps Setup is a Setup page for managing Salesforce-built Slack applications that extend the integration between Salesforce and Slack workspaces. Administrators can install, configure, and control permissions for Slack apps that bring CRM functionality directly into Slack channels.

Slack Channels for Records is a Setup feature that automatically creates dedicated Slack channels linked to Salesforce records such as Accounts, Opportunities, or Cases. These channels bring together all stakeholders for real-time collaboration directly connected to the CRM data.

In Salesforce Marketing Cloud and Email Studio, a reusable block of content (text, HTML, images) that can be inserted across multiple email templates and content areas, enabling consistent messaging without duplication.

In Salesforce development, the XML-based messaging protocol used by the Salesforce SOAP API for structured data exchange, where developers use WSDL files to generate client code for API interactions.

Salesforce SOAP API is a web service interface based on the SOAP (Simple Object Access Protocol) standard that uses XML-formatted request and response messages defined by WSDL (Web Services Description Language) files. Salesforce provides three main WSDLs: the Enterprise WSDL (strongly-typed, specific to the org's schema), the Partner WSDL (loosely-typed, generic across orgs), and the Metadata WSDL (for metadata operations such as deployments and retrievals). The Tooling WSDL is also available for developer tool integrations. SOAP API supports all standard CRUD operations (create, retrieve, update, upsert, delete, undelete), queries via SOQL and SOSL, metadata describe calls, and utility operations like merge, convertLead, and getUpdated. It is commonly used in enterprise integrations, particularly with Java and .NET platforms.

An sObject (Salesforce Object) is the Apex representation of a Salesforce standard or custom object. In Apex code, sObject is the generic data type that can represent any record, and specific sObjects like Account, Contact, or MyCustomObject__c are strongly-typed subtypes. Developers use sObjects to create, read, update, and delete records programmatically.

In Salesforce Health Cloud, data fields and related objects that capture non-clinical factors affecting a patient's health (like housing, food security, transportation, and education), supporting whole-person care coordination.

In Salesforce CTI and Service Cloud Voice, a software-based phone interface displayed in the Salesforce utility bar that allows agents to make, receive, and manage calls without a physical phone, featuring click-to-dial and call controls.

In Salesforce Open CTI, a JavaScript connector that links the browser-based softphone interface to the telephony provider's system, handling call events and enabling communication between Salesforce and the phone system.

A legacy Salesforce CTI component (replaced by Open CTI) that was a browser plugin required to connect a user's desktop phone system to the Salesforce interface for screen pops and call management.

Software as a Service - the cloud delivery model pioneered by Salesforce where applications are hosted centrally, accessed via web browser, maintained by the vendor, and sold as subscriptions rather than installed software.

A Salesforce Knowledge-predecessor object (primarily used in Classic) that stores answers to common customer questions, searchable by agents and customers, largely replaced by Salesforce Knowledge articles in Lightning.

In Salesforce Classic (Solutions feature), a user role responsible for reviewing, editing, and publishing solutions to ensure quality and accuracy before they become visible to agents and customers in the solutions database.

Salesforce Object Query Language, a SQL-like query language specific to Salesforce for querying records from a single object or multiple related objects through relationship queries. SOQL supports parent-to-child subqueries, child-to-parent dot-notation traversal (up to five levels), filters, sorting, aggregation, and grouping. It is used in Apex code, APIs, and developer tools.

Salesforce Object Search Language, a search language that performs text searches across multiple objects simultaneously using the Salesforce search index, supporting wildcards, operators, and returning records from different objects in one query.

In Salesforce Reporting Snapshots, the specific report whose results are captured at each scheduled execution, with columns mapped to fields on a target custom object for historical trend storage.

A Salesforce DX development methodology where the source of truth for metadata lives in a version control system (like Git) rather than in the org, enabling modern DevOps practices with scratch orgs and CI/CD pipelines.

In Salesforce CPQ or contract management, specific terms and conditions attached to a quote, order, or contract that define special pricing, discounts, clauses, or exceptions beyond the standard agreement terms.

In Salesforce opportunity management, a calculated field or metric that tracks how long an opportunity has remained in its current stage, used to identify stalled deals and optimize the sales pipeline.

A related list on the Salesforce Opportunity object that tracks changes to the opportunity's stage over time, recording each stage transition with dates to provide visibility into deal progression.

A Standard Object is a pre-built database table that comes included with every Salesforce org. Standard Objects like Account, Contact, Opportunity, Case, and Lead provide the foundational data model for CRM processes. They come with predefined fields, relationships, and behaviors, though administrators can customize them with additional fields and configurations.

In Salesforce price books, the price of a product as defined in the Standard Price Book, serving as the baseline list price from which custom price book entries may offer different pricing.

The default Salesforce price book that contains the standard (list) prices for all products, required as a baseline before products can be added to custom price books with alternate pricing.

State and Country/Territory Picklists is a Setup feature that replaces free-text state and country fields with standardized picklist values based on ISO codes. This improves data quality by preventing inconsistent entries like "CA," "Calif," and "California" for the same state.

In Salesforce Billing, a document or record summarizing a customer's account balance, charges, payments, and credits over a period, providing a consolidated view of financial transactions.

Static Resources is a Setup page for managing files uploaded to Salesforce that can be referenced in Visualforce pages, Lightning components, and other customizations. Static resources can include JavaScript libraries, CSS stylesheets, images, and ZIP archives containing multiple files, with a maximum size of 5 MB per resource.

In Salesforce, a picklist field present on many standard objects (like Case, Lead, Opportunity) that tracks the current state of a record through its lifecycle (e.g., New, In Progress, Closed).

In Salesforce search, the automatic reduction of search terms to their root word form (e.g., 'running' to 'run') to broaden search results and return matches regardless of word endings or conjugations.

Storage Usage is a Setup page that displays the org's data storage and file storage consumption, broken down by object. It shows how much of the total allocation is used, which objects consume the most storage, and helps administrators identify opportunities to archive or delete data to stay within limits.

In Salesforce Flow Builder, a flow element that calls another flow as a reusable component within the current flow, passing input variables and receiving output variables, enabling modular flow design.

In Salesforce managed packaging, a customer or organization that has installed a managed package from the AppExchange into their Salesforce org, receiving updates and patches from the package publisher.

In Salesforce managed packaging, the customer's Salesforce org where a managed package has been installed, which receives push upgrades and patches from the package developer's org.

In Salesforce Customer Success or Industries, a structured plan that outlines goals, milestones, and activities to guide a customer through adoption, implementation, or optimization of Salesforce products.

In Salesforce Service Cloud, a Knowledge article that is automatically recommended to an agent based on the case's subject, description, or other field values, surfaced through Einstein Article Recommendations or suggested articles settings.

A Summary Field, also known as a Roll-Up Summary Field, is a read-only field on a master object in a master-detail relationship that automatically calculates aggregate values from related child records. It supports functions including COUNT, SUM, MIN, and MAX, and can include filter criteria to limit which child records are included in the calculation.

A Salesforce report format that groups records by row values and includes summary fields (sum, average, min, max) at each grouping level, useful for totaling data by categories like region or stage.

A Salesforce Trailhead credential earned by completing a complex, multi-step hands-on project that requires applying multiple skills in a realistic scenario, demonstrating deeper expertise than standard badges.

In Salesforce Service Cloud Voice, the ability for a supervisor to forcibly disconnect an agent from an active call, typically used in quality management or emergency situations within the contact center.

A Survey in Salesforce (Survey in the API) is a standard object in Salesforce Surveys (and the more advanced Salesforce Feedback Management product) that represents a single survey definition - its name, current status, default language, and the metadata that drives the survey-taking experience. Each Survey is the parent of a rich data model: Survey Versions track changes over time, Survey Pages organize the survey into sections, Survey Questions define individual prompts (multiple choice, single select, free text, NPS, rating, ranking, slider, file upload), Survey Invitations track who was asked to take the survey through which channel, and Survey Question Responses capture each individual answer when a respondent completes the survey. Surveys can be sent through email, embedded in Experience Cloud sites, triggered automatically by Flow when a Case is closed (CSAT) or an Opportunity is won, or distributed through public links - with all responses centralized in the same data model regardless of distribution channel for unified analysis.

A Survey Question in Salesforce (SurveyQuestion in the API) is a standard object representing a single prompt within a Survey - the actual question that respondents answer. Each Survey Question record holds a parent SurveyId (or SurveyVersionId), a parent Survey Page, a Name (the question text), a QuestionType (Single Select, Multi Select, Free Text, Long Text, Numeric, Rating, Slider, NPS, Date, Time, File Upload, Image, Ranking), an order/sequence within its page, an IsRequired flag, and validation settings. For choice-based questions, related SurveyQuestionChoice records hold the available answer options; for matrix and ranking question types, additional metadata structures support sub-questions and order. The Survey Question is where the substance of every survey lives - choosing the right question types, ordering, and required flags directly determines completion rates and data quality. Survey Questions can be referenced across multiple Survey Versions, enabling year-over-year comparison of the same metric (a CSAT question on the 2025 survey can be the same Survey Question on the 2026 survey, supporting longitudinal trend analysis).

A Survey Question Response in Salesforce (SurveyQuestionResponse in the API) is a standard object that captures a single respondent's answer to a single Survey Question. Each Survey Question Response record holds a parent SurveyResponseId (the completion record for that respondent's full survey submission), a SurveyQuestionId, a ChoiceId for choice-based questions (or null for free-text and other types), the literal text or numeric value the respondent provided, a CompletionDate, and references back to the parent Survey, Survey Version, and Survey Subject. Survey Question Responses are the row-level data that populate every Salesforce Surveys analysis - when a respondent completes a five-question survey, Salesforce creates one Survey Response record plus five Survey Question Response records. Aggregating Survey Question Responses by Survey Question reveals the distribution of answers (50% chose Option A, 30% Option B, 20% Option C); aggregating across Survey Versions reveals trends over time. Survey Question Responses also link to the parent record (Case, Account, Contact) through Survey Subject, enabling cross-object reporting like 'average CSAT for Cases owned by each agent in the past quarter'.

A Salesforce object that stores an individual respondent's answers to a Salesforce Survey, including their responses to each question, submission timestamp, and any associated record like a case or contact.

In Salesforce, Sync is the process of keeping records consistent between Salesforce and external systems - email, calendars, ERPs, marketing platforms - so a change in one place is reflected in the other. Modern Salesforce syncs run on Einstein Activity Capture (for email and calendar, replacing the retired Lightning Sync), Data Cloud Activations (for unified-profile data), Marketing Cloud Connect (for campaign sync), and custom integrations via the Platform Event, Change Data Capture, and REST/Bulk APIs.

In Salesforce, Atom/RSS web feeds that allow external applications to subscribe to and consume Salesforce data updates, enabling content distribution from Salesforce Sites or Experience Cloud pages.

The default Salesforce administrative profile with the highest level of access to all setup and configuration features, data, and functionality in the org, responsible for managing users, security, and customizations.

In Salesforce development (Classic), the Developer Console's log viewer or debug log feature that records detailed execution information for Apex code, workflow rules, validation rules, and system events for troubleshooting.

System Overview is a Setup page that provides a high-level summary of the org's usage against key platform limits, including API calls, storage, custom objects, rules, flows, and other configurable components. It helps administrators monitor the org's capacity and avoid hitting governor limits.

In Salesforce development lifecycle, end-to-end testing of the complete Salesforce implementation including integrations, automation, security, and user workflows to verify the system works correctly as a whole before deployment.

A navigation element in Salesforce that provides quick access to an object's home page, app, web URL, Lightning component, or Visualforce page, appearing in the navigation bar or App Launcher.

Tableau is a data-visualization and analytics platform owned by Salesforce (acquired in 2019). Users connect to SQL databases, cloud warehouses, flat files, and Salesforce objects via native connectors, then build interactive dashboards by dragging dimensions and measures onto visualization shelves. Tableau's stack includes Tableau Desktop (authoring), Tableau Cloud (hosted analytics), Tableau Server (self-hosted), Tableau Pulse (AI-powered monitoring), and Tableau Embedded Analytics (white-label charts embedded in other apps).

The simplest Salesforce report format that displays a flat list of records in rows and columns without any groupings or summaries, essentially a table view of filtered data for basic record listings.

In Salesforce, a Tag is a user-defined keyword attached to a record to aid personal categorization and search. There are two Tag types: Personal Tags (private to the user who applied them) and Public Tags (visible to everyone in the org). Tags don't enforce values from a picklist - users type any keyword - which makes them flexible for ad-hoc organization but poor for structured reporting. They're commonly used for "read later" bookmarking, personal pipeline marking, and quick record-grouping outside formal picklists.

A Tag Cloud in Salesforce is a visual display element in Salesforce Classic that shows the personal or public tags a user has applied to records. Tags appear in different font sizes based on how frequently they are used, creating a weighted visual representation where the most-used tags appear largest. Tag Clouds help users quickly identify and navigate to commonly tagged records. This is a UI feature within Salesforce Classic's tagging functionality, not a cloud computing product.

A Task in Salesforce is a standard activity record that represents a to-do item, follow-up, phone call, or any other action a user needs to complete and track. Tasks store details like the subject, due date, priority, status, and assigned owner, and link to related records through two polymorphic relationships: WhoId (a Lead or Contact) and WhatId (any related object such as an Account, Opportunity, Case, or custom object). Together with Events, Tasks form the Activity timeline that appears on every record's detail page in Lightning Experience. Tasks can be created manually by users, generated automatically by Workflow Rules, Process Builder, or Flow, or logged retrospectively through features like Email-to-Task and call logging via CTI integrations. Closed Tasks roll up into Activity History on the parent record, providing a complete audit trail of customer touchpoints over time.

In the Salesforce Classic console, the links displayed in the footer (task bar) area of the console that provide quick access to common actions like new record creation without leaving the current workspace.

Tasks is a Setup area where administrators configure the behavior of task records across the org, including default task assignment notifications, task close settings, and whether completed tasks are archived. Tasks are a core activity tracking feature used to manage to-do items and follow-ups.

Teams Integration is a Setup page for configuring the integration between Salesforce and Microsoft Teams. It enables features like Salesforce record sharing in Teams channels, CRM data access from the Teams interface, and meeting notifications synced between the two platforms.

In Salesforce Shield Platform Encryption, an org-specific secret generated by the customer that combines with Salesforce's master secret to derive the encryption keys used to encrypt and decrypt the org's data.

In Salesforce Territory Management (Enterprise Territory Management), a defined geographic or logical area used to organize accounts and assign sales reps, determining account access and forecast rollup structures.

In Salesforce Maps and Territory Management, the process of designing, modeling, and optimizing sales territories based on geography, account attributes, and workload balance to maximize coverage and sales effectiveness.

In Salesforce Apex development, a metric that shows which Apex classes and triggers are covered by unit tests and which lines of code are exercised during test execution, with a 75% minimum org-wide coverage required for deployment.

A Test Class in Salesforce is an Apex class written specifically to verify that custom code - including triggers, classes, and controllers - works correctly under various conditions. Salesforce requires a minimum of 75% code coverage from test classes before any Apex code can be deployed to a production environment, making them a mandatory part of the development lifecycle.

Test Deliverability is a Setup tool that sends a test email from Salesforce to a specified address to verify that outbound email delivery is working correctly. It helps administrators diagnose email deliverability issues by confirming that emails can successfully leave the Salesforce platform and reach recipients.

In Salesforce AppExchange, a feature that allows potential customers to try a managed package in a pre-configured trial org to evaluate its functionality before purchasing, providing a hands-on preview.

In Salesforce Apex, a method annotated with @isTest that verifies Apex code behaves correctly by setting up test data, executing operations, and using System.assert methods to validate expected outcomes.

In Salesforce development, a dedicated org used for testing purposes (like a sandbox or scratch org) where developers and QA teams validate customizations, integrations, and configurations before production deployment.

Text is a Salesforce field data type that stores a single line of alphanumeric content up to 255 characters. It's the most common field type for short strings - names, codes, brief descriptions, external IDs - and the SOQL WHERE-clause default for equality comparisons. Text fields support unique constraints, case-sensitivity rules, default values, and can be set as External ID for upsert operations. For longer content Salesforce offers Text Area (255 chars, multi-line), Long Text Area (up to 131,072 chars), and Rich Text Area (HTML-formatted).

A Salesforce field data type that stores multi-line plain text up to 255 characters, suitable for short descriptions or notes that may need line breaks but don't require the larger Long Text Area capacity.

Themes and Branding is a Setup page where administrators customize the visual appearance of Lightning Experience, including the org's logo, brand color, loading page background, and default banner image. These settings help organizations align the Salesforce interface with their corporate brand identity.

In Salesforce workflow rules and processes, a time-based trigger that schedules workflow actions to execute at a specified time before or after a date field value on the record (like 3 days before Close Date).

In Salesforce workflow rules, an automated action (field update, email alert, task, outbound message) scheduled to execute at a future time relative to a date field, queued by a time trigger rather than firing immediately.

In Salesforce governor limits and API integrations, the maximum time allowed for a transaction, callout, or query to complete before Salesforce terminates it, preventing long-running processes from consuming shared resources.

Token Exchange Handlers is a Setup page for managing Apex classes that handle OAuth token exchange flows. These handlers implement custom logic for exchanging tokens between identity providers and Salesforce, enabling complex authentication scenarios like token delegation and cross-cloud identity federation.

Tools is a Setup section that provides access to various developer and administrator tools within Salesforce, including the Developer Console, debug log viewers, deployment tools, and other utilities that assist with building, testing, and troubleshooting customizations.

In Salesforce Ideas, a list view that ranks ideas by the highest cumulative vote count since the Ideas community was launched, surfacing the most popular feature requests or suggestions of all time.

A Topic in Salesforce is a standard object that represents a tag or theme used to categorize Chatter posts, Knowledge articles, records, files, and other content across the platform. Each Topic record holds a Name, an optional Description, and a TalkingAbout counter that tracks how often the Topic has been discussed recently. Topics are linked to specific items through the TopicAssignment junction object, which records which Chatter post, article, or record was tagged with which Topic. This shared tagging vocabulary lets users surface related content across object boundaries - clicking a Topic surfaces every Chatter post, knowledge article, and record tagged with it, regardless of their underlying objects. Topics are crowdsourced by default: any user can apply or create Topics, which makes them useful for capturing emergent themes (a product issue, a competitive scenario, a regional event) without requiring admin configuration. Topics also drive Experience Cloud navigation, where Topic pages serve as landing destinations for community content organized around themes rather than objects.

In Salesforce Chatter, a feature that uses hashtags (#) to categorize and organize posts by subject, allowing users to follow specific topics and discover related conversations across the org's feed.

In Salesforce Trailhead, a curated sequence of modules and projects that guides learners through a structured learning path on a specific topic (like Admin Beginner or Developer Intermediate), building skills progressively.

Trailhead is Salesforce's free online learning platform that teaches Salesforce skills through interactive modules, projects, and superbadges. It gamifies learning with points, badges, and ranks, and covers everything from basic CRM concepts to advanced development topics. Trailhead is used by administrators, developers, business users, and anyone wanting to learn Salesforce.

A free, pre-configured Salesforce Developer Edition org provisioned through Trailhead specifically for completing hands-on challenges and projects, providing a safe environment for learning without affecting real data.

In Salesforce Einstein and AI, the historical dataset used to train a machine learning model, which the model analyzes to learn patterns and relationships that it then uses to make predictions on new data.

A Training Phrase (also called a training utterance) in Salesforce Einstein Bots is an example sentence or expression that an administrator provides to teach the bot's Natural Language Understanding (NLU) model how to recognize a specific intent. For each intent, multiple training phrases are added to cover the different ways a customer might express the same request. For example, the 'Check Order Status' intent might include training phrases like 'Where is my order?', 'Track my shipment', 'I want to check my delivery status', and 'Order update.' The more diverse and representative the training phrases, the better the bot can accurately classify incoming messages.

Transaction Security is a Setup feature in Salesforce Shield that allows administrators to create policies that monitor real-time events and take automatic action when suspicious activity is detected. Policies can block actions, require multi-factor authentication, freeze users, or send notifications based on conditions like data export volume or login location.

In Salesforce Apex, a single unit of execution that includes all DML operations, SOQL queries, callouts, and other operations between the start and end of an execution context, subject to governor limits as a group.

In Salesforce B2B Commerce, a financial transaction that occurs during the checkout process when a buyer completes their purchase, encompassing payment processing, order creation, and confirmation.

Translation Language Settings is a Setup page where administrators manage the languages available for translation in the Translation Workbench. It allows admins to enable specific languages for translating custom labels, picklist values, help text, and other translatable metadata components in the org.

A Salesforce setup tool that manages the translation of custom labels, picklist values, field names, page layouts, and other customizable text into multiple languages for organizations with multilingual users.

In Salesforce Chatter, a feature that highlights topics (hashtags) that are currently receiving the most posts and engagement across the organization, helping users discover what subjects are top of mind.

An Apex Trigger is a piece of Apex code that executes before or after data manipulation language (DML) events on Salesforce records, such as insert, update, delete, merge, upsert, and undelete. Triggers allow developers to perform custom actions when records are modified, such as validating data, updating related records, or calling external services.

In Salesforce Apex triggers, system-provided variables (like Trigger.new, Trigger.old, Trigger.isInsert, Trigger.isBefore) that provide context about the records being processed and the type of DML operation that fired the trigger.

In Salesforce, the action of permanently removing all records from a custom object while preserving the object's metadata, fields, and configuration, used to clear data without deleting the object definition itself.

Trusted URL and Browser Policy Violations is a Setup page that logs instances where browsers blocked content due to Content Security Policy (CSP) violations. It helps administrators identify and resolve issues where custom JavaScript, iframes, or external resources are being blocked by the browser's security policies.

Trusted URLs is a Setup page where administrators add external URLs to the Content Security Policy (CSP) allowlist, permitting Salesforce Lightning pages to load scripts, styles, images, and frames from those domains. Without an allowlist entry, browsers block external content for security reasons.

Trusted URLs for Redirects is a Setup page where administrators specify external URLs that Salesforce is allowed to redirect users to. This prevents open redirect vulnerabilities by ensuring that users can only be redirected to pre-approved domains from Salesforce pages and custom links.

In Salesforce Chatter, the action of unsubscribing from a record's or user's feed to stop receiving updates about their activity in your Chatter news feed, reversing a previous follow action.

In Salesforce Data Cloud, a standardized data schema that maps customer data from multiple sources into a common structure, enabling consistent analytics, segmentation, and activation across the unified customer profile.

In Salesforce Health Cloud or Customer 360, a composite score that aggregates multiple health or engagement indicators into a single metric, giving care teams or account managers a quick overview of status.

In Salesforce development, the API Name (also called Developer Name) assigned to custom objects, fields, and components that uniquely identifies them in code, formulas, and API operations, following the convention like My_Field__c.

In Salesforce Trailhead, a single instructional lesson within a module that covers a specific topic, typically consisting of reading content followed by a hands-on challenge or quiz to test understanding.

In Salesforce Apex, a test method that validates code functionality by creating test data, running the code under test conditions, and verifying results with assertions, required for a minimum 75% code coverage to deploy.

A premium Salesforce CRM edition that includes all Enterprise Edition features plus unlimited customization, 24/7 premier support, expanded storage, multiple sandboxes, and access to additional platform services.

A Salesforce package that bundles components for distribution but does not have namespace protection or IP restrictions, meaning all components are fully editable and visible in the installing org, typically used for templates or open-source distribution.

In Salesforce DML operations and automation, an operation that modifies existing records in the database, changing field values on one or more records of an object, executable through Apex, flows, or the API.

In Salesforce B2B Commerce, the process of upgrading a product selection during checkout, such as choosing a higher tier or adding premium options to the cart before completing the purchase.

In Salesforce managed packaging, the process of installing a newer version of a managed package over an existing installation, which applies new features, fixes, and changes while preserving subscriber customizations.

In Salesforce data management, the process of importing data from external files (CSV, XML) into Salesforce using tools like Data Loader, Import Wizard, or the Bulk API.

URL is a Salesforce field data type that stores a web address as a clickable hyperlink - the field displays as a link on record pages, opens in a new tab when clicked, and stores the raw URL as text underneath. URL fields accept any valid URL syntax (no validation beyond basic format) and are the right type for website references, video links, document URLs, and any external resource a record should link to. Unlike a Text field with a URL inside, the URL field type renders as a live hyperlink without a formula.

In Salesforce Service Cloud Entitlement Management, an entitlement type that grants a customer a limited number of support interactions (like 10 cases or 5 phone calls), decrementing with each usage rather than expiring by date.

A User in Salesforce is a standard object that represents an individual login account in the org - every person who signs into Salesforce has exactly one User record. The User object stores authentication and profile data including username, email, name, alias, time zone, locale, federation ID, and the assigned Profile that controls baseline permissions. Each User is also associated with a Role (for record sharing), one or more Permission Sets and Permission Set Groups (for additive access), a User License (which determines available features and pricing), and a manager (for hierarchy-based reporting and approvals). Users own records - almost every standard and custom object has an OwnerId field that references a User. Beyond standard logins, the User object also represents Customer Community Users, Partner Users, Guest Users, Site Users, Integration Users, and Automated Process Users, each tied to a specific User License type. Active User counts directly drive Salesforce billing, so admins must deactivate (not delete) departed users to free up licenses while preserving historical record ownership.

In Salesforce project delivery, the testing phase where end users validate that the Salesforce implementation meets business requirements and works correctly in real-world scenarios before final sign-off and go-live.

In Salesforce, the visual presentation layer that users interact with, including Lightning Experience (modern), Salesforce Classic (legacy), the Salesforce Mobile App, and custom interfaces built with Visualforce or LWC.

A User License is the base license that defines what kind of Salesforce login a user has - Salesforce (full CRM), Salesforce Platform (custom-app-only), Chatter Free, Chatter External, Customer Community, Customer Community Plus, Partner Community, and others. It gates which objects and features the user can ever access; Permission Sets, Permission Set Licenses, and Feature Licenses layer on top to grant specific capabilities within the user type. A user has exactly one User License, assigned at user creation.

User Management Settings is a Setup page where administrators configure global settings for user account management, including enabling enhanced profile management, scrambling user data for deactivated users, and controlling the user self-deactivation feature.

In Salesforce profiles and permission sets, a specific system permission that enables a particular capability for assigned users, such as API Enabled, View Setup and Configuration, Manage Users, or Customize Application.

A Salesforce feature that automates the creation, update, and deactivation of user accounts in third-party applications connected via Connected Apps, synchronizing user lifecycle management across systems using SCIM protocol.

Users is a Setup page that displays all user records in the org and provides tools to create, edit, freeze, and deactivate user accounts. It shows each user's name, username, profile, role, license type, and active status, serving as the central hub for user management.

In Salesforce Einstein Bots and NLP, a sample phrase or sentence that represents how a user might express a specific intent, used to train the bot's language model to recognize variations of the same request.

A Validation Rule in Salesforce is a formula-based rule that prevents users from saving a record if certain conditions are not met. Validation Rules enforce data quality by checking field values against specified criteria and displaying an error message when the data does not comply.

In Salesforce managed packages and metadata, a numbered iteration of a component or package (like API version 59.0 or package version 1.5) that identifies a specific release with its capabilities and changes.

In Salesforce development, the practice of tracking metadata changes in a version control system (like Git) using Salesforce DX source format, enabling collaboration, change history, branching, and CI/CD workflows.

In Salesforce, a View (most commonly used as "List View") is a saved, named configuration for displaying records from an object. It defines the columns shown, the filter criteria that limit which records appear, a sort order, and a scope (My records, All records, or a shared group). Users create personal Views for their own use, admins can publish Views shared with groups or org-wide, and the same concept extends to Report views (filter + grouping + visualization) and Dashboard views (filtered dashboards per viewer).

View Setup Audit Trail is a Setup page that displays a log of the most recent 20 setup changes made in the org (with the ability to download the last 180 days of changes as a CSV). It records who made each change, what was changed, and when, providing an audit trail for configuration governance.

In Salesforce Visualforce, the state data that is serialized and stored in a hidden form field on the page, preserving controller data between server requests so the page maintains its context during postbacks.

Visualforce is Salesforce's legacy markup language for building custom user interfaces. It uses a tag-based syntax similar to HTML and can be paired with Apex controllers to create pages with custom layouts, logic, and data access. While still supported, Salesforce recommends Lightning Web Components for new development.

Visualforce Components is a Setup page that lists all custom Visualforce components in the org. Visualforce components are reusable UI building blocks that can be embedded in Visualforce pages, similar to how Lightning Web Components work in the Lightning framework. They encapsulate markup and controller logic for reuse.

In Salesforce Visualforce development, an Apex class that provides the data and handles user actions for a Visualforce page, available as standard controllers (auto-generated for objects) or custom controllers written in Apex.

In Salesforce Visualforce, the sequence of phases a page goes through during each server request: view state restoration, expression evaluation, controller method execution, and view state saving for the response.

A Salesforce UI component written in Visualforce markup (HTML-like tags with Apex binding) that renders dynamic web pages within the Salesforce platform, used for custom interfaces, email templates, and embedded content.

Voice is a Setup area for configuring Salesforce Service Cloud Voice, which integrates telephony directly into the Service Console. It enables features like real-time call transcription, AI-powered call recommendations, automatic call logging, and omni-channel routing of phone calls alongside other service channels.

In Salesforce CTI and telephony integrations, an IVR system (Interactive Voice Response) that handles automated phone interactions before connecting callers to live agents, often used interchangeably with IVR in call center contexts.

Volunteer Hours in Salesforce represents a single record of a volunteer's contributed time to a nonprofit organization. In the Volunteers for Salesforce (V4S) managed package, hours are stored on the Volunteer_Hours__c custom object; in Nonprofit Cloud, they live on the standard VolunteerHours object. Each Volunteer Hours record links to a Contact (the volunteer), an optional Volunteer Job and Volunteer Shift (defining what work was performed and when), the Hours Worked (decimal value capturing fractional hours), a Start Date and End Date, a Status (Web Sign Up, Confirmed, Completed, Cancelled, No-Show), and the Number Of Volunteers field for cases where one record represents a group commitment. Volunteer Hours are the operational unit of nonprofit volunteer engagement programs - they capture who showed up, what they did, and how long they contributed, providing the data foundation for volunteer recognition, recurring-volunteer cultivation, in-kind valuation reporting, and grant-funder accountability that increasingly requires volunteer-engagement metrics alongside traditional revenue figures.

In Salesforce Nonprofit Cloud (formerly Volunteers for Salesforce), features for managing volunteer recruitment, scheduling, hours tracking, and assignment, connecting volunteer activities with organizational programs and campaigns.

In Salesforce Ideas, an upvote or downvote cast by a community member on an idea, contributing to the idea's score and popularity ranking to help surface the most valuable suggestions.

In Salesforce Web-to-Lead, leads generated when prospects submit a web form directly on your website, captured automatically as Lead records with the lead source tracking their origin from the web form.

Custom links in Salesforce (also called custom buttons and links) that navigate users to external URLs, execute JavaScript (Classic only), or invoke Visualforce pages, configured on object page layouts for custom actions.

In Salesforce lead tracking, leads that arrive from third-party websites that link to your web-to-lead form, with the referring URL captured to track which external sites are driving lead generation.

In Salesforce integration context, an API endpoint (REST or SOAP) that enables programmatic communication between Salesforce and external systems for exchanging data and executing operations.

The collection of Salesforce APIs (REST API, SOAP API, Bulk API, Streaming API, Metadata API, and others) that enable external applications to programmatically interact with Salesforce data and metadata.

A Salesforce tab type that displays an external web page within the Salesforce interface using an iframe, allowing users to access third-party websites or applications without leaving Salesforce.

A Salesforce feature that automatically creates case records from customer submissions on a web form, capturing the form field values and routing the new case to a queue or assignment rule for handling.

A Salesforce feature that automatically creates lead records from visitor submissions on a web form embedded on your website, capturing prospect information and optionally triggering auto-response rules and assignment rules.

In Salesforce Apex, a method declared with the webservice keyword that exposes custom Apex logic as a SOAP web service endpoint, allowing external applications to call the method via the enterprise or partner WSDL.

In Salesforce Service Cloud Messaging, the integration that enables agents to communicate with customers through WhatsApp Business directly from the Service Console, supporting rich media, templates, and conversation history.

In Salesforce SOSL search and SOQL queries, special characters (* and ?) used as placeholders in search terms where * matches zero or more characters and ? matches exactly one character, broadening search results.

In Salesforce, a Wizard is a guided, multi-step user interface that walks a user through a structured task - one decision or input per screen - with validation between steps. Classic examples are the Data Import Wizard (point-and-click data loading), the Schema Builder object-creation wizard, and Salesforce's various setup wizards (Quick Start templates, Lightning App Builder's app wizard). Modern Wizards are typically built as Screen Flows in Flow Builder, which gives admins a declarative way to design multi-step guided experiences without code.

In Salesforce Omni-Channel, a record (case, lead, chat, or custom object) that has been queued for routing to an agent, representing a unit of work that Omni-Channel distributes based on routing configuration and agent capacity.

A Salesforce Field Service object that represents a job or task to be completed, typically at a customer's location, containing details like the work type, priority, service territory, and associated account or asset.

A child record of a Salesforce Work Order that represents an individual task or line item within the larger work order, allowing complex jobs to be broken into specific sub-tasks with their own scheduling and tracking.

A Salesforce Field Service template object that captures the standard attributes of a job - estimated duration, required skill set, and required materials - so work orders and work order line items can be created from it consistently.

An automated action configured in a Salesforce workflow rule that executes when the rule's criteria are met, including field updates, email alerts, task creation, and outbound messages to external systems.

A Workflow Email Alert is an automated action that sends email notifications to specified recipients (users, roles, email addresses, or related contacts) when a workflow rule's or approval process's criteria are met. It uses a predefined email template to generate the message. Email alerts are configured in Setup under Workflow Actions and continue to function even though Workflow Rules themselves have been retired in favor of Flow.

A specific type of workflow action in Salesforce that automatically changes a field value on the record (or a related record's field) when the parent workflow rule fires, commonly used for setting statuses or dates.

A workflow action in Salesforce that sends a SOAP XML message containing record field data to a specified external web service endpoint when the workflow rule triggers, enabling real-time outbound integration.

In Salesforce workflow, the system queue that holds time-dependent workflow actions waiting to execute at their scheduled time, viewable by admins in Setup under Time-Based Workflow monitoring.

A Workflow Rule is a legacy Salesforce automation that triggered automatic actions when a record met specified criteria - field updates, email alerts, outbound messages, and tasks. Salesforce ended Workflow Rules creation in Winter '23 and retired the feature entirely on December 31, 2025; existing rules stopped executing after that date. Flow is the official successor, and Salesforce provides a Migrate-to-Flow tool to convert remaining Workflow Rules.

A workflow action in Salesforce that automatically creates a task record and assigns it to a specified user, role, or record owner when a workflow rule fires, used for follow-up reminders and action items.

A Salesforce Service Cloud product that provides workforce planning, forecasting, scheduling, and intraday management tools to optimize staffing levels in contact centers based on predicted work volumes and channel mix.

In Salesforce Apex development, a design pattern where a custom class encapsulates (wraps) one or more sObjects or other data types, combining them into a single object for convenient use in Visualforce pages or Lightning components.

In Salesforce development, an open-source Java library (Web Service Connector) that generates Java stubs from Salesforce WSDL files, providing a client framework for making SOAP API calls to Salesforce from Java applications.

In Salesforce, an XML file that defines the operations and data types available in a web service API, downloaded from Setup and used to generate client code for SOAP API integrations with Salesforce (Enterprise, Partner, or Metadata WSDL).

In Salesforce metadata and APIs, the markup language used for SOAP API request/response payloads, metadata deployment packages, and configuration files like package.xml that define the structure of data exchanged with the platform.

In Salesforce metadata deployment, a compressed archive file (.zip) containing metadata components in their directory structure, used with the Metadata API deploy/retrieve operations and Salesforce CLI for org migrations.

In Salesforce Ideas and Chatter Answers, a container or category that groups related ideas or questions together, allowing administrators to organize community content by topic, product, or department.