Salesforce terms starting with L

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.