---
sourceDocument: Australia ServiceNow AI Platform Capabilities
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/servicenow-platform

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia ServiceNow AI Platform Capabilities

ft:clusterId :

    - platcap

bundleId :

    - platcap

workflow :

    - Platform


---

# User criteria migration

# User criteria migration {#ariaid-title1}

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

Service catalog user criteria records provide access control for service catalog items
and categories.  
You can migrate your access controls to use user criteria. The user criteria feature is automatically enabled for new instances. If you upgrade your instance, a script runs to determine current access control usage.

* If your instance does not use [entitlement-based](https://servicenow-prod.fluidtopics.net/FVAFJwPbrZP~KvsZaocatQ "Service catalog supports several ways to control access to a catalog item or category. These controls are also known as catalog entitlements.") access controls, the user criteria feature is automatically enabled.
* If your instance does use entitlements, the user criteria feature is not enabled. If you want to use user criteria, use the procedure described on this page to migrate your access controls from entitlements to user criteria.
{#c_MigrtSvcCatUserCriteria__ul_onm_ndl_1r}

Migrate to user criteria to provide more reuse, control, and flexibility compared to
entitlements.

For example, you can use a single criteria record to make multiple catalog items available to
only users who meet all these requirements:

* Are located in EMEA or APAC
* Belong to ACER
* Are in the Training department
{#c_MigrtSvcCatUserCriteria__ul_xx2_tdl_1r}

## Migrate to Service Catalog user
criteria {#ariaid-title2}

Service Catalog enables you to
maintain the required access controls to your service catalog while migrating from
entitlements to user criteria.

### Vorbereitungen

Role required: admin

### Warum und wann dieser Vorgang ausgeführt wird

### Prozedur

1. Navigate to AllService CatalogCatalog AdministrationProperties and verify that the user criteria feature is not already enabled on your system.  
   * If the property Use "User Criteria" to define access to catalog items and categories (glide.sc.use_user_criteria) is set to true, you can skip the following steps. The user criteria feature is automatically enabled because entitlements were not used in your old system.
   * If this property is set to false, continue with the following steps. The user criteria feature has not been enabled yet on your system.
   {#t_UserCriteriaMigrationProcess__ul_llg_dgl_1r}
2. To preview the user criteria feature, set the service catalog property Enable both "User Criteria" and "Entitlement" related lists for catalog items and categories when migrating from entitlements (glide.sc.user_criteria_migration) to true.  
   This option lets you compare user criteria records and entitlements before you fully switch to user criteria.
3. Inspect your service catalog items and categories to identify access control sets that you can configure user criteria records for.  
   Review your current entitlements and record your current design for access controls. Focus on identifying patterns where multiple items have the same combination of location, group, and so on. Each combination is a possible access control set.
4. [Create a user criteria record](https://servicenow-prod.fluidtopics.net/6_4mzQd0BIzaeEpJFnMj1g#t_CreateAUserCriteriaRecord "Create a user criteria record to define conditions that are evaluated against user records.") for each access control set that you identified from your inspection of the service catalog.  
   You have a step with a list, note, and image.
5. [Apply these user criteria records](https://servicenow-prod.fluidtopics.net/wIEvwFtoWm371ujhq1HJQw "An administrator can control access to content in the service catalog by creating and applying user criteria records.") to the items and categories identified, replacing the equivalent entitlements.
6. Enable user criteria on your system by setting the [service catalog property](https://servicenow-prod.fluidtopics.net/wY39nS27LqiZh4zQdcnaiw "The Service Catalog application contains properties used to configure various settings in the application.") Use "User Criteria" to define access to catalog items and categories (glide.sc.use_user_criteria) to true.  
   When this property is set to true, any remaining entitlements are no longer used.  
   Hinweis:  
   Scripts in user criteria cannot reference the category or catalog item as current as entitlement scripts do. For scripts in user criteria, use the user_id available for the user currently being evaluated against the category or catalog item.

## Data structure differences {#ariaid-title3}

There are significant data structure differences between entitlements and user
criteria, which you must be aware of while migrating.
Using entitlements, the following tables are loaded into memory and evaluated before
rendering.

For catalog items:  
Abbildung : 1. Entitlements Data Structure - Catalog Items

For categories:  
Abbildung : 2. Entitlements Data Structure - Categories The user criteria architecture collects all user attributes in the User Criteria
\[user_criteria\] table.

User criteria records can link to items and categories, as follows.  
For catalog items:

* Catalog Item Available for \[sc_cat_item_user_criteria_mtom\]
* Catalog Item Not Available for \[sc_cat_item_user_criteria_no_mtom\]
{#r_UserCriteriaDataStructureChanges__ul_d2t_zll_1r}  
Abbildung : 3. User Criteria Data Structure - Catalog Items  
For categories:

* Category Available for \[sc_category_user_criteria_mtom\]
* Category Not Available for \[sc_category_user_criteria_no_mtom\]
{#r_UserCriteriaDataStructureChanges__ul_xgj_2ml_1r}  
Abbildung : 4. User Criteria Data Structure - Categories