Engagement Pages Checklist
Use this checklist to set up an Engagement Page end to end. Configuration lives at Setup > Create > Engagement Pages. Each step links to a detailed article.
Requirements
- Administrator System Role (only administrators can create or delete Engagement Pages).
- The Roles, Groups, entities, Articles, Documents, Courses, Carousels, and Dashboards that the page will reference should already exist.
Plan
☐ Identify the audience and the page's purpose. Decide whether this is a partner home page, a customer landing page, a campaign page, or an internal employee dashboard. The audience drives layout, hero choice, and which widgets are appropriate.
☐ Decide on layout. Choose Single Column or Single Column with Sidebar. Use the sidebar layout when supporting widgets (Key Contacts, Events Calendar, RSS, Reward Summary) belong next to the main content.
☐ Sketch the hero. Pick Banner or Carousel. If Banner, decide whether the body shows a Summary message or a Search Box, and which buttons (if any) appear.
Build
☐ Create the page Set Name, Path, Layout, and Description from Setup > Create > Engagement Pages > New. The Path becomes the page URL at /pages/<Path>.
☐ Configure the hero Add a Banner or Carousel hero. For a Banner, choose Summary Text or Search Box, set the heading and image, and configure up to two buttons.
☐ Add widgets Use the + Add Widget button to drop widgets into the main column or the sidebar. For Entity Data Tables, Entity Summary Tiles, and Tiles, configure each item from its own settings dialog.
Secure and Personalize
☐ Share the page Use the kebab menu > Share to grant access to Roles, Groups, or specific Users. A page is only visible to users covered by at least one sharing rule.
☐ Verify widget permissions cascade correctly. Widget content respects the underlying module's permissions - for example, the Articles widget only shows Articles a user already has access to. Confirm a sample partner or customer user sees the right content.
☐ Use custom labels for translated portals. If your portal supports multiple languages, point banner headings, button labels, table titles, and tile headings at custom labels rather than hard-coded strings.
Test and Roll Out
☐ Preview the page as an end user. Open /pages/<Path> while logged in as a representative user (or use Login As) for each Role and Group the page is shared with. Confirm the hero, widgets, and button routing all behave as expected.
☐ Test license-gated widgets carefully. Active Page, Deal Inbox, Reward widgets, and Journey widget are gated by edition, product, or license. If a gate is not met, the widget will not appear in the picker. If a user's portal doesn't meet the gate, the widget won't render at runtime either.
☐ Set the page as a landing destination. Link the page from a navigation menu item, an App's landing menu item, or a banner button on another page once it is ready.
☐ Communicate the change. If you are replacing an existing landing page or home page, announce the switch before broad rollout.
If You Run Into Issues
☐ Engagement Pages Troubleshooting Symptom-by-symptom resolutions for missing widgets, sharing problems, banner buttons, search routing, and page-not-found errors.
<< About the Engagement Pages Module | Creating and Sharing Engagement Pages >>