Skip to main content
With the ServiceNow access integration, you can manage who has access in ServiceNow from Opal:
  • Allow users to request just-in-time access to a ServiceNow group or grantable role from the web and Slack
  • Sync active users, groups, parent/child group nesting, and the roles each group grants
  • Grant and revoke group membership, direct role assignments, and group roles
  • Optionally create and deactivate ServiceNow users from Opal
  • Automatically revoke access when a time-bound grant expires
Opal connects to one ServiceNow instance through OAuth client credentials as a dedicated web-service-only integration user.
This is separate from the ServiceNow ticketing integration, which creates and updates ServiceNow catalog requests for Opal access requests. You can use either or both.

Supported resources

Opal syncs active users who have an email. By default it doesn’t create or deactivate users, so your identity provider can keep provisioning ServiceNow. You can turn user create and deactivate on in the app settings.

How ServiceNow access maps to Opal

  • Groups: each active sys_user_group appears as a ServiceNow Group. You can add and remove members (sys_user_grmember).
  • Group nesting: a child group with a parent is nested under that parent in Opal. Members of the child inherit the parent’s roles through that nesting.
  • Group roles: roles a group grants with inherits=true appear on the group. Opal adds or deletes those sys_group_has_role rows. Rows copied from a parent group (where ServiceNow sets granted_by) aren’t listed or revoked; the child nesting covers them instead. Rows with inherits=false aren’t listed, because members get nothing from them.
  • Roles: each grantable sys_user_role appears as a ServiceNow Role. Direct, active grants (sys_user_has_role with inherited=false) can be granted and revoked. Roles held only through a group or a containing role show as inherited and aren’t treated as direct grants. Requested or pending role grants aren’t access yet.
  • Users: when user management is enabled, granting access to someone who isn’t in ServiceNow creates a sys_user, and removing them deactivates and locks the account rather than deleting it. Opal never reactivates a deactivated user, because that would quietly restore their old groups and roles.

Limitations

  • Roles contained by another role (sys_user_role_contains) aren’t modeled separately; ServiceNow writes them like inherited group roles, with no field telling the two apart.
  • Elevated roles such as admin may require security_admin on the integration user; Opal surfaces ServiceNow’s refusal if the grant isn’t allowed.
  • Custom domains still use the instance.service-now.com (or servicenowservices.com) API host in Opal.

Requirements

Before you begin, you must:
  • Be an Opal Admin
  • Be a ServiceNow admin who can create a user, assign roles or ACLs, and register an OAuth application
  • Ask the Opal team to enable the ServiceNow access integration for your organization

Configuration steps

1. Create a ServiceNow integration user

In ServiceNow, go to All > Users and Groups > Users, and create a user for Opal.
  1. Select Web service access only.
  2. Set a User ID and password (you’ll use the user with OAuth, not basic auth, in Opal).
  3. Grant the user read access to these tables, and write access when the connection is read/write:
You can grant these through ACLs on a custom role. The user_admin role also works, and lets the integration user edit every non-admin user. Record the User ID for the OAuth application user in the next step.

2. Enable OAuth client credentials and create an OAuth application

  1. Turn on the system property glide.oauth.inbound.client.credential.grant_type.enabled so ServiceNow accepts the client-credentials grant.
  2. Go to System OAuth > Application Registry, select New, then Create an OAuth API endpoint for external clients.
  1. Set the application’s OAuth Application User to the integration user from step 1.
  2. Record the Client ID and Client Secret.

3. Create the ServiceNow app in Opal

In Opal, go to Inventory > + App and select ServiceNow. Fill in the following fields: Opal checks the OAuth credentials when you save the app. On the Setup tab, app validations confirm the integration user can read each required table. ServiceNow ACLs hide rows rather than returning 403, so an empty users or roles result fails validation. The ServiceNow app's Setup tab in Opal, with the Users, Roles, Groups, OAuth client ID, and OAuth client secret settings and passing app validations.

4. Import groups and roles

After you save the app, import the groups and roles you want to manage: on the app’s Assets tab, select Import assets, and turn on requests for them. Opal pulls membership and role grants only for imported items, so they appear after the next sync.

Troubleshooting

Last modified on November 19, 2026