Salesforce terms starting with O

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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