Salesforce terms starting with A

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.