Creating and Sharing Engagement Pages
This article covers creating a new Engagement Page, setting its core properties, and granting access to the right users. For configuring the hero and widgets after the page exists, see Configuring Engagement Pages.
Requirements
- Administrator System Role to create or delete Engagement Pages.
- For editing an existing page, a sharing entry granting the user's Role, Group, or User record the Manage access level.
Creating an Engagement Page
- Go to Setup > Create > Engagement Pages.
- Click New.
- Configure the page properties (described below).
- Click Save to create the page. The page editor opens automatically so you can add a hero and widgets.
Page Properties
| Field | What It Does |
|---|
| Name | Display name of the page. Visible in lists, navigation, and page titles. |
| Path | The URL slug. The page is served at /pages/<Path>. Must be unique across the portal and cannot contain special characters. Choose a Path that reflects the page's purpose - for example, partner-home, onboarding, q1-promotion. |
| Layout | Choose Single Column for full-width pages or Single Column with Sidebar for pages that need a supporting column. |
| Description | Internal description for administrators. Not shown to end users. Use this to record the page's purpose and intended audience for future reference. |
Path tip. The Path is permanent for SEO and bookmarking. Renaming a Path after the page is in use breaks links from menus, banner buttons, and bookmarks. Choose carefully on creation.
Editing an Existing Page
- Go to Setup > Create > Engagement Pages.
- Click the page name to open the editor.
- To edit Name, Path, Layout, or Description, click the kebab menu (three dots) in the top right and select Edit Settings.
- To edit the hero or widgets, work directly in the editor canvas.
Users without administrator access who try to open a page they have View (not Manage) sharing on are redirected to the live page at /pages/<Path> with a message explaining they can browse but not edit.
Sharing an Engagement Page
Engagement Pages are not visible to anyone by default. Sharing rules determine which users can see and edit the page.
- Open the page from Setup > Create > Engagement Pages.
- Click the kebab menu (three dots) and select Share.
- Add sharing entries by Role, Group, or specific User.
- Click Save.
Sharing Targets
| Target | Default Access | When to Use |
|---|
| Employee Role | View | Internal team pages - dashboards, internal announcements, employee onboarding. |
| Partner Role | View | Partner-facing landing pages, partner home pages, tier-specific content. |
| Customer Role | View | Customer portal home pages, self-service hubs, knowledge landing pages. |
| Group | View | Audiences that cut across roles - regional teams, partner tiers, beta cohorts. Added in v2026.1.0. |
| Specific User | Manage | Grant edit rights to a non-administrator content owner who maintains the page. |
A user can see a page only if at least one sharing entry covers their Role, Group, or User record. Sharing is additive - granting access to a Group does not remove access from a Role.
Linking the Page from Navigation
Creating a page does not put it in front of users automatically. To surface the page:
- Add a Link Menu Item that points at /pages/<Path> in the appropriate App. See Managing Menu Items.
- Set the page as an App's default landing menu item if it should be the first thing users see when opening that App.
- Use the page as the destination of a banner button on another Engagement Page (Custom URL = /pages/<Path>).
Deleting an Engagement Page
Only administrators can delete Engagement Pages. Before deleting:
- Remove or update any Menu Items that link to /pages/<Path>.
- Update any banner buttons or Active Pages that reference the page's URL.
- If the page is a landing menu item for an App, change the App's landing first.
Delete the page from the kebab menu in the page list.
Troubleshooting (this page)
| Symptom | Likely Cause | Resolution |
|---|
| "Path already exists" on save. | Another Engagement Page (or system route) is using the same Path. | Choose a different Path. Paths must be unique portal-wide. |
| End users get a 404 at /pages/<Path>. | The user is not in any of the page's sharing rules, or the page itself was deleted. | Open the page's Sharing dialog and confirm the user's Role, Group, or User record is included. Reload the page after sharing changes. |
| Non-admin can't edit a page they expected to manage. | Their sharing entry is at View level, not Manage. | From the Share dialog, change their access level to Manage, or grant Manage at the User level. |
| Special characters rejected in Path. | Path validation does not allow spaces, slashes, or punctuation. | Use lowercase letters, numbers, and hyphens only. Example: partner-home, not Partner Home. |
For widget, hero, and banner-button issues, see Engagement Pages Troubleshooting.
<< Engagement Pages Checklist | Configuring Engagement Pages >>