Pages
Use Integration → Pages (/integrations/pages) to show a published Studio page as the homepage for selected signed-in members, including guests. For example, guests can see a shopping page while other members keep their built-in homepage. Assigning a page does not grant administration or additional data permissions.
Custom homepage configurations require Enterprise. Other plans show a locked entry and a plan dialog when selected. Only published Studio page assets can be selected.
Prepare and activate a page
- Create a Studio page asset. Read Local Studio Development for the folder-to-publish workflow and the SDK example that reads the current member.
- Compile and preview the page, then publish its Studio version.
- Open Pages, choose New, and enter the page name, optional description, applicability and page asset.
- Save. New page configurations are inactive. Review the configuration, then enable it.
- Sign in as an applicable member and open the homepage. Both an active configuration and a published page asset are required.
Publishing a Studio asset and enabling a page configuration are separate operations. Previewing source does not change the version served to members. Later Studio publications update the page's published runtime.
Applicability
Select 1–500 unique objects: members, departments, organizations or roles. Guest entries carry a Guest tag. Selection assigns a page; existing tenant permissions continue to control the data and actions available inside it.
The initial administrator never receives a custom homepage, including when selected indirectly through a department, organization or role. The selection dialog excludes this account; an indirect or programmatic selection does not override the runtime restriction.
Matching uses the active member's current department/organization and effective enabled role bindings within their start/end dates. Department and organization selections match the member's actual assignment; they do not imply a descendant selection. If several active, published pages match, the most recently created configuration wins, followed by ID descending for equal creation times. Editing a configuration does not change its creation order.
Maintain pages
- Search by page name, description, Studio asset name or code; use Refresh to reload the list.
- Edit replaces the name, description, asset and full applicability selection while preserving enabled/disabled status.
- Disable a page to stop selecting it as the homepage. Another matching active page can then apply; otherwise the built-in homepage is used.
- Delete is available only after disabling. Deletion removes the configuration and its scopes, and keeps the Studio asset.
Managing configurations requires Pages access and page-management permission. Members who only use an assigned page do not need Studio management access. Their page actions still run under their own identity and data permissions, against the current published version.
For command parameters, see Page Commands.