sys_user_group table not visible in UI Action table dropdown in scoped app

[deepaktomar]

Hi All,

I am working on a scoped application and trying to create a UI Action on the sys_user_group table.

• In Global scope, the sys_user_group table is visible in the Table dropdown when creating a new UI Action.

• But in my custom scoped app, the sys_user_group table is not available in the dropdown.

• I have already verified that the table is active and verified table application access set to 'All application scope'.

• This looks like a scope-related restriction, since Global scope shows it but my scoped app does not.

My questions are:

1. How can I make the sys_user_group table available in my scoped application’s UI Action table dropdown?

2. Is there a recommended best practice for handling this (e.g., extending sys_user_group into my scope vs. updating access)?

Any guidance on the correct approach would be appreciated.

Thanks,
Deepak Tomar

[aruncr0122]

Hi Deepak,

This is a common scope restriction in ServiceNow. Global tables like sys_user_group don’t automatically appear in scoped app dropdowns (like UI Action table selection), even if you set Application Access to "All application scopes."

What you can do:

Switch to Global scope and open System Definition > Tables > sys_user_group.

Confirm Accessible from = All application scopes.

Check Can create, Can read, and Extensible.

Allow cross-scope access:

Go to System Applications > Application Cross-Scope Access.

Add a record:

Source Scope = your app

Target Scope = Global

Target Type = Table

Operation = Read / Create (as needed)

Status = Allowed

Switch back to your scoped app. Now sys_user_group should appear in the UI Action table dropdown.

Best practice:

If the UI Action is generic, create it in Global scope and call your scoped logic from there.

Avoid extending sys_user_group unless you truly need custom fields—it can cause upgrade issues.

[mayankkumar]

Hi @deepaktomar,
Try this ->
Tick the Allow Configuration and can create and update on the table record then you will be able to do so
Refer Image:

Let me know if you need further help

--------------------------------------------------------------------------------------------------------------------------------------------------
Please mark my response helpful and accept as solution
Thanks & Regards
Mayank

[mujeebqasimi]

This is a scope thing. You generally don’t add a UI Action to a global table (like sys_user_group) from a private scope. The clean pattern is: put the button on the global table in Global, and have that button call code in your scoped app via a restricted-caller allowlist. Extending sys_user_group to “pull it into your scope” isn’t supported and won’t fix the picker, so skip that.
Reference:
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0746734