Set up supplied landing pages in workspace
- UpdatedJan 30, 2025
- 6 minutes to read
- Yokohama
- Navigation and UI
Set up pre-configured reports and relevant data for agents on the landing page to help agents quickly find issues to resolve.
Before you begin
Role required: uxframework_designer
About this task

- Lists—Display a filtered list of records.
- Single Score—Displays the number of records in a filtered list.
- Time Series/Trend By—Displays a graph of record values over time.
To design your own landing page and add custom components to it, see Creating custom landing pages.
Procedure
- Navigate to All > Workspace Experience > Landing Pages.
- (Optional)
Click a landing page to modify.
If the landing page form is read-only, click here in To edit this record click here.
- (Optional)
Create a new landing page in one of the following ways.
Option Description Create a new landing page based on an existing page Select a landing page. If the landing page form is read-only, click here in To edit this record click here. You can modify this landing page and save it under a different name to create a new landing page that is based on this one. Create a landing page Click New. -
On the form, fill in the fields.
Table 1. UX Custom Content Extension form Field Description Name Landing page name. Order Order that the page shows. If you set up multiple landing pages, the page with a lower value takes precedence over the pages with higher values. Note: If there are permissions on any active page, an agent sees the page with their group or role set. The permissions takes precedence over a user who sees a page without permissions that is the lowest order.Applicability If applicability is for any page or a specific page. Applicable Page Registry Page in the UX page registry. Select Agent Workspace. This field only appears when you set Applicability to Specific Page. Application Name of the application that this landing page applies to. For example, if this value is ITSM Landing Pages, this landing page applies only to ITSM. Active Option that you select to determine whether the landing page appears. A page that is not active does not appear. Optional Page Title Title to display on the page. Available Child Slots Pre-defined named location for child elements. Layout Pre-defined list of containers to define the number of slots (columns) that display on a layout. - Right-click anywhere on the top banner and click Save.
-
Put containers on your landing page.
Containers hold the components on your landing page. You set up the containers on the landing page before putting components into them.
- On the UX Page Elements tab, click New Container.
-
On the form, fill in the fields.
Table 2. UX Page Element form Field Description Name Name of the container. Component Name of the container component. Parent element Landing page that this container is on. Border Option to select a border around your container. Can Collapse Toggle to enable agents to collapse this container on the landing page. Optional Container Title Title to display on the container. Type Type of styling for your visualization. You can choose the default styling (no background color) or visualization styling (gray background). Collapsed Toggle for the initial state of the container. Select this option to collapse the container when the landing page opens. Order Order that the container appears in on the landing page. The lower the value means the higher it appears on the landing page. Available Child Slots Pre-defined list of containers to define the number of slots (columns) that appear in a layout. Layout Column layout on the page. Valid values depend on the value of Available Child Slots. The total number of columns on a page is 12. For example, if you choose Container - 3 Up for Available Child Slots, the Layout value enables you to specify the width of the three columns. -
Click Submit.
You've created a container to put your landing page components in.
-
Add components to the containers on your landing page.
- On the UX Page Element Permissions tab, click New Visualization.
-
On the form, fill in the fields.
Table 3. UX Page Element form Field Description Name Name of your component. Component Name of the visualization component. Parent element Container that this component goes into. Order Order that the component shows in the container if there's more than one component. Report Report that you want to render in the container, for example, Open problems older than 30 days or Transactions by month for Last 12 months. Note: You must select either a Report or PA Widget, but you can't display both in a single container. If you define both, only the report displays.is_realtime Toggle to update the Report or PA Widget values in real time. PA Widget PA Widget that you want to render in the container, for example, a single score or a time series. Note: You must select either a Report or PA Widget, but you can't display both in a single container. If you define both, only the report displays.Optional Widget Label Title to display with the PA widget. Size Variant Size of the PA Widget. Choosing a size depends on how many containers are on the landing page and what you want to emphasize. Note: Not all sizes apply to all widgets.Border Toggle to put a border around the report or PA widget. Refresh Interval Number of minutes before the values of this component refresh. The interval begins when an agent navigates away from a landing page and ends when they come back to the landing page. Note: There is no auto-refresh, but an agent can click the browser's refresh button at any time.Visualization SysID Designated ID for the widget. Report Type Type of report that renders. - Click Submit.
-
Configure permissions for agents to access the landing page:
- On the UX Page Element Permissions tab, click New.
-
On the page, fill in the form.
Table 4. UX Page Element Permissions form Field Description Element Value of Optional Page Title. Role Role that an agent must have to see this landing page. Group Group that an agent must belong to in order to see this landing page. Application Application that this component applies to. Global means that the component applies to all applications. Any page element (including subelements) can have a restriction to a given set of roles or groups. If no element permissions are set on roles or groups, all agents see the element. If some element permissions are set, an agent needs just one role or group assignment to see the element.
- Click Submit.
-
To see your landing pages:
-
Under your profile picture, click Configure
Workspace.
Configure Workspace enables you to set up list categories, list filters, landing pages, the record types that agents can create, and the modules that appear in the pane on the far left of the screen.
- On the Workspace form, click the Landing Pages tab.
-
Under your profile picture, click Configure
Workspace.
What to do next
Set up lists for your agents so they can find additional issues to work on.