The 137 terms you will hear when buying, building or running Salesforce, explained for the people who sign off on the project rather than the people who configure it.
No terms match. Try a shorter search.
An account is the Salesforce record for a company or organization you do business with, such as a customer, partner, or prospect. Contacts, opportunities, and cases hang off it. A clean account structure, including parent and child relationships, gives sales and service one shared view of each customer and keeps reporting on revenue and activity trustworthy.
Learn more →Marketing Cloud Account Engagement, formerly Pardot, is Salesforce's B2B marketing automation tool for email campaigns, forms, landing pages, lead nurturing, and prospect scoring. It syncs with Sales Cloud so sellers can see marketing activity on leads and contacts. It matters for businesses with longer, considered sales cycles that need marketing to warm up and qualify leads before handing them to sales.
Learn more →Account forecasting is a Manufacturing Cloud capability that projects future revenue or volume per account and product from orders, agreements and other sources. Planners can adjust the numbers, and recalculation runs on a schedule. It complements the opportunity forecast, which tracks new deals, by covering the run-rate business that never appears as an opportunity.
Learn more →Agent Script is an open-source language Salesforce introduced for Agentforce that combines deterministic rules with AI reasoning, so an agent follows approved steps where a process must be predictable and uses reasoning elsewhere.
Learn more →Agentforce is Salesforce's platform for building AI agents that can answer questions and take actions, such as updating records or resolving routine service requests, inside your org and channels. Agents follow instructions and topics you define and use your own data and automation. Results depend heavily on data quality, clear permissions, and well-built flows underneath, so readiness work usually comes first.
Learn more →Agentforce Contact Center is Salesforce's offering that brings native voice, digital channels, customer data and AI agents into one service workspace. Salesforce announced it as generally available in March 2026 as an add-on for Agentforce Service customers in the U.S. and Canada, alongside partner telephony options for companies keeping their existing phone systems.
Learn more →Agentforce Coworker is the AI assistant in the Salesforce search bar. Employees ask questions in plain language and it answers from the records they can already access, optionally adding Slack and other connected sources, then hands work to other agents or runs actions. Salesforce began enabling it automatically for eligible orgs in August 2026.
Learn more →AIforce is the name Salesforce gave at Dreamforce 2026 to bringing Salesforce data and governed actions to wherever people work: Claudeforce inside Claude, Slackforce inside Slack and Agentforce Coworker inside Salesforce, all using the permissions already defined in Salesforce.
Learn more →Annual recurring revenue is the yearly value of a company’s active subscription contracts. Salesforce can show ARR from opportunities, assets or contract data, but finance often keeps the official figure in the billing system. Agreeing which system owns ARR, and how upgrades, downgrades and churn are counted, prevents two different numbers in every board meeting.
Learn more →Apex is Salesforce's own programming language, used when declarative tools such as Flow cannot handle a requirement cleanly. Developers write Apex for complex business logic, integrations, and custom processing. It runs on Salesforce servers, must stay within governor limits, and requires automated test coverage before deployment to production, so it adds capability but also long-term maintenance responsibility.
Salesforce is a shared, multitenant platform, so it caps how much work any one customer can do. API limits control how many calls outside systems can make over a period. Governor limits cap what a single transaction of code or automation can consume. Designs that ignore these limits tend to fail under real data volumes, so architects plan integrations and automation around them from the start.
Learn more →API-led connectivity is MuleSoft’s approach of organizing integrations into three layers: system APIs that unlock a source, process APIs that combine data for a business purpose, and experience APIs shaped for a specific consumer. The layering makes each piece reusable. It pays off when many projects need the same data, and adds overhead when only one does.
Learn more →AppExchange is Salesforce's marketplace for apps, components, and consulting listings that extend an org. Many packages install directly into Salesforce and add objects, automation, or screens. Picking the right app can save months of custom build, but each package brings its own licensing, security review, upgrade cycle, and data model, so evaluate fit and long-term cost before installing.
Big objects are Salesforce storage designed for very large volumes of records, such as years of history or event data, with consistent query performance at scale. They suit archives and audit trails rather than everyday working records, and they have limits: Salesforce notes, for example, that they do not support encryption.
Learn more →A care plan in Health Cloud organizes the goals, problems and tasks a care team works through for one patient or member. Templates keep plans consistent across a program, while each plan stays editable for the individual. Care plans sit alongside care teams and care programs, and access to them follows the org’s health data permissions.
Learn more →A case is the Service Cloud record for a customer question, problem, or request. It tracks who raised it, what it concerns, its status, priority, and every interaction until it is closed. Well-designed case processes, with clear statuses, assignment rules, and escalation paths, are the foundation of service reporting and of any routing or AI deflection you add later.
Learn more →Change data capture is a Salesforce feature that publishes an event whenever selected records are created, updated, deleted or undeleted. Integration tools subscribe to those events to keep other systems current in near real time, instead of polling for changes on a schedule. It reduces API calls, but subscribers still need retry and replay handling.
Learn more →A change set is Salesforce's built-in, point-and-click way to move configuration and code from one connected org to another, typically from a sandbox to production. It works for simple deployments but has no version history, cannot easily remove components, and becomes error-prone as teams grow. Many organizations move to DevOps Center or source-control-based pipelines for more predictable releases.
Learn more →Claudeforce is the Salesforce and Anthropic partnership announced in August 2026. It brings Salesforce data and governed actions into Claude through a plugin with prebuilt sales skills, and it makes Claude the default reasoning model in parts of Agentforce. Salesforce listed it in beta at Dreamforce 2026.
Learn more →A connected app is a configuration in Salesforce that lets an outside application authenticate and access your org through APIs, usually with OAuth. It controls which users can connect, what scopes they get, and session policies. Reviewing connected apps regularly matters because an unused or overly permissive connection is a common and easily overlooked path into company data.
Learn more →Consent management in Salesforce records whether a person agreed to be contacted, through which channel and for what purpose. Standard consent objects link an individual to contact points and data use purposes, so marketing and service tools can check permission before sending. Regulated industries rely on it to show what a customer approved, and when.
Learn more →A contact is the Salesforce record for an individual person, usually linked to an account. It stores details such as name, title, email, and phone, and ties that person to opportunities, cases, and campaigns. Keeping contacts deduplicated and correctly linked lets sales, service, and marketing see the same person and avoids embarrassing duplicate outreach.
Learn more →Contacts to Multiple Accounts is a Salesforce setting that lets one contact relate to several accounts, each with its own role. It fits industries where the same architect, advisor or referral partner works with many companies. An admin turns it on, and each contact keeps one primary account while indirect relationships appear on the others.
Learn more →The Salesforce editions introduced on September 3, 2026 for Agentforce Sales, Service and Industries, replacing Enterprise, Unlimited and Agentforce 1 for new purchases. Each tier bundles Agentforce, Slack, Tableau Next, security features, a Premier Success Plan and a yearly pool of Flex Credits.
Learn more →CPQ stands for configure, price, quote: tools that let sellers build valid product bundles, apply pricing and discount rules, and generate quotes. Salesforce CPQ is now end of sale for new customers, though existing customers can keep using, renewing, and getting support for it; Revenue Cloud Advanced is its successor. Either way, clean products and pricing rules matter more than the tool.
Learn more →CRM Analytics, formerly known as Tableau CRM and Einstein Analytics, is Salesforce's native analytics product for building interactive dashboards and datasets inside Salesforce. It can combine Salesforce and external data and embed insights on record pages. It suits teams that need more than standard reports but want analytics to live within the CRM where users already work.
A custom object is a database table your team creates in Salesforce to store information that standard objects do not cover, such as projects, contracts, or equipment. Custom objects get the same platform features as standard ones, including reports, security, and automation. Create them deliberately, because unnecessary custom objects fragment data and add long-term maintenance.
Cutover is the planned switch from an old system or process to the new Salesforce setup. It covers the final data load, freezing changes in the legacy system, deploying to production, enabling users, and a rollback plan if something goes wrong. A rehearsed, hour-by-hour cutover plan is what separates a calm go-live weekend from a chaotic one.
Learn more →The daily API request allocation is the number of API calls an org can make in a rolling 24 hours. For most paid editions it is a base amount plus an allowance per user license, shared by every integration and app in the org. Monitoring it in Setup and designing integrations to use bulk and event-based patterns keeps systems from hitting the ceiling.
Learn more →A dashboard is a visual page of charts, tables, and key figures built from Salesforce reports. Executives use dashboards to track pipeline, service performance, or adoption at a glance, and managers use them to coach teams. Dashboards are only as reliable as the reports and data behind them, so consistent definitions and clean data come first.
Data 360 is the current name for the product Salesforce previously called Data Cloud. It brings customer data from Salesforce and outside sources into unified profiles that can drive segmentation, analytics, automation, and AI. It is often the data foundation for Agentforce. Value depends on choosing the right sources, identity rules, and use cases before connecting everything.
Learn more →A Data Mapper is the OmniStudio component that extracts, transforms and loads Salesforce data for OmniScripts and FlexCards. Salesforce renamed DataRaptors to Data Mappers, though older API names still use the original term. They keep data logic declarative, but large or nested mappings need careful testing to stay fast and maintainable.
Learn more →Data Mask & Seed is a Salesforce add-on for sandboxes that hides or scrambles sensitive data copied from production and loads realistic sample data for testing and training. It helps teams work with production-like records without exposing personal or confidential information to developers, testers, or partners. It matters for organizations with privacy obligations that still need meaningful data in their sandboxes.
A data stream is a connection that brings data from one source, such as Salesforce, a website, a data warehouse or a file, into Data 360 on a schedule or in near real time. Each stream is mapped to the Data 360 data model. The number of streams and how often they refresh drive both implementation effort and consumption.
Learn more →Dataverse is the data platform underneath Microsoft Dynamics 365 and the Power Platform, where Dynamics tables, relationships and security are stored. When a company moves from Dynamics 365 to Salesforce, Dataverse tables, choice fields and GUID identifiers are mapped to Salesforce objects, picklists and external IDs.
Learn more →DevOps Center is Salesforce's tool for managing changes and releases with source control behind the scenes. Admins and developers track work items, move changes through pipeline stages, and see what is deployed where, without relying on change sets. It helps teams release more predictably and keep an audit trail of what changed, when, and why.
Learn more →Discovery is the first phase of a Salesforce project, where the partner and your team document goals, current processes, pain points, data sources, integrations, and constraints. It produces requirements, a proposed design, and a realistic scope and plan. Skipping or rushing discovery is one of the most common reasons projects go over budget or miss what users actually need.
Learn more →Matching rules define how Salesforce decides two records are likely the same, for example by comparing company name and website. Duplicate rules decide what happens when a match is found, such as warning the user, blocking the save, or reporting it. Together they keep new duplicates out, which protects reporting, routing, and customer experience, but existing duplicates still need a cleanup project.
Learn more →Einstein Activity Capture connects Gmail or Microsoft email and calendars to Salesforce and logs emails and events against matching records automatically. Older setups stored captured activity outside standard activity records, which limited reporting; Salesforce's newer approach can store it as standard Salesforce activity. Teams should decide which emails must never be captured before switching it on.
Learn more →Einstein Bots are Salesforce's scripted chatbots for service channels. They entered maintenance mode on August 17, 2026: still supported, with no new features. Salesforce recommends Agentforce for new work and offers an Upgrade Agent tool that converts a bot into a draft Agentforce agent.
Learn more →Engagement Studio is the visual program builder in Marketing Cloud Account Engagement for creating automated nurture journeys. You set up steps that send emails, wait, check whether a prospect opened, clicked, or reached a score, and branch accordingly. It lets marketing follow up consistently with each prospect based on their behavior, instead of sending the same message to everyone on a list.
Learn more →Entitlements define what level of support a customer is owed, and milestones track service-level agreement targets such as first response or resolution time on cases. Salesforce can show countdowns, warn agents, and escalate when targets are at risk. Set up correctly, they turn SLA commitments in contracts into something your service team can actually see and manage every day.
Learn more →Event Monitoring records detailed activity in your org, such as logins, report exports, API calls, and page views, so you can see how data is being accessed and spot unusual behavior. Basic login data is available to every org, while the full set of event logs and real-time policies comes with Salesforce Shield or a separate add-on. It supports security investigations, compliance evidence, and adoption analysis.
Learn more →An Experience Cloud site is a branded portal or website built on Salesforce, used for customer self-service, partner collaboration, or member communities. External users log in to view records, submit cases, or share information stored in your org. Because outsiders are accessing your data, licensing, sharing settings, and page design must be planned together from the start.
Learn more →An external ID is a custom field marked to hold a unique identifier from another system, such as an ERP customer number or a legacy record ID. Salesforce indexes it and can use it to find matching records during imports and integrations. It matters because it keeps records linked across systems, prevents duplicates when data is loaded again, and makes migrations and ongoing syncs far more reliable.
A field is a single piece of information stored on a record, such as a phone number, status, amount, or date. Fields have types that control what users can enter, and they can be required, calculated by formula, or restricted by security. Too many unused or overlapping fields clutter screens and reports, so field sprawl is a common cleanup target.
Field Audit Trail, part of Salesforce Shield, keeps a long-term history of changes to the fields you choose, well beyond what standard field history tracking retains. You define which objects and fields to track and how long to keep the data. It matters when regulators, auditors, or legal teams need to see who changed a value, when, and what it was before, years after the fact.
Learn more →Field-level security controls whether a user can see or edit a specific field, regardless of whether they can access the record. It is set through profiles and permission sets. It matters for protecting sensitive data such as salaries, health details, or financial information, and it also affects what integrations, reports, and AI features are able to read.
Learn more →A financial account is the Financial Services Cloud record for a client's bank, brokerage, loan, insurance or investment account. It links to the people and households that own it, and often carries balances and holdings fed from a custodian or core system. It is usually read-only in Salesforce, with the source system remaining the system of record.
Learn more →Flex Credits are a consumption-based pricing model Salesforce uses for Agentforce and some other AI features, where usage draws down a balance of credits based on the actions agents perform. It is one of the ways Agentforce can be licensed. It matters for budgeting, because costs depend on how often agents run, so estimating volumes and monitoring usage should be part of any rollout plan.
Learn more →Flow is Salesforce's main tool for building automation without code. Record-triggered flows run when data changes, screen flows guide users through step-by-step forms, and scheduled flows run on a timetable. Flow replaced Workflow Rules and Process Builder as Salesforce's recommended automation tool. Good flow design, naming, and documentation keep automation understandable as the org grows.
Learn more →Flow Orchestration coordinates multi-step, multi-person processes in Salesforce, such as approvals or onboarding that pass between teams. It groups work into stages and steps, assigning interactive steps to users or queues and running background steps automatically. Salesforce made it a standard flow type in early 2026, so many orgs no longer need a separate add-on.
Learn more →Grounding means supplying an AI model with relevant, current information from your own systems, such as record details or knowledge articles, when it generates a response. In Salesforce, prompt templates and agents pull in CRM and Data 360 data for this purpose. Grounding makes AI answers more accurate and specific, but only if the underlying data is correct and properly permissioned.
Learn more →A guest user is the built-in identity Salesforce uses for unauthenticated visitors to a public Experience Cloud site or form. Anything the guest user can see is effectively public. Misconfigured guest user sharing has exposed sensitive records in real orgs, so its object access, sharing rules, and API exposure deserve a careful, regular review.
Learn more →Health Check is a built-in Salesforce Setup tool that compares your org's security settings, such as password, session, and login policies, against a Salesforce baseline or a custom one and gives a score. It is a quick way to spot weak settings. It covers configuration only, not your data model, automation, or sharing design, which a broader partner-led assessment reviews.
Learn more →Health Cloud is Salesforce's industry solution for healthcare and life sciences organizations, adding data models and tools for patients, members, care teams, care plans, and providers. Salesforce briefly branded it Agentforce Health, so both names appear in documentation. It suits organizations managing ongoing patient or member relationships, but it adds cost and complexity, so a standard Sales or Service Cloud setup is sometimes enough.
Learn more →In Financial Services Cloud, a household groups the people who share finances, such as a couple and their dependents, so an advisor sees combined relationships, accounts and goals in one place. Households are usually modeled as an account linked to members through relationship records. Getting the household design right early matters, because reports, rollups and advisor workflows all depend on it.
Learn more →Hypercare is the period right after go-live when the project team provides intensified support. The team watches for errors, answers user questions quickly, fixes defects, and tracks adoption before handing the org over to normal support. A defined hypercare window with clear exit criteria helps users build confidence and catches issues before they become habits.
Learn more →Hyperforce is Salesforce's infrastructure architecture built to run on major public cloud providers rather than Salesforce's own legacy data centers. It lets customers choose the region where their data is stored where services are available. It matters mainly for data residency, compliance, and planning migrations, since moving an org to Hyperforce can affect integrations that rely on fixed IP addresses or hardcoded URLs.
Identity resolution is the Data 360 process that decides which records from different systems belong to the same person or company, using match rules, and which value wins when they disagree, using reconciliation rules. It produces unified profiles for segmentation, analytics and AI. Weak identifiers, such as shared emails, can merge different people, so rules are tuned and reviewed before activation.
Learn more →An integration user is a dedicated Salesforce user account that an outside system uses to connect, rather than borrowing a real person's login. It is usually limited to API access and given only the permissions the integration needs. This makes activity easier to audit, prevents breakage when employees leave, and reduces the damage if credentials are ever compromised.
Learn more →An integration platform as a service (iPaaS) is a cloud tool for building and running integrations between applications, such as MuleSoft, Boomi, Celigo or Workato. It handles connections, data mapping, scheduling, error handling and monitoring in one place. An iPaaS usually pays off when several systems connect to Salesforce or integrations need central monitoring.
Learn more →Salesforce's seven named, pre-built Agentforce agents announced in September 2026, each for one role: Casey for customer service, Paige for IT and HR, Carter for shopping, Hunter for outbound sales, Marshall for supply chain, Piper for inbound pipeline and Fin for complex customer experience.
Learn more →Journey Builder is the Marketing Cloud Engagement tool for multi-step customer journeys across email, SMS and other channels, triggered by events or data changes. Journeys can read and update Salesforce records through Marketing Cloud Connect. Well-designed journeys have clear entry rules, exit criteria and suppression so people do not receive conflicting messages.
Learn more →Salesforce Knowledge is a library of articles, such as how-to guides, troubleshooting steps, and policies, that agents and customers can search. Articles can be attached to cases, shown in portals, and used to ground AI responses. A governed knowledge base with owners, review cycles, and clear categories reduces repeat questions and improves both agent and AI answers.
Learn more →A lead is a Salesforce record for a prospective buyer who has not yet been qualified, often from a web form, event, or list. Sales or marketing works the lead and, if it is promising, converts it into an account, contact, and usually an opportunity. Clear qualification criteria and routing rules keep leads from going stale or being worked twice.
Learn more →Lead scoring measures a prospect's interest based on actions like email clicks, form fills, and page visits, while grading measures how closely they match your ideal customer profile. Used together, they help sales focus on leads that are both engaged and a good fit. They can be built with formulas and Flow, Account Engagement, or Einstein AI scoring, and only work if sales trusts the criteria.
Learn more →Lightning App Builder is Salesforce's drag-and-drop tool for designing Lightning pages, including record pages, home pages, and app pages. Admins place components, add tabs, and show or hide sections based on rules such as record type or user permission. Well-designed pages put the right information in front of each role and reduce clicks, which directly improves adoption.
Learn more →Lightning Web Components, often shortened to LWC, is Salesforce's modern framework for building custom user interface components using standard web technologies. Developers use LWC when standard pages and tools cannot deliver a needed experience, such as a specialized calculator or data grid. Custom components add flexibility but need testing, documentation, and upkeep across seasonal releases.
A loan origination system is the lender’s platform for applications, underwriting, disclosures and closing. In most lenders it stays the system of record for the loan file, while Salesforce manages leads, referral partners, borrower communication and pipeline visibility. The integration design decides which milestones flow back so loan officers and marketing see status without re-keying it.
Learn more →A maintenance plan in Field Service generates recurring work orders for assets on a set schedule, such as quarterly inspections or annual servicing. It turns service agreements into scheduled work without anyone creating each visit by hand. Contractors and manufacturers with installed equipment use it to keep preventive work, and the revenue attached to it, predictable.
Learn more →A managed package is a bundle of Salesforce components, usually from an AppExchange publisher, that installs into your org as a unit. The publisher controls the code and pushes upgrades, and you often cannot see or change its internals. That reduces your maintenance burden, but it also means the package's limits and roadmap shape what you can customize.
Managed services is an ongoing arrangement where a Salesforce partner supports and improves your org on a recurring basis instead of through one-off projects. Typical work includes admin requests, bug fixes, release readiness, small enhancements, and user support. It suits organizations without a full in-house Salesforce team that still need steady, expert attention to keep the platform healthy.
Learn more →Marketing Cloud Connect is the connector between Marketing Cloud Engagement and Sales or Service Cloud. It syncs leads, contacts and campaign data into Marketing Cloud and writes email engagement back to CRM records. Deciding which objects and fields sync, and how often, controls both data quality and cost.
Learn more →Metadata is the configuration that defines how your Salesforce org works, including objects, fields, page layouts, flows, permissions, and code, as opposed to the business data stored in records. Metadata is what gets deployed between sandboxes and production. Treating it as something to version, review, and document is the core of disciplined Salesforce release management.
Learn more →The Model Context Protocol is an open standard that lets AI assistants and agents connect to outside systems, such as a Salesforce org, through a server that exposes specific data and actions. For a business, it offers a consistent way to let AI read and update CRM records without building a custom integration for every tool, provided permissions, user identity, and logging are set up carefully first.
Learn more →MuleSoft is Salesforce's integration platform for connecting applications, databases, and APIs across an organization. Instead of point-to-point connections, teams build reusable APIs that expose systems such as ERP or billing in a consistent, governed way. It fits organizations with many systems to connect, where integration reliability, monitoring, and reuse matter more than a quick one-off link.
Learn more →Multi-factor authentication requires users to prove who they are with something beyond a password, such as an authenticator app or security key, when logging in to Salesforce. It sharply lowers the risk from stolen or reused passwords. Salesforce treats MFA as a baseline security expectation, and rollouts go smoother with clear user communication and a plan for lost devices.
Learn more →Nonprofit Cloud is Salesforce's native nonprofit solution for fundraising, programs, case management, outcomes, and volunteer work. Salesforce briefly branded it Agentforce Nonprofit and now uses the Nonprofit Cloud name again. Unlike the older Nonprofit Success Pack, it is built into the platform rather than installed as a package, and Salesforce recommends it for new customers. Moving from NPSP is a reimplementation with a different data model, not a simple upgrade.
Learn more →The Nonprofit Success Pack is a long-standing managed package that adds donor, household, gift, and recurring donation features to Salesforce for nonprofits. Salesforce continues to support it for existing customers, while steering new customers to Nonprofit Cloud. It matters when deciding whether to keep improving a current NPSP org or plan a migration, since the two products store constituents and gifts differently.
Learn more →An object is a table in the Salesforce database that stores one kind of record, such as accounts, cases, or invoices. Each object has fields, relationships to other objects, page layouts, and security settings. The set of objects and how they relate, called the data model, drives what you can report on and automate, so it deserves careful design.
Omni-Channel is Service Cloud's routing engine for pushing work, such as cases, chats, messages, and leads, to the right available agent based on capacity, skills, and priority. It replaces agents picking from shared queues. Good routing design balances workload, speeds up responses, and gives supervisors real-time visibility into who is handling what.
Learn more →OmniStudio is Salesforce's set of low-code tools for guided processes and data handling in industry clouds: OmniScripts for step-by-step flows, FlexCards for compact record views, Integration Procedures for server-side data calls and Data Mappers for reading and writing data. It now runs natively on the platform rather than only in a managed package, and it needs specialist skills to maintain.
Learn more →An opportunity is a Salesforce record for a potential deal, tied to an account and tracked through sales stages until it is won or lost. It holds the amount, close date, products, and next steps. Consistent stage definitions and required fields make opportunities the basis for accurate forecasting and pipeline reporting.
Learn more →An org, short for organization, is a single instance of Salesforce: your company's own environment with its data, configuration, users, and licenses. Production is your live org, and sandboxes are separate copies used for building and testing. Some companies run several orgs, which affects reporting, integration, and cost, and sometimes leads to org consolidation projects.
Org Check is a free Salesforce Labs app that scans an org's metadata and flags problems such as unused fields, outdated API versions, inactive users, and risky configuration. Salesforce's admin team points to it now that the older Salesforce Optimizer has been retired. It matters as a quick, low-cost starting point for cleanup and technical debt work, though its findings still need human judgment before anything is deleted.
A partner-led org health check is a structured review of your whole Salesforce environment by a consulting partner. It typically goes beyond Salesforce's built-in security Health Check to examine the data model, automation, code, security and sharing, data quality, integrations, and adoption. The result is a prioritized list of risks and improvements you can act on.
Learn more →Organization-wide defaults, or OWDs, set the baseline level of access every user has to records they do not own, for example private, public read only, or public read and write, for each object. They are the starting point of Salesforce's sharing model. Other tools can only open access further, so choosing restrictive enough defaults is a key security decision.
Learn more →A page layout controls which fields, buttons, and related lists appear on a record page, and in what order. Different layouts can be assigned by profile and record type, so a sales rep and a finance user see what each needs. Simplified, role-specific layouts reduce clutter, speed up data entry, and noticeably improve user adoption.
A permission set is a bundle of access rights, such as object permissions, field access, and system abilities, that you assign to users on top of their profile. Salesforce recommends managing most access through permission sets rather than profiles. This approach makes it easier to grant exactly what each job needs and to see why a user has access.
Learn more →A permission set group combines several permission sets into one assignable package, usually aligned to a job role such as sales manager or service agent. Admins assign one group instead of many individual sets and can mute specific permissions within it. Groups keep access consistent across people in the same role and simplify onboarding and audits.
Learn more →A permission set license gives a user access to features not included in their base user license, such as certain add-on products or industry capabilities. The license alone does nothing; the user also needs a permission set that turns the features on. It matters for cost and access planning, because add-on features often require both the right licenses and careful permission design to reach the right people.
Learn more →A person account is a Salesforce record type that combines an account and a contact into one record for an individual customer, rather than a company. It suits businesses that sell to or serve consumers, patients, donors, or students. Enabling it cannot be undone and changes how data, reports, and integrations work, so it is a design decision to make deliberately and test in a sandbox first.
Platform Encryption, part of Salesforce Shield, encrypts sensitive fields, files, and attachments while they are stored in Salesforce, using keys your organization can manage. It helps meet contractual or regulatory rules for protecting data at rest. Encryption can limit how some fields are searched, filtered, or sorted, so it is worth testing reports, automation, and integrations in a sandbox before switching it on in production.
Learn more →A price book is a list of products and their prices in Salesforce, used when adding products to opportunities and quotes. Organizations often maintain separate price books for regions, currencies, channels, or customer segments. Keeping price books accurate and limited in number prevents quoting errors and makes revenue reporting by product reliable.
Learn more →A price rule adjusts prices on a quote automatically based on conditions such as quantity, customer segment or bundle contents. Discount schedules handle tiered volume pricing. Rules should reflect pricing policy finance has agreed in writing; encoding every historical exception makes quoting slow and hard to maintain.
Learn more →Privacy Center is a paid Salesforce add-on for handling privacy obligations inside the platform: data subject access and deletion requests, retention and deletion policies, de-identification and consent. It helps teams act on requests consistently across related records, but it supports a privacy program rather than replacing legal advice or a documented process.
Learn more →Process Builder is an older Salesforce automation tool for updating records and triggering actions when data changes. Salesforce ended support for it on December 31, 2025. Existing processes continue to run, but Salesforce no longer provides support or bug fixes. Organizations should migrate processes to Flow, which also helps consolidate automation and reduce technical debt.
Learn more →A product bundle groups a parent product with required or optional components so reps can quote a complete offer in one step. In CPQ and Revenue Cloud, bundles carry rules for which options are allowed together. Keeping bundles simple and matched to how customers actually buy is one of the biggest drivers of a successful quoting rollout.
Learn more →Production is your live Salesforce org, where real users work with real customer data. Changes should reach production only after being built and tested in a sandbox and deployed through a controlled release process. Editing configuration directly in production is fast but risky, because mistakes affect users immediately and are harder to trace or undo.
Learn more →Professional services automation software plans and tracks client delivery: projects, resourcing, time, expenses and billing. Some PSA tools run natively inside Salesforce, while others are separate systems integrated with it. The choice decides whether sold work flows straight into staffing and delivery, or crosses a system boundary that someone has to maintain and reconcile.
Learn more →A profile is the base set of settings every Salesforce user must have, covering things like login hours, IP ranges, default apps, and page layout assignments. Historically profiles also carried most permissions. Salesforce now recommends keeping profiles minimal and granting access through permission sets, which reduces the number of near-duplicate profiles that complicate security reviews.
Learn more →A prompt template is a reusable set of instructions for a generative AI task in Salesforce, such as drafting a sales email or summarizing a case. Built in Prompt Builder, templates can pull in record fields, related data, or flow outputs to ground the response. They let admins standardize AI output and control what data the model sees.
Learn more →Quote-to-cash is the end-to-end flow from building a quote to collecting payment: quote, order, fulfillment, invoice and payment. In most companies it spans Salesforce and an ERP or billing system, so the integration design decides which system owns each step. Gaps in the flow show up as re-keyed orders and disputed invoices.
Learn more →Record types let one object support different business processes, for example separate picklist values, page layouts, and sales stages for new business versus renewals. Users choose or are assigned a record type when creating a record. Used well, they keep one shared object tailored to each team; overused, they multiply layouts and automation to maintain.
Salesforce upgrades every org three times a year with its Spring, Summer, and Winter releases. Sandbox preview instances receive each release a few weeks before production, giving teams time to review release notes and test changes. Planning around releases helps you adopt useful features early and avoid surprises when updates change existing behavior.
Learn more →A report type is the template that defines which objects and fields a Salesforce report can use, such as accounts with opportunities. Salesforce provides standard report types, and admins can create custom ones for specific relationships. When users say a report is impossible to build, the fix is often a missing or poorly designed report type.
Restriction rules narrow which records a user can see, even when sharing settings would otherwise grant access. They are useful for sensitive record types, such as confidential deals or matters, where most of the team should not see everything they technically could. Availability depends on edition and object, so check before designing around them.
Learn more →Revenue Cloud Advanced is Salesforce's successor to legacy Salesforce CPQ, covering product catalog, pricing, quoting, contracts, orders, and renewals natively on the platform rather than in an installed package. Salesforce briefly branded the Revenue Cloud suite as Agentforce Revenue Management, and its site now uses the Revenue Cloud name again. It matters because CPQ is end of sale, so existing CPQ customers should plan when a move makes sense rather than assume it is forced.
Learn more →The role hierarchy mirrors your reporting structure in Salesforce and, by default, lets managers see and report on records owned by people below them. It also shapes forecasting and some sharing behavior. It should reflect how data access needs to flow, not necessarily the exact org chart, and overly deep hierarchies can create performance and maintenance problems.
Learn more →A sales agreement is a Manufacturing Cloud record that captures a customer’s committed volumes and prices by product over a planned period. Actual orders are compared against the plan month by month, so account managers see where a customer is running ahead or behind. It suits manufacturers whose revenue repeats on forecastable volumes rather than one-off deals.
Learn more →Sales Territories, formerly Enterprise Territory Management, lets you organize accounts into territories by geography, industry, size, or other criteria, then assign sellers and control who can see which accounts. You can build and test a territory model before activating it. It matters when simple record ownership no longer reflects how your sales team is structured, shares accounts, or forecasts revenue.
Learn more →Salesforce Shield is a paid add-on that bundles advanced security and compliance tools: Platform Encryption, Event Monitoring, Field Audit Trail, and Data Detect for finding sensitive data. It matters for regulated organizations that must show auditors who accessed what, keep long change histories, or encrypt data at rest with keys they control. Many orgs need only part of it, so scope it against real requirements.
Learn more →A sandbox is a copy of your production org used to build, test, and train without affecting live users. Types include Developer and Developer Pro, which copy configuration only, Partial Copy, which adds a sample of data, and Full, which copies all data. Choosing the right sandbox for each stage of work is basic to safe releases.
Learn more →A sandbox refresh replaces a sandbox's contents with a fresh copy of production, bringing its configuration and, for data-bearing sandboxes, its records back in sync. Each sandbox type can only be refreshed at set intervals, and a refresh erases work not yet deployed. Teams coordinate refreshes with release schedules and mask sensitive data afterward.
Learn more →Sender authentication is the set of DNS records that prove your marketing email really comes from your domain. SPF lists the servers allowed to send, DKIM signs each message, and DMARC tells mailbox providers what to do with mail that fails. Major mailbox providers expect all three from bulk senders, so they are set up before the first campaign.
Learn more →A service appointment in Field Service is the scheduled visit for a technician or crew, with a time window, location, status, and assigned resource. It is what dispatchers and scheduling tools place on the calendar and map. Accurate appointment data drives technician routes, customer arrival notifications, and first-time-fix reporting.
Learn more →A service contract in Salesforce records the support or maintenance a customer bought, including covered assets, dates and entitlements. Agents and dispatchers can check coverage before they commit work, and renewals can be tracked as the end date approaches. It is the record that ties recurring service revenue to the cases and visits delivered under it.
Learn more →Sharing rules automatically open record access beyond organization-wide defaults to groups of users, based on who owns the record or on field values, such as sharing all West region accounts with the West sales team. They handle predictable exceptions without manual sharing. Too many overlapping rules make access hard to explain and can slow large orgs.
Learn more →Slack is the messaging and collaboration platform owned by Salesforce, used for channels, direct messages, and workflows. Connected to Salesforce, it lets teams discuss deals and cases, get record updates, and act on CRM data without leaving the conversation. It matters when sales and service work depends on quick coordination across teams, though the Salesforce connection needs clear rules about which data appears where.
Learn more →SOQL, the Salesforce Object Query Language, is the language used to retrieve records from Salesforce, similar to SQL for traditional databases. Developers use it in Apex and integrations, and admins sometimes use it for quick data checks. Efficient queries matter because poorly filtered SOQL can hit governor limits or slow pages as data volumes grow.
Speed to lead is the time between an inbound inquiry and the first real contact from a salesperson. In Salesforce it depends on how quickly leads are created, deduplicated and routed to someone available. Measuring it needs a reliable creation timestamp and a first-activity timestamp on every lead, not just a rep’s impression of how fast they respond.
Learn more →Standard objects are the tables Salesforce provides out of the box, such as Account, Contact, Lead, Opportunity, and Case. They come with built-in features, reports, and integration with other Salesforce products. Using standard objects where they fit, rather than recreating them as custom objects, makes future features, AI tools, and partner apps easier to adopt.
A statement of work, or SOW, is the contract document that defines what a Salesforce partner will deliver: scope, deliverables, assumptions, roles, timeline, acceptance criteria, and commercial terms. A clear SOW sets shared expectations and a process for handling changes. Vague scope or missing assumptions in the SOW are a frequent source of disputes later in a project.
Learn more →The subscriber key is the unique identifier Marketing Cloud Engagement uses for each contact across email, SMS and journeys. Using the Salesforce contact or lead ID keeps Marketing Cloud and CRM records aligned. Changing the key after launch is difficult, so it is one of the first decisions in an implementation.
Learn more →The system of record is the one system that owns the authoritative value of a piece of data, such as the customer's credit terms or an invoice total. Other systems read it or receive copies. Naming a system of record for every shared field is the first step in any Salesforce integration and prevents systems from overwriting each other.
Learn more →Tableau is Salesforce's analytics platform for exploring and visualizing data from many sources, not only Salesforce. Analysts build interactive dashboards that combine CRM data with finance, operations, or product data. It fits organizations that need enterprise-wide analytics, while standard Salesforce reports and CRM Analytics serve more CRM-centered reporting needs inside the platform.
Learn more →Tableau Next is Salesforce's agent-driven analytics platform built on Data 360. A semantic layer defines business metrics once, and Tableau Agent lets people prepare data, build visualizations and ask questions in plain language. It is included in the Core, Advanced and Max editions.
Learn more →Technical debt is the accumulated cost of shortcuts and outdated choices in your org, such as unused fields, overlapping automation, legacy tools, hardcoded values, and undocumented code. It slows every future change and raises the risk of errors. Paying it down through cleanup and consolidation makes enhancements, releases, and AI adoption faster and safer.
Learn more →Total cost of ownership is the full cost of running Salesforce over several years, not just the license quote: implementation, integrations, storage, AppExchange apps, internal staff or managed services, training, release testing and the cost of technical debt. Modeling it up front helps finance compare CRMs fairly and avoid surprises at renewal.
Learn more →The Einstein Trust Layer, which Salesforce increasingly calls simply the Trust Layer, is the set of safeguards applied when Salesforce AI features call a large language model. It includes grounding in permitted data, masking sensitive information, zero data retention by model providers, toxicity checks, and audit logging. It reduces AI risk, but your own permissions and data quality still matter.
Learn more →Upsert is a data operation that updates a record if a match already exists and inserts a new record if it does not, usually matching on the Salesforce record ID or an external ID. It is widely used in data migrations and integrations. It matters because it lets the same load or sync run repeatedly without creating duplicates, which makes cutovers and recurring data feeds safer to rerun.
User acceptance testing is the phase where real business users test the new Salesforce setup against their everyday scenarios before go-live. It confirms the system supports how people actually work, not just the written requirements. Well-prepared test scripts, representative data, and a clear defect triage process make UAT productive instead of a last-minute scramble.
Learn more →A validation rule checks data when a user or integration saves a record and blocks the save with an error message if a condition is not met, such as a close date in the past or a missing reason for a lost deal. Validation rules protect data quality at the source, but too many can frustrate users and break integrations.
A work order in Field Service describes the job to be done, such as an installation, repair, or inspection, including the asset, location, required skills, and line items for parts or tasks. Work orders generate service appointments for scheduling. A well-structured work order model keeps technicians, dispatchers, and billing aligned on what was requested and completed.
Learn more →Workflow Rules are Salesforce's oldest automation tool, used for simple field updates, email alerts, and tasks when records change. Salesforce ended support for them on December 31, 2025. Existing rules still run, but Salesforce no longer provides support or bug fixes. Salesforce offers a Migrate to Flow tool to help move them to Flow.
Learn more →Zero copy data sharing lets Data 360 and a data warehouse such as Snowflake or Databricks query each other’s data without duplicating it through a pipeline. Salesforce data can be read in the warehouse, and warehouse tables can be used in Data 360 segments and agents. Compute and query costs still apply on each side, so model usage early.
Learn more →A Salesforce Consulting Partner since 2017, with 150 Salesforce certifications on one U.S.-based team.
Tech Talk
A monthly brief for the people who own Salesforce, AI and revenue technology
What changed in Salesforce and AI this month, and what to do about it.
One email a month. Written by the consultants who deliver the work, not by a marketing team, for the leaders who make the technology decisions.
Consultant analysis, not vendor recaps. One click to leave.