fso admins not able to see list in workspace

[Debasis Pati]

I have created one application and modules added in the sys_us list for fso workspace.
Now admin can see both the application and module in application navigator also in fso workspace list.
But the fso admins only can see the app and module in the application menu in the navigator but in workspace list they are not able to see.
I am not able to find what is wrong because the module role they are already having.
even the fso admin can see the application and module in the application navigator but not in the fso workspace only.

@Ankur Bawiskar any idea on this?

[Debasis Pati]

Hello @Ankur Bawiskar ,
I do not have any list applicability nor audiences for the list actually.
Still its not visible on the workspace.

[Ankur Bawiskar]

@Debasis Pati 

not visible for admin as well?

Did you create UX Category and add those UX lists under it?

did you check the link I shared?

[VJ_Srivastava]

Hello @Debasis Pati,

From a platform architecture standpoint, this visibility discrepancy perfectly illustrates the paradigm shift between the legacy UI16 framework and the modern Next Experience (Seismic) architecture.

In the classic UI, navigation visibility and data security were tightly coupled—if you had the role on the Application/Module, the navigation link appeared. In Configurable Workspaces like FSO, ServiceNow intentionally decoupled the presentation layer from the data layer. Access to the underlying table is still governed by standard ACLs, but the visibility of the UI components themselves (like Workspace Lists and Categories) is strictly governed by Audiences.

System Administrators inherently bypass these UI restrictions, which frequently creates false positives during testing.

To build robust, scalable workspace configurations, your engineering team must treat Audience definitions as a mandatory component of their deployment architecture, not just an afterthought. Standardizing the mapping of your operational roles (like fso_admin) to dedicated Workspace Audiences ensures seamless deployments, enforces a clean separation of concerns, and prevents these frustrating UI inconsistencies across environments.

[Tanushri]

Hi @Debasis Pati,

Thank you for highlighting this! While it looks like a minor backend configuration glitch, visibility issues like this directly impact the success and adoption of your Financial Services Operations (FSO) rollout.

When operational leaders like FSO Admins log in and cannot access the newly deployed applications they requested, it creates immediate process bottlenecks and degrades their confidence in the platform's readiness. The discrepancy between what the IT development team sees (as System Admins) and what the actual business user experiences is one of the most common causes of stalled User Acceptance Testing (UAT) and delayed go-lives.

Resolving this quickly by aligning the Workspace "Audiences" with your FSO admin roles will instantly restore that visibility and trust. Moving forward, incorporating strict persona-based testing—where your deployment teams are required to impersonate the actual operational users (like fso_admin) rather than relying on their overarching System Admin access, will eliminate these friction points before they ever reach your business stakeholders.