Index listings do not display correctly for users with 'snc_read_only' roleIssue Index List does not display correctly for users with 'snc_read_only' role. When a user initially loads the list it will display correctly. However for each subsequent load or refresh the listing of indexes with increase, duplicating the initial indexes listed for the specific table However as soon as a user without 'snc_read_only' views indexes the issue will resolves itselfCauseReproducing the issue will trigger a log statement similar to the following: Security restricted: access for table: v_index_creator, user: read.only, operation: delete -- from class: ReadOnlyRoleAccessHandler The list of indexes within ServiceNow platform does not query a permanent table, but rather one which is dynamically populated based upon your initial query requirements. This functionality is referred to as a 'virtual' table. For indexes there is a single table named 'v_index_creator' and each time a user requests to view the indexes for a specific table any existing data in this table is purged before it is repopulated with the requested information. The GUI then displays the records as found within 'v_index_creator'To the end user this is just standard list behaviour, but behind the scenes there is additional actions taking place.However, as per the error message, the 'snc_read_only' role is preventing the deletion of records from the 'v_index_creator' table so it instead simply skips the initial purge step and loads new recordsThe result is the continued growth of records in 'v_index_creator' because it is populated with the same indexes on each view by a 'snc_read_only' user.ResolutionThe easiest approach is to ensure that no users with 'snc_read_only' role need to access index lists. Those without this role will be able to delete records from the virtual table without impact and the issue will not occur This is because we should consider this to be the expected behaviour of the platform given the 'snc_read_only' role. However if you need to workaround this issue the following documentation highlights several sys_properties records that can be introduced to grant read only users with addition access.Read-only role - https://docs.servicenow.com/bundle/paris-platform-administration/page/administer/user-administration/concept/c_ReadOnlyRole.htmlSpecifically in this case there is the 'glide.security.snc_read_only_role.tables.exempt_delete' record which can be used to extend access to the 'v_index_creator' table.This property defaults to a specific set of tables in the background so in order to address this impact you would need to create the following record:Name: glide.security.snc_read_only_role.tables.exempt_deleteType: stringValue: sys_user_preference, sys_ui_list, sys_ui_list_element, sys_db_cache, user_multifactor_auth,v_index_creatorThe first details within value are the 'default' tables, while 'v_index_creator' is added to address this specific impact.Because 'v_index_creator' is a virtual table and is only used to display indexes (and does not actually modify them on tables) there is no risk to adding this property if you need read only users to access this functionality