- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-22-2025 11:01 PM
I have read ACL on a field with a role and script and as the condition is not satisfying so the users are not able to see fields on form.
But somehow they are still able to see the fields on list view, can add/remove the fields in list view even though the data is not visible, the fields are, why and how to fix it?
Not able to see how they are getting the access.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-26-2025 12:06 AM
then better to raise a case with ServiceNow.
As per this KB it should work but it's not working for you
Hiding fields from "Personalized Column List"
If my response helped please mark it correct and close the thread so that it benefits future readers.
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-23-2025 12:50 AM
Please share your ACLs. If there is table level access, a user can see the table and the fields. The ACL is just limiting the content within the field. What's the issue of users being able to see the column?
If you have an ACL that only allows a certain group to see records on a certain category, the list will also say 'security constraints hide x number of records'. They can still see the total number, even though the records aren't there.
Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-23-2025 01:05 AM
if the field level READ ACL is blocking then it should not show in the personalize gear icon as well.
1) Do you have any other field level READ ACL which is allowing access?
2) Did you use Access analyser to debug?
[Vancouver Release] Customers gain enhanced access visibility with ServiceNow Access Analyzer
As a workaround create field level add_to_list operation ACL but remember it only supports role
If my response helped please mark it correct and close the thread so that it benefits future readers.
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-25-2025 09:24 PM
Hope you are doing good.
Did my reply answer your question?
If my response helped please mark it correct and close the thread so that it benefits future readers.
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-25-2025 09:56 PM
Hi @Ankur Bawiskar Thank you for the response.
Exactly, that is what I want to understand why the read ACl is not doing the job. The add to list doesn't work me or make no difference in results as I need to use script in ACL and I don't want to change the oob script field hidden on add to list.
The read ACL works fine on other table and hides from column,(I tried for testing) but not here. In the access analyzer, I see that the use is not passing the read ACL check and that is fine. But do we get to see on the list view level, how they see columns in access analyzer? If yes, please suggest.