Lightning Platform Builder
A Lightning Platform builder is any of the point-and-click design tools that Salesforce ships for extending the Lightning Platform without writing Apex.
Definition
A Lightning Platform builder is any of the point-and-click design tools that Salesforce ships for extending the Lightning Platform without writing Apex. The phrase is an umbrella label rather than a single product. It groups the declarative builders an admin reaches for every day: Lightning App Builder for pages, Object Manager for data, Flow Builder for automation, and Schema Builder for visual data modeling. Each one lives inside Setup and produces metadata that deploys through normal release tools.
Salesforce documentation rarely prints the exact words "Lightning Platform builder" as a heading. It instead names each builder directly. You will see "Lightning App Builder" and "Flow Builder" in the Help pages, not a combined app. Treat the phrase as a way to talk about the whole declarative toolset. When you actually need to build something, open the specific builder that matches the job rather than hunting for one master builder.
The builders that make up the toolset
What "builder" means on the Lightning Platform
On the Lightning Platform, a builder is a visual workspace inside Setup where you assemble something by clicking and dragging instead of writing code. The Lightning Platform is the underlying app-development layer of Salesforce, the part that lets you create custom objects, pages, and automation on top of the standard CRM. Salesforce groups the click-based tools under the idea of extending the platform "with clicks, not code." Lightning App Builder, Object Manager, Flow Builder, and Schema Builder are the headline members. They share a common trait: each one outputs metadata. That metadata is the same format whether you build by clicking or by deploying through a developer pipeline. Because the output is metadata, anything you make in a builder moves between sandboxes and production using change sets, the Metadata API, or a DevOps tool. So the phrase "Lightning Platform builder" is less about a product and more about a working style. You stay declarative, you let the platform generate the metadata, and you keep your changes portable across environments without ever opening a code editor.
Lightning App Builder for pages
Lightning App Builder is the drag-and-drop designer for Lightning pages. You use it to build Record Pages, App Home Pages, Home Pages, and mobile app pages for Lightning Experience and the Salesforce mobile app. You drag standard or custom Lightning components into regions on a canvas, then set each component's properties in a side panel. The result is a Lightning page stored as metadata and activated for the right app, record type, or profile. Newer features extend what the page can do without code. Dynamic Forms let you place individual fields and field sections directly on the canvas instead of relying on a single page layout. Dynamic Actions control which buttons appear based on record criteria. Dynamic Related Lists and conditional field formatting tune the display further. Dynamic Interactions let one component update another when a user clicks. For most admins, Lightning App Builder is the only supported way to create a new Lightning page. You assign the page through the activation step, choosing an org default, an app default, or an app-and-profile combination so the right users see the layout you designed.
Object Manager for data
Object Manager is the Setup workspace for every object in your org, both standard objects like Account and custom objects you create. Salesforce describes it as a one-stop shop for managing objects. From a single per-object view you create fields and relationships, define record types, edit page layouts, write validation rules, and reach buttons, links, and triggers. Each custom field you add gets a "__c" suffix on its API name, which is how you spot a custom field at a glance. Object Manager replaced the older scattered Setup tree where object settings lived in separate areas. To open it, go to Setup, then click the Object Manager tab next to Home. From there you pick an object, then use the left sidebar to jump to Fields and Relationships, Page Layouts, or other settings. Creating a field walks you through choosing a data type, naming the field, setting field-level security, and adding it to layouts. Most production schema work happens here because the changes are precise and tracked. When you need to model relationships visually instead, Schema Builder is the better fit, but the durable per-object configuration lives in Object Manager.
Flow Builder for automation
Flow Builder is the declarative automation designer, and on the modern Lightning Platform it is the single most important builder. Salesforce Help describes it as a way to create simple or complex automations, forms, and guided experiences with little to no code. You build several flow types from one canvas. Record-triggered flows run when a record is created, updated, or deleted. Screen flows present a step-by-step interface to a user. Scheduled flows run on a set cadence, and platform-event flows respond to events. You drag elements onto the canvas to query records, make decisions, loop, assign variables, and create or update data. Flow Builder is the strategic direction for Salesforce automation. It absorbed the work once done by Workflow Rules, which Salesforce retired, and it supersedes Process Builder for new builds. Flow Trigger Explorer lets you see every record-triggered flow on an object in one place, which matters because multiple flows can run on the same object. New automation should start in Flow Builder. You launch a flow several ways: from a quick action, a button, a record event, a schedule, or another flow as a subflow.
Schema Builder and Setup as the shared home
Schema Builder is the visual data-modeling tool. It draws your objects and their relationships as a connected diagram on a single canvas. You can create objects, add fields, and draw lookup or master-detail relationships right on the diagram, and the changes save back to your org. Salesforce positions it for designing a data model and for seeing how objects connect at a glance. For documentation and early design it is excellent. For careful production changes most admins still prefer Object Manager because the field-creation wizard is more deliberate. Every builder discussed here lives inside Setup, the central administration interface. Setup hosts thousands of configuration nodes, so the Quick Find search box is the fastest way to reach any of them. You type a feature name, such as "Flows" or "Schema Builder," and pick it from the results rather than clicking through the tree. Setup Home also surfaces the Object Manager tab and, in recent releases, AI-assisted help through Setup with Agentforce. Understanding Setup as the shared launch point ties the builders together into one declarative workflow.
How the builders fit together on a real project
A typical build touches several of these tools in sequence, which is why grouping them is useful. Say you are adding a simple project-tracking feature. You start in Object Manager or Schema Builder to create a Project custom object and its fields, then draw a lookup to Account. You return to Object Manager to add a validation rule that blocks a closed project from being reopened. Next you open Flow Builder and create a record-triggered flow that sets a default owner and sends a notification when a project is created. Then you switch to Lightning App Builder and design the Project record page, placing Dynamic Forms field sections, a related list of tasks, and your custom components. Finally you activate that page for the right profiles. Each step produced metadata, so the whole feature can move from a sandbox to production together. No single "Lightning Platform builder" app did all of this. You moved between specialized builders, each focused on one concern, all reachable from Setup. That is the practical meaning of the umbrella term: a coordinated set of declarative tools, not one monolithic editor.
Why the naming shifted over time
The umbrella phrasing comes from an earlier era of Salesforce branding. The platform itself was renamed from Force.com to the Lightning Platform, and marketing material from roughly 2015 to 2018 liked to group the click-based tools under banners that stressed a single unified declarative experience. As each tool matured and gained its own depth, Salesforce documentation moved toward naming them individually. Today the Help portal sends you to the Lightning App Builder pages, the Flow pages, or the Object Manager pages directly. You rarely see one combined "builder" entry. This matters for search and for training. If you look for a product literally called Lightning Platform Builder, you will not find a download or a single Setup node, because there is not one. You will find the four real builders described above. The capability is exactly that set of tools, fully current and actively developed. The shift is purely in how Salesforce talks about them. When a colleague or an older Trailhead module mentions the umbrella term, read it as shorthand for the declarative toolset and then go open whichever specific builder the task in front of you actually requires.
Open a builder and create a Lightning page
There is no single app called Lightning Platform Builder to open. To start building declaratively, you open a specific builder from Setup. The steps below use Lightning App Builder, the most common entry point, to create a new Lightning page. The same Setup-first pattern works for Object Manager, Flow Builder, and Schema Builder.
- Open the builder from Setup
Click the gear icon and choose Setup. In the Quick Find box, type Lightning App Builder and select it. To reach a different builder, type its name instead, such as Flows or Schema Builder. Every declarative builder is reachable this way.
- Create a new page
On the Lightning App Builder page, click New. Choose the page type you need: App Page, Home Page, or Record Page. Pick a layout template, give the page a label, and click Finish to open the drag-and-drop canvas.
- Drag components and set properties
From the Components panel on the left, drag standard or custom components into the canvas regions. Select each component to edit its properties in the right panel. Add Dynamic Forms field sections on a record page to place individual fields instead of one layout.
- Save and activate
Click Save, then Activate. Choose how the page is assigned: as the org default, an app default, or an app-and-profile combination. Activation is what makes your users actually see the page, so do not skip it.
App Page, Home Page, or Record Page. The type controls where the page can be assigned and which components are available.
The region structure of the page, such as one region, two regions, or a header plus columns. You can change components later but the template sets the frame.
Org default, app default, or app and profile. This decides exactly which users and apps load your new page.
- There is no Setup node literally named "Lightning Platform Builder." Search for the specific builder you need instead.
- A saved Lightning page does nothing until you activate it. Unactivated pages are a common reason changes seem to disappear.
- Use Object Manager, not Schema Builder, for production field changes. Schema Builder is best for visual modeling and documentation.
- Start new automation in Flow Builder. Workflow Rules are retired and Process Builder should not be used for new work.
Prefer this walkthrough as its own page? How to Lightning Platform Builder in Salesforce, step by step
Trust & references
Cross-checked against the following references.
- Lightning App Builder OverviewSalesforce
- Extend Salesforce with Clicks, Not CodeSalesforce
Straight from the source - Salesforce's reference material on Lightning Platform Builder.
Hands-on resources to go deeper on Lightning Platform Builder.
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What does the term Lightning Platform Builder refer to?
Q2. Why does Salesforce recommend reaching for declarative Lightning Platform Builder tools before writing Apex or LWC code?
Q3. Which set of tools belongs to the declarative Lightning Platform Builder suite?
Discussion
Loading discussion…