Lightning App Builder versus Experience Builder for Manufacturing components
Key Takeaway
Choose the builder by who will see the page. Use Lightning App Builder for internal users. Use Experience Builder for external users on an Experience Cloud site that uses the Manufacturing template.
Agentforce Manufacturing includes standard components, such as forecast, rebate, sales agreement, and visit components. You add them to pages so users can reach the information they need. Internal users see pages you build in Lightning App Builder. Partners and customers see pages in an Experience Cloud site that uses the Manufacturing template, and you build those pages in Experience Builder. To set up partner engagement, you work in Experience Builder and choose components that are available for external users.
Which builder to use
The builder you use depends on who will see the page.
| Lightning App Builder | Experience Builder | |
|---|---|---|
| Who sees the page | Internal users | External users, such as partners and customers |
| Pages you add components to | App, home, and record pages | Pages in an Experience Cloud site that uses the Manufacturing template |
Manufacturers use these Experience Cloud sites as partner and customer portals. Experience Builder is therefore the builder for anything that external users will see.
Not every component works in both places. Each component is available for internal users, external users, or both. A component that is available for external users is supported on Experience Cloud sites built using the Manufacturing template. Check a component's availability before you design a portal page.