Skip to main content

ServiceNow permissions

Roles and permissions

  • Only administrators can configure the ServiceNow integration for their organization

To integrate Hyperproof and ServiceNow, you need two types of user accounts in both systems. To configure the integration and map data between the two systems, you must create a Hyperproof administrator account and a corresponding ServiceNow administrator account with the same email address. The administrator account must be configured before you can set up the integration connection between Hyperproof and ServiceNow.

Once the integration is configured, each Hyperproof user who creates or links Hyperproof tasks to ServiceNow tasks must have an account in Hyperproof and a corresponding user or service account in ServiceNow with the same email address. Those users perform the day-to-day task creation and task update functions.

Administrator permissions for configuring the ServiceNow integration

In ServiceNow, you must create at least one administrator account that is used to configure the Hyperproof integration. It should have the following roles:

  • admin

  • snc_read_only

These roles are used to query the sys_ui_* tables, so fields are rendered when creating a new task in Hyperproof. No other ServiceNow preset roles or ACLs allow the same access. The snc_read_only role restricts the user to only read access on everything it can see.

The administrator account must have the Identity type set to MACHINE, with the Web service access only setting enabled.

User permissions for integrating Hyperproof and ServiceNow tasks

In ServiceNow, create a user or service account for each user who will create and/or link Hyperproof tasks to ServiceNow tasks. These users must have the following roles assigned:

  • itil

  • catalog_admin

OR

  • sn_incident_write

  • sn_problem_write

  • sn_request_write

These roles are used to read and write data to the linked ServiceNow object and keep it in sync with the coordinating Hyperproof task.

Note

See the official ServiceNow documentation for more information on base system roles.

Add these users to assignment groups in ServiceNow. Membership in assignment groups determines which ServiceNow tasks and task types the user can create. Users in Hyperproof are matched with users in ServiceNow based on their email address. To ensure that tasks are assigned to the correct person in ServiceNow they must have the same email address in both systems.

In this section: