---
sourceDocument: Australia ServiceNow AI Platform user interface
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/platform-user-interface

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia ServiceNow AI Platform user interface

ft:clusterId :

    - platux

bundleId :

    - platux

workflow :

    - Platform


---

# Embedded Help roles

# Embedded Help roles {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Embedded help content can be targeted to users with a specified role who access the UI page.
All roles that contain the role also see the content, unless another topic targeted to their role exists for the same page.

For example, if you add embedded help content for the itil role that
describes your business process for entering incidents, the itil_admin role also sees the
content. If you write a different topic with the itil_admin role, the itil_admin sees that
content instead of the itil content.

## Embedded help role priority

The embedded help role priority is stored in the Embedded Help Role
Priority \[sys_embedded_help_role\] table. Each role is assigned a default priority order
number based on the role name in the Roles \[sys_user_role\] table.  
{#embedded-help-roles__table_txw_bc5_2z__entry__2}

| Order number | Role name |
|:-|:-|
| 10 | admin Examples: admin, chat_admin, pa_admin, survey_admin Exception: itil_admin |
| 100 | manager or itil_admin Examples: itil_admin, catalog_manager, content_manager, sla_manager |
| 300 | itil (only) |
| 1000 | All other roles or no role (ESS user) Examples: approver_user, financial_management_user, personalize_form, template_editor |
[Table 1. Default embedded help priority order numbers]

{#embedded-help-roles__table_txw_bc5_2z}

The priority executes from the lowest number to the highest, meaning that embedded help
content with no role displays only if no other content is available for the UI page and the
user's role. All base system content is targeted to a role unless the content is intended for
all users, including ESS users. When you add a role, such as a role for a custom application, it is automatically added to the Embedded Help Role Priority \[sys_embedded_help_role\] table with the appropriate default order. You
can modify the order of priority as needed.

If a page requires different help content for different roles,
separate topics must be added. For example, users with any role can access the
incident.do page, and it opens with a view appropriate for their
role.

The following list describes how content for different roles can be targeted for the Incident
form.

Admin
:   Provides information and links to help with configuring the Incident form.

itil_admin
:   Describes how to monitor the progress of the incident.

itil
:   Describes how to work on an incident.

No role
:   Explains what the user can review and modify in the Self-Service view of the Incident
    form.
* **[Modify embedded help role priority](https://servicenow-prod.fluidtopics.net/YW7beRhSdQA6UzIx_pUJdA)**   
  You can modify the default order of priority that is assigned to a role in the Embedded Help Role Priority \[sys_embedded_help_role\] table. The priority order determines what embedded help content a user accesses on a UI page, based on roles assigned to the user.