ServiceNow CPQ: User Access Control

logik_admin_user_access_control.md
Raw file

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. For step-by-step instructions, see Create a case on Now Support for CPQ Customers.

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.

Access levels

  • NONE
  • READ
  • EDIT
  • ADMIN

Access areas

  • END_USER

  • CONFIG

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

  • TRANSACTION

    Users 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"
  • DEPLOY

    • Applies all blueprint, transaction, product catalog enrichment, and product filter deploys
    • Roles are either NONE or ADMIN UTILITIES
  • UTILITIES

    • Logs, user access, runtime clients, admin API keys, external connections, settings, webhooks, connections
    • Products (for Ecommerce tenants)

Tables

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

  • 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

Modifying access controls

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

[Omitted image "cpq-user-access-control-list.png"] Alt text: Admin: User Access Control

Steps:

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

    [Omitted image "cpq-user-access-control-list-tooltip.png"] Alt text: Admin: User Access Control

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

    [Omitted image "cpq-user-access-control-list-sample-csv.png"] Alt text: Admin: User Access Control

  3. Import the CSV file.

    [Omitted image "cpq-user-access-control-csv-import.png"] Alt text: Admin: User Access Control

    You will receive a message confirming success or failure.

    [Omitted image "cpq-user-access-control-csv-import-status.png"] Alt text: Admin: User Access Control

Changes to user list are now made.

[Omitted image "cpq-user-access-control-list-updated.png"] Alt text: Admin: User Access Control

Sample CSVs

Default all-access admin CSV:

SQL
name,userName,area,access,actionUser,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:

SQL
name,userName,area,access,actionUser 1,user.one@example.com,DEPLOY,ADMINUser 2,user.two@example.com,UTILITIES,ADMINUser 2,user.two@example.com,CONFIG,ADMINUser 2,user.two@example.com,TRANSACTION,ADMINUser 3,user.three@example.com,END_USER,END_USERUser 4,user.four@example.com,END_USER,END_USER,DELETEUser 5,user.five@example.com,CONFIG,ADMINUser 5,user.five@example.com,TRANSACTIONS,ADMINUser 5,user.five@example.com,MANAGED_TABLES,READUser 5,user.five@example.com,UTILITIES,ADMINUser 5,user.five@example.com,DEPLOY,ADMINUser 6,user.six@example.com,CONFIG,ADMIN

CSV adding user to the table "sampleTable":

SQL
name,userName,area,access,variableName,actionJohn Smith,john.smith@example.com,CONFIG,ADMIN,,UPSERTJohn Smith,john.smith@example.com,TRANSACTIONS,ADMIN,,UPSERTJohn Smith,john.smith@example.com,TABLE,ADMIN,sampleTableName,UPSERTJane Doe,jane.doe@example.com,MANAGED_TABLES,READ,,DELETEJane Doe,jane.doe@example.com,UTILITIES,,NONE
Search documentation
Search document titles and file paths on the australia branch