---
sourceDocument: Australia Platform Analytics
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/now-intelligence

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Platform Analytics

ft:clusterId :

    - par

bundleId :

    - par

workflow :

    - Platform


---

# Activate record-level analysis

# Configure record level analysis in AI Data Explorer {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 Minuten Lesedauer

Get more detailed answers based on the content of individual records to provide more meaningful insights.

## Vorbereitungen

Roles required: now_assist_explorer_admin or higher

## Warum und wann dieser Vorgang ausgeführt wird

Record-level analysis provides deeper insights into your data. You can activate it as an administrator. You can activate it as an opt-in, where you specify the tables to which it applies, or as an opt-out, where it applies to all
tables you don't specify. Whether activated or not, queries that touch on more than 50 records in a table aren't supported.  
Warnung:  
Take care when activating record-level analysis for a table with record-level security. The LLM applies the record-level security when analyzing records, but it applies only report_view ACLs when the exploration is shared. Therefore, users may see data about records that they are not authorized to access when an exploration is shared with them.

## Prozedur

1. Navigate to AllNow Assist AdminSkills.
2. In the product area pane, select Data and AnalyticsAnalytics.
3. In Now Assist skills for Analytics, search for the analytics exploration skill.
4. If the Activate skill button is visible for this skill, press it to activate the skill.
5. If the Deactivate skill button is visible for this skill, expand the 3-dot menu ![Menu icon]() and select Edit.  

   <br />

6. Select Advanced analysis from the menu, which opens the Record level analysis page.
7. Toggle on Enable record analysis.  
8. In the Enable for field, select whether to create an include list or an exclude list of tables.

   | Option | Description |
   | Selected tables | Select a list of tables to which record level analysis will apply. Record level analysis will not apply to any other tables. |
   | All except selected tables | Select a list of tables to which record level analysis won't apply. Record level analysis will apply to all other tables. |
   |-|-|

   {#record-level-analysis__choicetable_vhl_1zh_zgc}
9. In the Supported tables or Excluded tables field, select which tables to include or exclude, respectively.
10. Select Save and continue.
11. Finish configuring the skill as described in [Activate AI Data Explorer skills](https://servicenow-prod.fluidtopics.net/gmyj5F8YHNXsZgEFR~GVOA "Enable AI Data Explorer skills under Now Assist skills for Data and Analytics to give users AI-assisted, shared spaces to explore data."), or exit if the skill is already activated and you don't wish to make further changes.
{#record-level-analysis__steps_yhs_cxg_zgc}

## Simple request with and without record level analytics {#record-level-analysis__example_psh_3b3_zgc}

You don't have record level analytics enabled, and you open an exploration and ask for all open incidents. You're told "There are currently 40 open incidents. This reflects all incidents that remain unresolved at this time."  

Now you enable record level analytics on the instance. You choose an opt-in approach and specify Incident \[incident\] as the only table included in record level analytics.  

Finally, you ask the same question again in an exploration, asking for all open incidents. Now the response includes details about the differences between open incident records. You're told "There are 40 open incidents currently. Among these, several are marked as 1 - Critical priority, including issues such as inability to launch VPN clients, rain leaking on the main DNS server, and multiple SAP application outages. The most common categories for open incidents are inquiry / help, software, and hardware, with critical incidents distributed across all three."