Section 2 · Configuration and Setup · 15% of exam
2.2 Declarative user interface configuration
Exam objective
Distinguish and administer UI configuration such as UI/UX settings, the app menu, list views, global actions, and Lightning App Builder.
UI settings control how users interact with Salesforce. The app menu helps users find available apps; list views organize records using filters and selected columns; global actions let users start supported tasks from locations beyond one specific record. Lightning App Builder arranges components on supported pages and can tailor the page experience.
Start with what the user needs to see or do. Use a list view for a reusable filtered work queue, an action for a focused create-or-update task, and a Lightning page when the record or home experience needs a different component arrangement. Assign and activate pages carefully, and test visibility conditions as a user in the target audience.
Additional concepts
Navigation versus page composition
The app menu and navigation items help users reach apps and work areas. Lightning App Builder changes the components and layout of supported pages. A list view is a filtered way to work with a set of records; it does not change the page layout or grant access to those records.
Actions and visibility
A global action is available from broader Salesforce contexts, while a record-specific quick action can use the current record as context. Component visibility and app assignments tailor the experience for an audience. Always test both what is displayed and whether the user has underlying object, field, and record access. Sales representatives need a shared view of overdue opportunities. A list view with appropriate filters, columns, and visibility is more direct than redesigning the entire Lightning record page.
A page component or action being hidden does not grant or remove object, field, or record permissions.
Key takeaways
- App navigation, list views, actions, and page composition address different user needs.
- Lightning App Builder controls presentation and component visibility.
- Always distinguish the user experience from the underlying security model.
