---
sourceDocument: Brazil Sales Customer Relationship Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/order-management

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Sales Customer Relationship Management

ft:clusterId :

    - omgmt

bundleId :

    - omgmt

workflow :

    - Customer and Industry


---

# ServiceNow CPQ: User Access Control

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

Release version: Brazil  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 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 ServiceNow CPQ: User Access Control

The User Access Control feature in ServiceNow CPQ allows administrators to manage user permissions across various access areas such as configuration, transactions, managed tables, deployment, and utilities.
This control is critical for defining and restricting what users can view or modify within the CPQ environment.
The feature is available starting from the Brazil release and must be enabled through a ServiceNow support request.
Show full answer Show less  

## Key Features

* **Access Levels:** Permissions are categorized into NONE, READ, EDIT, and ADMIN levels, defining users' capabilities from no access up to full administrative control.
* **Access Areas:** Includes ENDUSER, CONFIG (configuration), TRANSACTION, MANAGEDTABLES, DEPLOY (deployment-related activities), and UTILITIES (logs, APIs, settings, etc.).
* **Role-Based Permissions:** Specific user roles such as ENDUSER, CONFIGADMIN, TRANSACTIONADMIN, MANAGEDTABLESADMIN, DEPLOYADMIN, and UTILITIESADMIN correspond to different system endpoints and functionalities, ensuring granular control over user actions.
* **Table-Specific Permissions:** Access can be further refined to individual tables, allowing users to have edit or read rights on specific tables even if their overall managed tables access is more restrictive.
* **Management via CSV Import:** Admins can modify user access levels by importing CSV files through the User Access utility, enabling bulk updates, additions, or deletions of user permissions efficiently.

## Practical Use for ServiceNow Customers

Customers can leverage this utility to tightly control who can configure products, manage transactions, deploy catalogs and filters, or access system utilities within the CPQ application. This ensures compliance with organizational policies and reduces risk by limiting administrative capabilities to authorized personnel only.

By using the CSV import feature, administrators can quickly update access permissions in bulk, saving time in managing user roles and ensuring accurate and consistent enforcement of access controls across the CPQ environment.

## Next Steps

* Submit a support case to enable the User Access Control feature if not already active.
* Use the User Access utility to review current user roles and permissions.
* Prepare CSV files following provided examples to assign or modify user access across various CPQ areas and tables.
* Import CSV files to apply changes and verify success messages to confirm updates.  
View access types, access areas, and user roles that can be managed via the User Access utility.  
Note:  
This feature must be enabled by support request. Create a support case by using the [ServiceNow Support portal](https://support.servicenow.com). For step-by-step instructions, see [Create a case on Now Support for CPQ Customers](https://support.servicenow.com/kb?sys_kb_id=d67d3e71475d7a90f64de825126d4326&id=kb_article_view).

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

For basic user access in ServiceNow CPQ, see [User access](https://servicenow-prod.fluidtopics.net/GF2UmtSYsXRFSVIvIg1Ixg "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.  
Note:  
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


