---
sourceDocument: Australia Sales and Order Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/order-management

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Sales and Order Management

ft:clusterId :

    - omgmt

bundleId :

    - omgmt

workflow :

    - Customer and Industry


---

# CPQ: User Access Control

# CPQ: User Access Control {#ariaid-title1}

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

View access types, access areas, and user roles that can be managed via the User Access utility.  
Hinweis:  
This feature must be enabled by support request.

Use the User Access utility to manage access to CPQ Admin. Admin users have full admin access unless their access level is modified via CSV import.

For basic user access in CPQ, see [User access](https://servicenow-prod.fluidtopics.net/kuKo5qPYJ7IcipMKfDfAzg "Learn how to grant or revoke admin access for a user. Existing users have admin access by default, while new users have only end-user access.").

## Access levels {#logik_admin_user_access_control__access_types}

* NONE
* READ
* EDIT
* ADMIN
{#logik_admin_user_access_control__ul_srj_f1l_fhc}

## Access areas {#logik_admin_user_access_control__areas}

* END_USER
* CONFIGUsers with ADMIN can use the Matrix Loader, including product filters and the catalog enrichment script MANAGED_TABLES.

* TRANSACTIONUsers with ADMIN can use the Matrix Loader.

* MANAGED_TABLES
* TABLE  
  Applies permissions for an individual table listed in addition to any MANAGED_TABLES access level. Examples:
  * EX: MANAGED_TABLES: NONE + TABLE "myTable" Edit = ability to edit "myTable" only
  * EX: MANAGED_TABLES: READ + TABLE "myTable" Edit = ability to read all tables and edit "myTable"
  {#logik_admin_user_access_control__ul_pg5_y1l_fhc}
* DEPLOY
  * Applies all blueprint, transaction, product catalog enrichment, and product filter deploys
  * Roles are either NONE or ADMIN UTILITIES
  {#logik_admin_user_access_control__ul_yjl_1bl_fhc}
* UTILITIES
  * Logs, user access, runtime clients, admin API keys, external connections, settings, webhooks, connections
  * Products (for Ecommerce tenants)
  {#logik_admin_user_access_control__ul_ppz_fbl_fhc}
{#logik_admin_user_access_control__ul_fgn_h1l_fhc}

## Tables {#logik_admin_user_access_control__section_dsj_yxq_qhc}

User access can be limited to specific tables via CSV or API.  
Hinweis:  
These are additive permissions with the overall tables permission set, so if the user has read access for all tables, the individual permission of NONE would have no effect.

## User roles {#logik_admin_user_access_control__section_gqq_mcl_fhc}

* END_USER: This is the only permission for the runtime
* CONFIG_NONE / CONFIG_READ / CONFIG_EDIT / CONFIG_ADMIN
  * READ correlates to GET endpoints
  * EDIT additionally correlates to POST PUT PATCH DELETE endpoints
  * ADMIN additionally correlates to Matrix Loader endpoints
  {#logik_admin_user_access_control__ul_xhw_tcl_fhc}
* TRANSACTION_NONE / TRANSACTION_READ / TRANSACTION_EDIT / TRANSACTION_ADMIN
  * READ correlates to GET endpoints
  * EDIT additionally correlates to POST PUT PATCH DELETE endpoints
  * ADMIN additionally correlates to Matrix Loader endpoints
  {#logik_admin_user_access_control__ul_cjw_xcl_fhc}
* MANAGED_TABLES_NONE / MANAGED_TABLES_READ / MANAGED_TABLES_EDIT / MANAGED_TABLES_ADMIN
  * READ correlates to GET endpoints
  * EDIT additionally correlates to POST PUT PATCH DELETE endpoints
  * ADMIN additionally correlates to Matrix Loader endpoints
  {#logik_admin_user_access_control__ul_odh_ycl_fhc}
* DEPLOY_NONE / DEPLOY_ADMIN (no EDIT or READ): ADMIN everything deployment related, including Product Filter Rules and Product Catalog Enrichment Deployments
* UTILITIES_NONE / UTILITIES_READ / UTILITIES_ADMIN (no EDIT)
  * READ correlates to GET endpoints
  * ADMIN correlates to everything else
  {#logik_admin_user_access_control__ul_jd1_bdl_fhc}
{#logik_admin_user_access_control__ul_jmt_ncl_fhc}

## Modifying access controls {#logik_admin_user_access_control__modifying_access_controls}

Admin users can modify access via CSV upload (Admin \> Utilities \> User Access). The User Access list shows existing users.

Steps:

1. Hover a tooltip to view a userʼs access.

2. Create a CSV file to add users, make changes to users, or delete users. (See below for sample CSV files.)

3. Import the CSV file.

   You will receive a message confirming success or failure.

{#logik_admin_user_access_control__ol_qmk_fdl_fhc}

Changes to user list are now made.

## Sample CSVs {#logik_admin_user_access_control__section_mtl_zxq_qhc}

Default all-access admin CSV:

    name,userName,area,access,action
    User,email@example.com,DEPLOY,ADMIN,
    User,email@example.com,UTILITIES,ADMIN,
    User,email@example.com,CONFIG,ADMIN,
    User,email@example.com,TRANSACTION,ADMIN,
    User,email@example.com,MANAGED_TABLES,ADMIN, 

Example complex-access CSV:

    name,userName,area,access,action
    User 1,user.one@example.com,DEPLOY,ADMIN
    User 2,user.two@example.com,UTILITIES,ADMIN
    User 2,user.two@example.com,CONFIG,ADMIN
    User 2,user.two@example.com,TRANSACTION,ADMIN
    User 3,user.three@example.com,END_USER,END_USER
    User 4,user.four@example.com,END_USER,END_USER,DELETE
    User 5,user.five@example.com,CONFIG,ADMIN
    User 5,user.five@example.com,TRANSACTIONS,ADMIN
    User 5,user.five@example.com,MANAGED_TABLES,READ
    User 5,user.five@example.com,UTILITIES,ADMIN
    User 5,user.five@example.com,DEPLOY,ADMIN
    User 6,user.six@example.com,CONFIG,ADMIN 

CSV adding user to the table "sampleTable":

    name,userName,area,access,variableName,action
    John Smith,john.smith@example.com,CONFIG,ADMIN,,UPSERT
    John Smith,john.smith@example.com,TRANSACTIONS,ADMIN,,UPSERT
    John Smith,john.smith@example.com,TABLE,ADMIN,sampleTableName,UPSERT
    Jane Doe,jane.doe@example.com,MANAGED_TABLES,READ,,DELETE
    Jane Doe,jane.doe@example.com,UTILITIES,,NONE