---
sourceDocument: Brazil Enable AI
sourceDocumentLink: https://www.servicenow.com/docs/r/intelligent-experiences

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Enable AI

ft:clusterId :

    - platai

bundleId :

    - platai

workflow :

    - Platform


---

# Configuring pages

# Configuring pages in AI Control Tower {#ariaid-title1}

Release version: Brazil  
Updated September 21, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read  
View and govern your AI portfolio using terms and visualizations tailored to your organization.

## Key benefits {#aict-configuring-page-widgets__section_key_benefits}

* Present AI Control Tower charts and details in your organization's own terms instead of the default labels.
* Provide data for a specific business unit or reporting period by building a condition into a card.
* Direct users from a card to a different list, report, or page instead of the default destination.

{#aict-configuring-page-widgets__ul_key_benefits}

AI Control Tower pages ship with a default set of cards, titles, and visualizations that you can configure as needed.
Figure 1. Editing cards on the AI Control Tower Home page

Every configurable card exposes a set of presentation settings, which let you match a page to the vocabulary and reporting style your organization already uses. For example, you can update a card title and subtitle, the chart
type, its data labels and legends, and the number of rows and sort direction in a ranked list. The exact settings available depend on the card.

Cards that read directly from tables on your instance also provide a condition builder, so you can narrow a card to the subset of records a page is meant to report on. Cards that retrieve their data from an API provide
presentation settings only.

## Required roles {#aict-configuring-page-widgets__section_kz1_s4s_qkc}

The aix_config_admin role is required to edit cards on AI Control Tower pages. The sn_ai_governance.workspace_admin role includes this role.

## How configurations are saved and applied {#aict-configuring-page-widgets__how-configurations-persist}

Card configurations apply to all AI Control Tower users. Every user sees a saved configuration the next time the page loads.

Configurations are stored as metadata that layers over the default card, rather than as a copy of the card. When editing a card, an unset or cleared value uses the original behavior.  
Note:  
Hiding information in a card changes only what the page presents. It doesn't restrict access to the underlying records, which remain governed by the access controls on your instance.

## Configurations and application upgrades {#aict-configuring-page-widgets__configurations-and-upgrades}

Configurations remain in place through an application upgrade. When AI Control Tower is upgraded, saved configurations for cards that still exist are reapplied automatically, and the pages continue to show the configured titles, conditions, and display options.

Cards introduced by a new version appear with their shipped settings, which an administrator can then configure.

## Important considerations {#aict-configuring-page-widgets__configuration-considerations}

* Configurations aren't scoped to a domain. Separate domains on a domain-separated instance can't have different versions of the same page.
* Card titles and labels that an administrator enters are stored as typed and aren't translated.
* Configuration is available on all pages and tabs except Activity Center, the Inventory list views, the Policies tab, and Settings.
* If the available settings don't cover a change your organization needs, you can extend pages with pro-code tools. For more information, see [Creating or extending pages with pro-code tools](https://www.servicenow.com/docs/g1JS0KJ208o3I2FXnNlycA "Extend your AI Control Tower pages beyond the built-in configuration options with the ServiceNow Lux Lab for VS Code extension.").

## Use cases {#aict-configuring-page-widgets__section_n1h_vps_qkc}

Matching card titles to internal terminology
:   An organization refers to its onboarded AI systems as registered assets rather than inventory. A workspace administrator changes the title of the inventory card on the Home page to Registered AI assets, so the page uses the
    same term that appears in the organization's internal governance process. Every user who opens the Home page sees the new title.

Preparing a page for a leadership review
:   A governance team presents AI system scores in a monthly leadership review, where a list of five systems is more detail than the meeting needs. A workspace administrator reduces the ranked list on the Monitor page to the two
    lowest-scoring systems and sets the sort direction to show the largest score declines first, so the page opens on the systems that need attention.

Narrowing a card to a reporting period
:   An organization reports on the AI systems it onboarded during the current fiscal year, but the inventory card counts every system on the instance. Because the card reads directly from a table, a workspace administrator adds
    a condition that limits it to systems created in the last year. The card count and the page it navigates to both reflect the condition.
* **[Configure a page card in AI Control Tower](https://www.servicenow.com/docs/~yyGqiObfO7sOxPBrc41ag)**   
  Change how a card presents its data so that a page matches the terminology, level of detail, and reporting focus your organization works with.

**Related tasks**   

* [Configure a page card in AI Control Tower](https://www.servicenow.com/docs/~yyGqiObfO7sOxPBrc41ag "Change how a card presents its data so that a page matches the terminology, level of detail, and reporting focus your organization works with.")

