- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-24-2023 03:50 PM
Hello
I am unable to find what scopes are available to restrict access defined by ServiceNow OAuth WebApp.
For a specific pair of client-id and client-secret.
Please provide a reference of what available scopes and their restrictions.
Thank you
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-25-2023 07:13 PM
@jeff00seattle in OAuth2.0 no need to define any scope seperately, there are ACL on auth credential table which allow same user to read the token who has generated.
If you look user field in oauth credential table, same user can read token otherwise will show null for any other API user.
Hope this will help you.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-24-2023 04:07 PM
Hello @jeff00seattle,
According to the ServiceNow documentation, when you select ServiceNow as an OAuth provider, the default and only scope available is useraccount. This scope grants access to the user’s account information and preferences. You cannot configure custom scopes or restrict access to specific resources or endpoints.
If you want to use different scopes or grant types, you may need to use an external OAuth provider, such as Google or Facebook, and register your ServiceNow instance as an OAuth client. You can find more information on how to set up your ServiceNow instance as an OAuth client using the.... You can also learn how to manage OAuth tokens stored in ServiceNow.
I hope this helps you understand the scope limitations of ServiceNow OAuth WebApp
Kind Regards,
Swarnadeep Nandy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-25-2023 12:09 PM
- What is "useraccount" scope?
- For Table API, are there scope assignments per table?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-25-2023 04:22 PM
My apologies. It seems from Tokyo onwards; you can configure your own auth scopes.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-25-2023 07:13 PM
@jeff00seattle in OAuth2.0 no need to define any scope seperately, there are ACL on auth credential table which allow same user to read the token who has generated.
If you look user field in oauth credential table, same user can read token otherwise will show null for any other API user.
Hope this will help you.