---
sourceDocument: Australia Platform Analytics
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/now-intelligence

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Platform Analytics

ft:clusterId :

    - par

bundleId :

    - par

workflow :

    - Platform


---

# Included roles, tables, and jobs

# Roles, tables, and scheduled jobs included with Query Generation {#ariaid-title1}

Release version: Australia  
Updated March 12, 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 Roles, tables, and scheduled jobs included with Query Generation

Query Generation in ServiceNow Australia release provides a set of roles, tables, and scheduled jobs that enable semantic data processing and AI-powered search capabilities.
These components work together to manage entities, dimensions, indicators, and segments, facilitating enhanced query understanding and data retrieval within your ServiceNow instance.
Show full answer Show less  

## Roles

* **snquerygen.user:** Grants permission to call Query Generation services through an application. This role should be included in any app that integrates with Query Generation.
* **snquerygen.admin:** Provides admin-level access to Query Generation tables, allows customization of semantic metadata, manual segment creation, and access to the Health Page.
* Additional roles such as **snnowassistadmin.nsa.admin** and **aisadmin** include the user role and offer broader administrative capabilities.

## Scheduled Jobs

* **Generate Semantic Layer:** Creates entities, dimensions, and segments; cleans up unused segments and records. Runs on initial installation and on demand.
* **\[Query Generation\] Sync Segments Job:** Generates and synchronizes segments from various data sources and cleans up ineligible segments. Runs initially and weekly (Sundays).
* **\[Query Generation\] Semantic Entity Auto-Scaling Job:** Maintains synchronization of entity activation states and supports semantic scaling. Runs daily at 20:23.

## Tables

All tables require admin role access and are found under Query Generation in the ServiceNow Navigator. Key tables include:

* **Entity \[snquerygenentity\]:** Read-only table representing supported semantic tables with enabled semantic generation.
* **Dimension \[snquerygendimension\]:** Read-only representation of queryable columns for each entity.
* **Indicator Configurations \[snquerygenindicatorconfig\]:** Manually curated high-quality indicators used to boost search relevance.
* **Segments \[snquerygensegment\]:** Definitions providing context to queries (e.g., interpreting terms like "open" or "emergency"). Admins can manage these segments.
* **Manual Segment Configs \[snquerygensegmenttableconfig\]:** Manually created segments synced to the main segments table via scheduled jobs.
* **Utterance Bank \[snquerygenutterancebank\]:** Predefined phrases linked to database contexts, supporting natural language query matching. Editable by admins.
* **AI Search Search Profile \[aissearchprofile\]:** Configurations for search experiences, linked to search boxes, reusable across applications.
* **AI Search Indexed Sources \[aisdatasource\]:** Defines searchable content sources, editable by admins to resolve data indexing issues.
* **Logs \[snquerygenlog\]:** Records all Query Generation service calls for monitoring and troubleshooting.
* **Semantic Table Configurations \[snquerygentableconfig\]:** Controls which tables are semantically searchable, including child table settings.
* **Semantic Column Configurations \[snquerygencolumnconfig\]:** Allows customization of column metadata, active status, and descriptions tied to semantic tables.

## What This Enables for ServiceNow Customers

By leveraging these roles, tables, and scheduled jobs, ServiceNow customers can implement a powerful semantic data layer that improves AI-driven search accuracy and flexibility. Admins can customize metadata and segments to better reflect organizational context, while scheduled jobs ensure semantic data stays current and optimized. This foundation supports enhanced user experiences through natural language queries and relevant search results across ServiceNow applications.  
Several types of components are installed with Query Generation, including tables and scheduled jobs.

## Roles included {#tables-sched-jobs-query-gen__section_wxy_5rb_4gc}

{#tables-sched-jobs-query-gen__table_zxs_4r3_1gc__entry__3}

| Role name | Description | Contains roles |
|-|-|-|
| sn_query_gen.user | Allows the person with the role to call the Query Generation service through the app they are using. | None, but applications that call Query Generation should contain this role in their own user roles. |
| sn_query_gen.admin | Allows the user to access the Query Generation tables like an admin user. Can access the Health Page. Can customize semantic metadata and create manual segments. | * sn_nowassist_admin.nsa.admin * ais_admin * sn_query_gen.user {#tables-sched-jobs-query-gen__ul_sxn_scx_vgc} |
[ ]

{#tables-sched-jobs-query-gen__table_zxs_4r3_1gc}

## Scheduled jobs installed {#tables-sched-jobs-query-gen__section_fsw_xm3_cgc}

{#tables-sched-jobs-query-gen__table_gsw_xm3_cgc__entry__3}

| Scheduled job | Description | Default frequency |
|-|-|-|
| Generate Semantic Layer | Generates entities, dimensions, and segments. Cleans up unused segments and Entity and Source records. Segment generation works like the Sync Segments job.Runs when Query Generation is first installed and then on demand. | When first installed, then on demand |
| \[Query Generation\] Sync Segments Job | Generates segments from report sources, reports, indicator sources, modules, and filters. Synchronizes manual segments with segment table. Cleans up unused segments. Cleans up segments based on unused or otherwise ineligible reports, report sources, and indicator sources. | When first installed, then weekly, on Sundays |
| \[Query Generation\] Semantic Entity Auto-Scaling Job | Synchronizes entity activation states and helps with semantic entity scaling. | When first installed, then daily, at 20:23:00 |
[ ]

{#tables-sched-jobs-query-gen__table_gsw_xm3_cgc}

## Tables installed {#tables-sched-jobs-query-gen__section_hsw_xm3_cgc}

All tables require the admin role for access and are available under Query Generation in the Navigator.
{#tables-sched-jobs-query-gen__table_isw_xm3_cgc__entry__2}

| Table | Description |
|-|-|
| Entity \[sn_query_gen_entity\] | Representations of the tables that have semantic generation enabled for them (explicitly or through their parent tables) on the Semantic Table Configuration \[sn_query_gen_table_config\] table. Each Entity record corresponds to one supported table. Entity records are generated automatically, and this table is read-only. |
| Dimension \[sn_query_gen_dimension\] | Representation of queryable columns for every table that an Entity record references. Each record corresponds to one column. Dimension records are generated automatically, and this table is read-only. |
| Indicator Configurations \[sn_query_gen_indicator_config\] | List of high-quality indicators, as manually determined by administrators. At search time, these indicators get their own search and are included in the general indicator search. These indicators get a boost when the two searches are then merged. For more information, see [Indicator scope control](https://www.servicenow.com/docs/9p0U9718YS_M5ujwOatwzA#indicator-scope-control "Indicator Scope Control provides an admin-curated list that boosts selected Performance Analytics indicators in ambient AI search results, with optional custom descriptions to improve search accuracy."). |
| Segments \[sn_query_gen_segment\] | Reusable definitions that provide non-obvious context, to assist the semantic layer or LLM to select the correct entity, dimension, and values. For example, in the utterance "How many open emergency change requests are there?", a segment identifies that "open" means "active=true" and "emergency" is a Type, not a Priority. Admins can add new segments, delete existing segments, or edit segment names and descriptions. |
| Manual Segment Configs \[sn_query_gen_segment_table_config\] | Manually created segments. The \[Query Generation\] Sync Segments job syncs this table up to the Segments table. |
| Utterance bank \[sn_query_gen_utterance_bank\] | Predefined sentences and phrases mapped to database contexts and queries. User questions are compared to the utterance bank to see if a predefined mapping can apply. Admins can create, edit, and delete utterance banks. |
| AI Search Search Profile \[ais_search_profile\] | A container for all search experience configurations. A search profile is mapped to a specific experience you would like to expose in your app. Search Profile is  linked to a search box and can be used across applications. Admins can create, clone, and publish search profiles. |
| AI Search Indexed Sources \[ais_datasource\] | Records on this table reflect what content users can search on. The content can be tables on the instance or external tables. You have the necessary indexed sources by default. The sn_query_gen.admin role or higher is necessary to edit this table. The most likely use case is if the system cannot find the correct table and not all the indexed queries are fully applied. For more information, see [Common AI Data Explorer issues and fixes](https://www.servicenow.com/docs/uA0IDtFT5NUg_k9DxAVMLA "Use Query Generation logs to inspect failed or incorrect queries and identify common issues with AI Data Explorer responses."). |
| Logs \[sn_query_gen_log\] | A log of every call to Query Generation. For more information, see [Query Generation logs](https://www.servicenow.com/docs/L3WBnv87fPS8yQlUBhj0Uw "Every call to a Query Generator and its results are logged in the Query Generation Log [sn_query_gen_log] table."). |
| Semantic table configurations \[sn_query_gen_table_config\] | List of tables that Query Generation can search, whether semantic generation is enabled for that table, and whether child tables are included. Admins can create, edit, and delete these records. For more information, see [Add a table to the semantic data layer](https://www.servicenow.com/docs/DnI5HK_x_33jozN_85GrWQ#add-table-semantic-layer "Add more tables to the Query Generation semantic layer so that users can use ServiceNow Otto for Platform Analytics applications to ask questions about the data in those tables."). |
| Semantic column configurations \[sn_query_gen_column_config\] | Records for setting the domain, active status, and custom semantic descriptions and usage instructions for table columns. Must reference a table in sn_query_gen_table_config. For more information, see [Customize column descriptions and usage instructions](https://www.servicenow.com/docs/i1~~QehgpkihcmfFwayBZQ "Create custom column descriptions and usage instructions in the Semantic Column Configuration table so that customizations can be transferred between instances via update sets."). |
[ ]

{#tables-sched-jobs-query-gen__table_isw_xm3_cgc}