User Access Control reference

Control Admin access levels using CSV imports. Assign NONE, READ, EDIT, or ADMIN permissions to specific areas.

Note: The User Access utility is enabled via a support request. Open a ticket by using the ServiceNow Support portal. For step-by-step instructions, see Create a case on Now Support for CPQ Customers.

Access levels

• NONE

• READ

• EDIT

• ADMIN

Access areas

• END_USER

• CONFIG

  Users with ADMIN can use the Matrix Loader.

• TRANSACTION

  Users with ADMIN can use the Matrix Loader, including product filters and the catalog enrichment script.

• MANAGED_TABLES

• TABLE

  Applies permissions for an individual table listed in addition to any MANAGED_TABLES access level. Examples:

  • MANAGED_TABLES: NONE + TABLE “myTable” Edit = ability to edit “myTable” only

  • MANAGED_TABLES: READ + TABLE “myTable” Edit = ability to read all tables and edit “myTable”

• DEPLOY

  • Applies all blueprint, transaction, product catalog enrichment, and product filter deploys

  • Roles are either NONE or ADMIN

• UTILITIES

  • Logs, user access, runtime clients, admin API keys, external connections, settings, webhooks, connections

  • Products (for Ecommerce tenants)

• Access to specific resources

  Tables: Users can be limited to specific tables they have access to. This is done via CSV as well as API.

User roles

• 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

• 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

• 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

• 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

Related topics

Using CPQ user access management

User access