Understanding portal pages and navigation
Pages are the building blocks of a portal. Each page has a type that determines what it displays, what configuration it requires, and which portal types support it. A portal can contain as many pages as needed, each serving a different purpose or audience.
Page types and availability
The following page types are available in Storyteq CMP:
| Page type | What it displays | Key requirement | Available in |
|---|---|---|---|
Asset list |
A lens |
Assets portal |
|
Templates list |
Templates from a specific lens |
A lens |
Assets portal |
User adaptations list |
Adaptations created from templates by the current user |
None |
Assets portal |
Free-form content built with grids and widgets |
None |
All portal types |
|
Projects |
Projects filtered by type and state |
Project types defined in the system |
Projects portal |
Analytics |
A QLIK report embedded in the portal |
Workspace configuration for the report |
Analytics portal |
CMS pages support nesting, which allows sub-pages to be grouped under a parent page in the navigation. Other page types sit flat in the navigation and cannot be nested.
|
What you see here depends on your workspace’s configuration. An analytics page shows its report only once your workspace has been configured to connect to it. To change it, contact your administrator. Configure an analytics portal covers setting up an analytics portal. |
How navigation works
Pages are added and ordered via the portal’s Manage Navigation settings. Once added, a page appears as a navigation item in the portal and can be reordered by dragging it to the desired position.
CMS pages are the only page type that supports nesting. Nested CMS pages can be presented as a horizontal dropdown or a vertical sidebar. This is configured when the parent page is created. Nesting is supported up to four levels deep.
Links to external URLs or internal pages can also be added to the navigation alongside pages.
Pages can be hidden from navigation without being deleted. A hidden page remains accessible to users who have a direct URL, but does not appear in the portal navigation.
Page permissions
By default, all user groups assigned to a portal can access all pages within it. Access to individual pages can be restricted by toggling specific groups off in the page’s permissions settings.
Page permissions are based on the groups already assigned at the portal level. If a group requires access to a page, it must first be added to the portal. Only the user who created the page can set or update its permissions.
Understanding workspaces and portals explains how portal-level permissions work.