HR Profiles are being automatically generated when users navigate to the ESC portal for the first time.Issue HR Profiles are being automatically generated when users navigate to ESC portal for the first time.ReleaseAll releases.CauseThis is the expected behaviour for instances created before Rome: each time a user without an HR Profile opens the ESC portal for the first time, an HR Profile gets created for them.The logic for this is in the Header | Footer "ESC Header":https://instance_name.service-now.com/sp_header_footer.do?sys_id=bda7abc623882300fb0c949e27bf6544--- if(new GlidePluginManager().isActive("com.sn_hr_core")) {data.isHrCoreActive = true;// HR Profilevar hrProfileGr = new GlideRecord('sn_hr_core_profile');hrProfileGr.addQuery('user', gs.getUserID());hrProfileGr.setLimit(1);hrProfileGr.query();if (!hrProfileGr.next()) {hrProfileGr.setValue('user', gs.getUserID());hrProfileGr.insert();}}ResolutionStarting with the Rome release, a new System Property has been introduced to allow you to decide whether to maintain this behaviour or avoid creating the HR Profile on the first visit to the ESC portal. Note that this property does not get created on existing instances upgrading to Rome+. To change this behaviour in pre-Rome releases: 1. Import XML the attached system property "sn_hr_core.esc.create_hrprofile.override" and confirm it is set to false (below URL should bring you to the property once you have imported it)https://instance_name.service-now.com/sys_properties.do?sys_id=7c7b3883eb172010c7296d3eb55228632. Make sure that the Header | Footer "ESC Header" is OOB and on the latest version:https://instance_name.service-now.com/sp_header_footer.do?sys_id=bda7abc623882300fb0c949e27bf65443. Review your RCAs and make sure to move to 'Allowed' state any record that might have been invalidated (if any):https://instance_name.service-now.com/sys_restricted_caller_access_list.do?sysparm_query=status!%3D2%5EORstatus%3DNULL&sysparm_view=