---
sourceDocument: Brazil Conversational Interfaces
sourceDocumentLink: https://www.servicenow.com/docs/r/conversational-interfaces

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Conversational Interfaces

ft:clusterId :

    - convint

bundleId :

    - convint

workflow :

    - Platform


---

# URL navigation in NLU

# (Legacy) URL navigation in NLU {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of (Legacy) URL navigation in NLU

URL navigation settings in ServiceNow's Natural Language Understanding (NLU) enable you to control where and how chat links open within different portals.
These settings allow you to specify default portals for various ServiceNow tables and customize link targets, such as opening links in popup windows.
This functionality applies across chat widgets, chat channels, and messaging channels.
Show full answer Show less  

## How URL Navigation Works

The system determines the portal to use for chat links by evaluating parameters in a specific order:

* **sysparmportal parameter:** If present in the chat widget URL, this portal is used.
* **Topic script variable:** Uses the portal specified in the topic script if set.
* **Default portal for Provider Channel Identity:** Uses the portal defined in the Provider Channel Identity table for chat integrations.
* **Default portal for a table:** Uses portal mappings defined in the URL navigation Chat Setting.
* **Global default portal:** Uses the global portal set by the system property `com.glide.cs.urlredirect.default.portal`.
* **Fallback:** If no other portal is specified, the Service Portal is used by default.

## Legacy URL Mappings and Properties

Legacy URL mappings configured before the Brazil release are retained and can now be viewed or managed via the URL navigation settings or the `syscsportalurlmapping` table. Two types of URL mappings exist:

* **Default mappings:** System properties that define default portals for key tables like Knowledge Base articles (`kbknowledge`), Catalog Items (`sccatitem`), and Users (`sysuser`). For example, Knowledge Base articles default to the Service Portal ("sp").
* **Custom mappings:** Properties that specify portal and table combinations, allowing more granular control. These mappings use placeholders to dynamically generate URLs based on portal and record data.

## Smart Links

Administrators can configure smart links to specify how URLs open based on patterns. For instance, you can set all Knowledge Base articles to open in a new window. This is managed through general chat settings, enhancing user experience by customizing link behavior.  
Use URL navigation settings to specify where and how chat links open. You can configure
certain links to open in a specific portal. You can also specify the link target, such as a popup
window.
Your base system instance provides default portals in which chat links to records from certain
ServiceNow tables are opened automatically. For example, Service Portal is the default portal used to display knowledge records from the
Knowledge \[kbknowledge\] table and also catalog items from the Catalog Item \[sc_cat_item\]
table.

Use URL navigation in Chat Settings to change these default mappings, as well as define custom mappings that map a portal URL to a specified ServiceNow table. The portal configurations apply to the chat widget, chat channels, and messaging channels.

## How URL navigation works {#url-navigation-ci__section_pq1_hvl_gtb}

To determine the portals to be used for chat links, the system evaluates the following information in the order listed:

1. <kbd class="ph userinput">sysparm</kbd> portal parameter - If you specified a sysparm_portal parameter in the instance URL for the chat widget, that portal is used.
2. Topic script variable - If you specified a portal in a topic script variable, that portal is used.
3. Default portal for Provider Channel Identity - If you specified a default portal in the Provider Channel Identity \[sys_cs_provider_application\] table for pre-built chat integrations or custom chat integrations, that portal is used. The default portal applies to the chat and messaging channels for the provider. For details on configuring the Provider Channel Identity, see [Create a channel identifier for your custom chat integration](https://www.servicenow.com/docs/AN8NK7pyNCN11DYhRUyHcA "Create a channel identifier for your custom chat integration in the Provider Channel Identities [sys_cs_provider_application] table.") in Custom chat integration framework.
4. Default portal for a table - Uses the portal value in the default portal mapping listed in URL navigation Chat Setting.
5. Global default portal - If you defined a global default portal using the com.glide.cs.url_redirect.default.portal system property, that global portal is used.
6. Service Portal - If you didn't define a global portal using the com.glide.cs.url_redirect.default.portal property, Service Portal is used.
{#url-navigation-ci__ol_om5_tgh_fqb}

## Legacy URL mappings defined in previous releases (fallback method) {#url-navigation-ci__section_wmn_vvl_gtb}

If you previously added the
com.glide.cs.portal_url_mapping.default.\<portal_value\>.\<table_name\>
property to create URL mappings that were used instead of the default URL mappings, those
properties are retained after you upgrade to the Brazil release.
However, you can now view the mappings using URL navigation in Chat
Settings or the URL Navigation \[sys_cs_portal_url_mapping\] table. There are two types of URL
mappings.

Default mappings
:   All system properties with the format
    com.glide.cs.portal_url_mapping.portal.\<table_name\> that define the
    default portal used for certain ServiceNow tables.  
    {#url-navigation-ci__table_u53_1pk_24b__entry__2}

    | Property | Description |
    |-|-|
    | com.glide.cs.portal_url_mapping.portal.kb_knowledge | Default portal context (URL mapping) to use for Knowledge Base articles. * Type: string * Default value: sp (Service Portal) {#url-navigation-ci__ul_pwc_3n4_24b} |
    | com.glide.cs.portal_url_mapping.portal.sc_cat_item | Default portal context (URL mapping) to use for Service Catalog items. * Type: string * Default value: sp (Service Portal) {#url-navigation-ci__ul_o4v_mp4_24b} |
    | com.glide.cs.portal_url_mapping.portal.sys_user | Default portal context (URL mapping) for sys_ user records. * Type: string * Default value: esc (Employee Service Center) {#url-navigation-ci__ul_ikf_cr4_24b} |
    [Table 1. Default URL mapping properties]

    {#url-navigation-ci__table_u53_1pk_24b}

Custom mappings
:   All system properties that define a portal and table combination using the format
    com.glide.cs.portal_url_mapping.\<portal_name\>.\<table_name\>. These
    mappings are retained as custom mappings. When the portal or table is specified with
    _default, it indicates that any portal or table is used.  
    The system determines the URL for custom mappings by evaluating the following values:

    * Portal and table/parent table
    * Portal and any table
    * Any portal and table/parent table
    * Any portal and any table
    {#url-navigation-ci__ul_oc1_lq4_gqb}

    {#url-navigation-ci__table_wtj_ztf_b4b__entry__2}

    | Property | Description |
    |-|-|
    | com.glide.cs.portal_url_mapping._default.kb_knowledge | Default for Knowledge URL mapping. * Type: string * Value:/{{portal}}?id=kb_article\&sys_id={{data.sys_id}} {#url-navigation-ci__ul_rv5_bt4_24b} |
    | com.glide.cs.portal_url_mapping._default.sc_cat_item | Default for Catalog Item URL mapping. * Type: string * Value: /{{portal}}?sys_id={{data.sys_id}}\&id={{data.table_name}}\&table={{data.table_name}} {#url-navigation-ci__ul_urw_nt4_24b} |
    | com.glide.cs.portal_url_mapping._default.sys_user | Default for User URL mapping. * Type: string * Value: /{{portal}}?id=user_profile\&sys_id={{data.sys_id}} {#url-navigation-ci__ul_vh3_qwj_f4b} |
    | com.glide.cs.portal_url_mapping._default._default | Default URL mapping for records other than knowledge articles, Service Catalog items, People (sys_user) records, publication records, and task records. * Type: string * Value: /{{portal}}?sys_id={{data.sys_id}}\&id=form\&table={{data.table_name}} {#url-navigation-ci__ul_o25_ybk_f4b} |
    [Table 2. Custom URL mapping properties]

    {#url-navigation-ci__table_wtj_ztf_b4b}

## Smart links {#url-navigation-ci__section_mbv_1vl_gtb}

As an admin, you can specify the target for URL links based on patterns that you specify. For
example, if you want all KB articles to open in a new window, you can configure the mapping in
general chat settings. For more information, see [(Legacy) Create a smart link preference](https://www.servicenow.com/docs/rf3DKl0MMKw5Xh4uTjteBg "Create smart links to specify where a URL should open. For example, the URL could open in a new browser window, in a new browser tab, in the chat window, or in a pop-up window.").

