Salesforce terms starting with F

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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