Access Analyzer says "Passed" but sys_user list columns are completely blank (OOTB Instance)

jordimsant
Mega Sage

Hi everyone,

I am facing a very strange issue on a brand new, completely clean OOTB (Out-Of-The-Box) demo instance with zero customizations.

 

When a specific non-admin user (G. Geimer) accesses the User (sys_user) table list view, almost all key columns appear completely empty (such as User ID, Email, Active, Created, and Updated). The only column that actually renders data is the Name field.

To troubleshoot, I used the Access Analyzer to check why the platform is hiding this data. To my surprise, the tool shows that everything is fine:

  • Table Read Access: Passed

  • Field Read Access (e.g., first_name): Passed (All ACLs, Data Filtration, and Access Handlers return a green "Passed" status for the read operation).

The Evidence:

  1. Admin List View (Everything is visible):

    visible.png
  2. User List View (everything is white):

    invisible.png
  3. Access Analyzer - Table Level (sys_user):

    table read acl.png
  4. Field Level (sys_user.first_name):

    first_name read acl.png

My Question:

If the Access Analyzer explicitly states that the user passes the security checks to read both the table and the specific fields, why is the OOTB user interface still rendering these columns completely blank? 

 

Since this is a brand new demo instance, there are no custom Before Query Business Rules, no custom Data Masking, and no custom ACLs overriding the behavior. Has anyone encountered this OOTB behavior on the sys_user table? What native platform mechanism or hidden constraint is causing Access Analyzer to say "Passed" while the UI suppresses the data?

 

Thanks in advance for your insights!

2 REPLIES 2

Tanushree Maiti
Tera Patron

Hi @jordimsant 

 

1. Check 

KB0725733 Field values displayed on the form but list shows empty columns 

2. As you are using OOB instance , in that case I will suggest you to raise a case to your ServiceNow Vendor. 

 

 

 

Please Accept the solution if it assisted you with your question & Mark this response as Helpful.
Regards
Tanushree Maiti
ServiceNow Technical Architect
LinkedIn: https://www.linkedin.com/in/tanushreemaiti

I am sure there must be an easy explanation for these. I mean, we are talking about sys_user table in a demo instance, I cannot be the first person that finds this out